Windows Server 2003 weird DNS error

T

The_Unbeliever

Honorary Master
Joined
Apr 19, 2005
Messages
103,193
Reaction score
10,233
Location
Nkaaaaandla
Hi

We're running 2x Win2k3 servers on an AD domain.

Exchange is running on the server with IP 192.168.50.1

All is well, as you can type in "ping server1" and it will reply with the correct IP.

However, the DNS service keeps on adding a new DNS entry for this specific server, with an incorrect IP. This causes Outlook to disconnect from the Exchange server, and leaves a lot of grumpy people in its wake.

Any ideas on how to prevent DNS hijacking, and to enforce that the DNS pointer for server1 will remain 192.168.50.1 no matter what?

TIA

Libs
 
Hold on - we get outside DNS' from our Smoothwall... it might be that some silly IP is stuck in the smoothie's DNS cache.

I have rebooted the Smoothie so any DNS entries who might got cached should be flushed out...

...and add to this mix of woe a suspect onboard NIC... and, as per Murphy's Law, it is on server1... :(

Lovely Monday... *sigh*
 
You don't have to reboot a server to flush the DNS cache.

Open command prompt and type the following : ipconfig /flushdns

Type ipconfig /displaydns to display cache.

Quick Google search :

Turning off DNS Caching under Microsoft Windows

If you experience frequent issues with DNS caching under Microsoft Windows, you can disable client-side DNS caching with either of these two commands:

net stop dnscache
sc servername stop dnscache

This will disable DNS caching until the next reboot. To make the change permanent, use the Service Controller tool or the Services tool to set the DNS Client service startup type to Disabled.

Tuning DNS Caching under Microsoft Windows

You can modify the behavior of the Microsoft Windows DNS caching algorithm by setting two registry entries in the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Dnscache\Parameters registry key.
The MaxCacheTtl represents the maximum time that the results of a DNS lookup will be cached. The default value is 86,400 seconds. If you set this value to 1, DNS entries will only be cashed for a single second.
MaxNegativeCacheTtl represents the maximim time that the results of a failed DNS lookup will be cached. The default value is 900 seconds. If you set this value to 0, failed DNS lookups will not be cached.
Click to expand...
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X