Jump to content
Forum²

Recommended Posts

Posted

Hello,

 

I Have a Server with Windows 2008 standard edition SP1 installed.

 

The server works well, it shares internet with all the computers in the network with ICS.

 

Everytime after about 3 days all the computers can't go on the internet anymore, but on the server still works.

 

The only way to resolve the problem is to restart the dns service.

 

If I Use routing and remote acces it works to share my internet connection but after a few days I have always a blue screen crash.

 

Does anyone have some experience with this problem?

 

Kind regards

 

Ruben

Posted

There is no error in the error log, About every 2 to 3 days recursive queries fail on my w2k8 server.

 

The server still respond to DNS queries for the AD integrated zones, but is unable to reslove any internet names.

 

Only a restart of the DNS service or clear the cache fixes the problem

  • 2 months later...
Posted
You could also set the secondary DNS ip address to the workstations to something like 4.2.2.1 very fast and reliable DNS server. This would keep the workstations alive and online without restarting services.
  • 3 months later...
Posted

make sure you have one server set as a primary dns server for all .com (external) zones en active directory integrated for local zones. the other server set local zones ad integrated as well and other zones seconary zones... Make sure you enable "replicate to servers in server name tab" and add your dns servers in the name servers tab.

 

It sounds like after a dns problem when a server atemps to replicate zones..

 

This should be the trick.

 

good luck

  • 1 month later...
Posted

I have exactly this problem too. I would be interested to know if you solved it?

 

My 2008 server DNS stops providing any DNS responses every few days but with absolutely no errors. Restarting the service does the job, but I shouldn't be needing to do this!

 

It is a single DNS server on a single DC on a test network - no replication going on. It is using the root hints to resolve internet names.

 

Now, dcdiag /test:dns alerted me to the fact that some of the root hints were wrong. So I updated them from the latest list from internic.net.

 

However, dcdiag /test:dns still complained some were wrong - I removed that one, ran it again and it failed on several other root hint servers - and then was fine again. Is this the 'root' of the problem?!?

 

The only other thing is that I am not using IPV6 - the diagnostics also moan about the missing AAAA records and so forth - but I am not using IPV6, its disabled on the nic, so there are no IPV6 addresses to have records for - so I assume this just the diagnostics not being too clever.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...