0

Win2k3 environment using WINs

server resolves to the correct IP when I use the FQDN, but resolves to a different IP when I use the shortname.

I've tried resetting NetBios cache and purging/reloading remote cache table (nbtstat), but that doesn't work.

Any other ideas on how I can get the server to resolve to the same IP when using both shortname and FQDN?

2 Answers2

1

Snortname resolution follows a couple of different paths, both DNS and NetBIOS. Since purging the NBT cache isn't working for you, it must be getting it from somewhere else like WINS. When attempting to resolve a shortname by DNS, it will try resolving each of the domains listed in the DNS search list in order until it finds it. If it finds the wrong one first, it will return that.

If you have a split DNS where servers have both an AD name and a static DNS name, such as, servname.addom.example.com and servname.servers.example.com, and have the servers.example.com domain listed in your search list before addom.example.com, then it will be the servers.example.com version of that name that will be returned. It is for this reason that I recommend to our own people to ensure that AD's DNS domain tops all such search lists.

sysadmin1138
  • 131,083
  • 18
  • 173
  • 296
  • You're comment sent me in the right direction. AD servers had residual entries for the old IP. deleting those from the domain controllers resolved the issue. –  Sep 10 '10 at 18:59
0

Have you checked to see if there is an entry for it in the Lmhosts file? If so then it will use that IP address instead of looking up the IP using WINS or NetBIOS.

Greg Bray
  • 5,530
  • 5
  • 33
  • 52
  • Yes. There are entries in there, but none that point to that name or IP. –  Sep 10 '10 at 17:11