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.

Below is the output of ipconfig /all and nslookup (with debug & db2 enabled). This is using a static IP & (internal) DNS server.

C:\>ipconfig /all

Windows IP Configuration

        Host Name . . . . . . . . . . . . : frayedlogic
        Primary Dns Suffix  . . . . . . . : eondream.com
        Node Type . . . . . . . . . . . . : Unknown
        IP Routing Enabled. . . . . . . . : No
        WINS Proxy Enabled. . . . . . . . : No
        DNS Suffix Search List. . . . . . : eondream.com

Ethernet adapter Wireless Network Connection:

        Connection-specific DNS Suffix  . :
        Description . . . . . . . . . . . : Dell Wireless 1390 WLAN Mini-Card
        Physical Address. . . . . . . . . : 00-1B-FC-29-EB-6B
        Dhcp Enabled. . . . . . . . . . . : No
        IP Address. . . . . . . . . . . . :
        Subnet Mask . . . . . . . . . . . :
        Default Gateway . . . . . . . . . :
        DNS Servers . . . . . . . . . . . :
Default Server:  shardik.eondream.com

> set debug
> set db2
> www.microsoft.com
Server:  shardik.eondream.com

Got answer:
        opcode = QUERY, id = 2, rcode = NOERROR
        header flags:  response, want recursion, recursion avail.
        questions = 1,  answers = 1,  authority records = 0,  additional = 0

        www.microsoft.com.eondream.com, type = A, class = IN
    ->  www.microsoft.com.eondream.com
        internet address =
        ttl = 0 (0 secs)

Non-authoritative answer:
Name:    www.microsoft.com.eondream.com

(Note: it resolves to that IP because I use the opendns service and that is their suggestion page or whatever you want to call it) If I am reading the nslookup output correctly then it is not a problem with my DNS server because windows is actually asking for the incorrect domain.

  • 1
    "Even for fully qualified domain names..." -- no, just to set it straight for googlers: www.microsoft.com is not a fully qualified domain name. WIndows is doing this one right. See the should-be-accepted answer: superuser.com/a/413529/150263 – Sz. Mar 25 '18 at 13:08

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]

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


  • 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

  • It doesn't affect nslookup, but it affects every program that uses DNS Client, which includes programs like your web browser. – RyanTM Jul 13 '10 at 23:06

Sorry to revive a clearly old question, but it seems no one suggested the obvious answer of forcing a fqdn. Just use a trailing dot to force top level lookup. So in this example lookup www.microsoft.com..

  • 6
    It’s not really “forcing”. A FQDN ends with a period. The end. Every other format is not a FQDN. www.example.com is only partially qualified. – Daniel B May 17 '17 at 7:56
  • 4
    "Sorry to revive a clearly old question" -- Jeff, thank god you did! Never apologize for actually adding value to an apparently dormant topic, where time is clearly not an important dimension (compared to relevance, consistency, utility etc.) – Sz. Mar 25 '18 at 13:20

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:

  1. Go to your network card's IP settings and click Advanced
  2. On the DNS tab select Append these DNS suffixes (in order)
  3. Add the two suffixes . and mydomain.com as shown here: enter image description here
  4. Click OK

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

  • This is exactly what had me chasing my tail for two hours. Somehow my employer's domain was showing up in the ipconfig /all "DNS Suffix Search List". Turns out, it was listed exactly where you illustrate above. I removed the entry and changed the radio button to "Append primary and connection specific DNS suffixes" and it stopped pinging my employer for every DNS query. – Allen Jackson Jun 15 '18 at 1:57

It works as designed. Just append a dot at the end.

so for e.g.:

nslookup www.yahoo.com. 

instead of

nslookup www.yahoo.com

then you'll get the result you probably want to see.

  • 1
    Your answer is like a comment and OP has already accepted another answer – Sam May 17 '17 at 6:08
  • "OP has already accepted another answer" - that doesn't mean anything, this is not a competition. And OP has accepted the "wrong" answer, BTW. ("Wrong" in the sense of misleading: it has probably solved his problem, but for the wrong reason and narrative.) – Sz. Mar 25 '18 at 13:12

look to see if you have a domain name defined in your Router/Gateway. enter image description here

Your Answer

By clicking "Post Your Answer", you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.