Any info on what I'm missing is greatly appreciated! I can't repro the scenario you are describing. The record data is stored in that object's dnsRecord attribute. The TTL is stored as bytes , along with the other data. AD integrated zones reload their zones from AD every three minutes by default. Are you certain you are not being a little impatient? I don't know if they are.. Sign up to join this community. The best answers are voted up and rise to the top.
Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Learn more. Asked 9 years, 4 months ago. Active 8 years, 8 months ago. Viewed times.
I apologize if this has been asked. My searches have not been successful. Improve this question. JFish JFish 1 1 silver badge 7 7 bronze badges. For host records, it's the MaxCacheEntryTtlLimit, which has a max one day value, but if the host record is less, it will take that value.
But instead of changing it in the registry on each individual machine, you just change it in the zone properties, since this is the time that the client side resolver service will store the record once it has queried it. I would change it from the one hour to 5 minutes. But keep in mind, this will generate quite a bit more of DNS query traffic.
We usually chop it down right before a maintenance window, then put it back to an hour after we've completed the tasks. This post is provided AS-IS with no warranties or guarantees and confers no rights. Office Office Exchange Server.
Not an IT pro? Sign in. United States English. Ask a question. Quick access. Search related threads. This doesn't seem right, and is very annoying.
Anyone seen this before, and what can I do about it? I do have kicking around in the back of my memory some KB article about Windows behaving wonky when this situation occurs, and some way of working around it it's not clear to me why it won't re-lookup the name, though, since it's not like it has a negative response cached , but I forget what exactly.
The server has no forwarders, it's using root servers and doing full lookups itself. Actually we discovered the probem before the KB article was published. The issue was just maddening and nonsensical. As for that one, maddening and nonsensical? That's not the half of it.
0コメント