Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I have a Windows Server 2008 R2 DNS server in our AD. Every now and again (sometimes once a week, sometimes three times a day) it will just stop resolving certain domain names. It is NOT a problem with caching TTL's for .uk and .eu TLDs. The records in question have a 30-minute TTL and are hosted with DNS Made Easy. Other domains on the same TLD work fine.

The solution to this is to just restart the DNS service and it all comes back online, but I need a more permanant solution.

Where is the best place to start debugging this? Does Windows DNS server have some tracing or debugging logs I can enable and study?

share|improve this question

1 Answer 1

up vote 1 down vote accepted

You can turn on some fairly verbose debugging in the properties sheets for the DNS server itself. It'll log each query received and the response sent to the client.

I'd capture network traffic, too, and see what's happening on the wire. There's nothing like seeing what's on the wire.

I'd turn on "Advanced Features" in the management console and dig into the cache when you're having the problem and see if something odd is being cached by the DNS server. I had a problem that, while I'm sure is completely unrelated to what you're seeing, where a Customer' ISP's DNS server would return a private IP address for hosts in their domain periodically. Looking at the cache showed me what was going on and led me to notifying the ISP of their problem.

share|improve this answer
    
Great place to start, thanks. I have a feeling its related to glue records, but I need to be sure before I go and blast the registrar. –  Mark Henderson Aug 2 '10 at 4:17

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.