Link to home
Start Free TrialLog in
Avatar of slselwyn
slselwynFlag for United Kingdom of Great Britain and Northern Ireland

asked on

2 DNS records for server causing problems

This is the problem. Setup: SBS 2003 server address 10.0.0.100,  RAS Internal IP routing 10.0.0.60, Server name XXXX. In DNS forward zone XXXX is shown as both 10.0.0.60 and 10.0.0.100. There are connection issues from workstations sometimes solved by a server reboot or combined server & workstation reboot. When the problem exists ping XXXX from a workstation resolves as 10.0.0.60. If I then delete 10.0.0.60 from DNS and flushdns on the workstation it then correctly resolves as 10.0.0.100 and everything works. Changes to the workstations host file also solves the problem. The issue is that 10.0.0.60 keeps on returning as a DNS record. Why does it so this, should it be there and if not how do I stop this from coming back and creating issues on workstations without host file changes?
Avatar of Glen Knight
Glen Knight
Flag of United Kingdom of Great Britain and Northern Ireland image

Make sure that "register this connection in DNS" is only checked on the card that you want registered with DNS.

You can find this under TCP/IP Properties and then advanced.

Check the setting on both/each card.
ASKER CERTIFIED SOLUTION
Avatar of Darius Ghassem
Darius Ghassem
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
-Open the DNS management console, right click on the server and choose properties. Under Interfaces select only the appropriate IPv4 and IPv6 (if present) appropriate for the primary adapter.
-Also in the network connections window, on the menu bar choose advanced | advanced settings | adapters and bindings | make sure your LAN adapter is at the top of the list
-Flush DNS (delete wrong entries from DNS)
Avatar of slselwyn

ASKER

This problem had our IT people puzzled. Initial testing of the workaround in the KB looks as though it has solved the problem. Well done.