Strange DNS problem

pts.
Tags:
DHCP
DNS
Microsoft Windows
Networking services
Ping
We are running Windows 2003 R2 A/D. The server also handles DNS. During the weekends DNS will not resolve until it's restarted. This only happens during the weekend when usage is very low. No events are logged. When notified of the problem, I can ping by IP while on the server but not by name. When DNS is restarted everything works fine. Any thoughts?

Answer Wiki

Thanks. We'll let you know when a new response is added.

I don’t have an answer to your problem offhand, but I love this sort of mystery. I’d like to make a few troubleshooting suggestions and see where they lead.

1) Set up a batch file which does:
ipconfig /flushdns

Discuss This Question: 3  Replies

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • Jjuliannc
    Do you have only 1 DNS server and is this server also your DHCP server? Aideme
    0 pointsBadges:
    report
  • Jjuliannc
    Sorry, add to last reply...Is the DNS server also a WINS server? Aideme
    0 pointsBadges:
    report
  • Sonyfreek
    Another option is to download and run the program "hostmon" from http://www.ks-soft.net/hostmon.eng/index.htm. It can be configured to monitor services on computers and restart them if they fail. It'll keep track of how many times it goes down and give you some statistics. Unfortunately, it's a shareware product and will "spam" you with messages to register it. However, it's cheap ($99.00) and does the job. Obviously, the goal is to fix the cause of the problem, but this can at least save you from having to come in at 6:00 every Monday so that users can log on again. Obviously, if you have a second DC on your network, you'll want to configure a secondary DNS server. You may also want to set the second DC as the primary DNS server, reinstall the original DNS and see if that fixes it. Unfortunately, without log messages, I feel like that mechanic saying "I don't know what's wrong with it. The check engine light isn't on." Hope this helps, SF
    0 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following