Home » Questions » Computers [ Ask a new question ]

Windows using the DNS suffix search list on all lookups, even valid FQDNs. How to stop this?

Windows using the DNS suffix search list on all lookups, even valid FQDNs. How to stop this?

When doing DNS lookups (specifically using nslookup, for some reason most things are not effected) Windows XP Pro SP3 is using the DNS suffix search list for every single one. Even for fully qualified domain names. For example I lookup "www.microsoft.com" but windows actually asks for "www.microsoft.com.eondream.com" (eondream.com is my primary domain). Now I can fix the issue by removing the Primary DNS suffix, but it seems to me that the DNS suffix search list should be for short, invalid names (where dots=0 or something). I'm sure I have a misconfiguration somewhere in windows but I don't know where. I've changed every option I can think of or find.

Asked by: Guest | Views: 112
Total answers/comments: 2
Guest [Entry]

"Well, I'm no expert, but here's what I found:

This registry entry works for both Windows XP and Windows Vista

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows NT\DNSClient]
""AppendToMultiLabelName""=dword:00000000

HKLM\Software\Policies\Microsoft\Windows NT\DNSClient\AppendToMultiLabelName
Type = DWORD

Data:

0 (Do not Append Suffix)
1 (Append suffix)

If the registry entry is not present, the default in Windows XP is 1, and 0 in Windows Vista.

Note: This registry changes and its effect apply only to the ping command, they do not apply to the nslookup tool. This is because nslookup contains its own DNS resolver and does not rely on the resolver built into the operating system (DNS Client). The DNS (multi-label) query packets sent by the nslookup tool will append the domains listed in the suffix search order irrespective of the registry key settings mentioned here.

Reference: http://blogs.technet.com/networking/archive/2009/04/16/dns-client-name-resolution-behavior-in-windows-vista-vs-windows-xp.aspx"
Guest [Entry]

"I had the same problem because my domain controller was installed as part of a domain and then removed from the domain. For instance domain cloud as subdomain for mydomain.com

Every DNS related action such as running nslookup resulted in an address with the suffix .mydomain.com being appended. For example, performing an nslookup of www.google.com showed up as www.google.com.mydomain.com.

To work around this:

Go to your network card's IP settings and click Advanced
On the DNS tab select Append these DNS suffixes (in order)
Add the two suffixes . and mydomain.com as shown here:

Click OK

This takes effect immediately and affects all NICs on the computer. This must be done for all domain computers."