• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 859
  • Last Modified:

Vista not honouring the DNS suffix search list

My computer is joined to my company's domain, so its primary DNS suffix is mycompany.pvt.

When visiting a client, I get a connection-specific DNS suffix of myclient.pvt.

Running "ipconfig /all" shows the following:

Windows IP Configuration

   Host Name . . . . . . . . . . . . : DEV-KDEAN
   Primary Dns Suffix  . . . . . . . : mycompany.pvt
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : mycompany.pvt
                                       myclient.pvt

Ethernet adapter Local Area Connection:

   Connection-specific DNS Suffix  . : myclient.pvt
   Description . . . . . . . . . . . : Intel(R) 82566MM Gigabit Network Connection
   Physical Address. . . . . . . . . : 00-1E-EC-16-93-5A
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::70c9:9c0f:2e75:1ce5%11(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.15.97(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : February 24, 2009 08:57:48
   Lease Expires . . . . . . . . . . : March 4, 2009 08:57:48
   Default Gateway . . . . . . . . . : 192.168.15.3
   DHCP Server . . . . . . . . . . . : 192.168.14.32
   DNS Servers . . . . . . . . . . . : 192.168.14.2
                                       192.168.14.32
   NetBIOS over Tcpip. . . . . . . . : Enabled

I have "Append primary and connection specific DNS suffixes" enabled on the network card.

Despite this, I cannot resolve hosts on my client's network.  Here's a typical "nslookup" session:

Default Server:  tor-dc02.myclient.pvt
Address:  192.168.14.2

> set d2
> tor-fs01
Server:  tor-dc02.myclient.pvt
Address:  192.168.14.2

------------
SendRequest(), len 46
    HEADER:
        opcode = QUERY, id = 2, rcode = NOERROR
        header flags:  query, want recursion
        questions = 1,  answers = 0,  authority records = 0,  additional = 0

    QUESTIONS:
        tor-fs01.mycompany.pvt, type = A, class = IN

------------
------------
Got answer (121 bytes):
    HEADER:
        opcode = QUERY, id = 2, rcode = NXDOMAIN
        header flags:  response, want recursion, recursion avail.
        questions = 1,  answers = 0,  authority records = 1,  additional = 0

    QUESTIONS:
        tor-fs01.mycompany.pvt, type = A, class = IN
    AUTHORITY RECORDS:
    ->  (root)
        type = SOA, class = IN, dlen = 64
        ttl = 4448 (1 hour 14 mins 8 secs)
        primary name server = A.ROOT-SERVERS.NET
        responsible mail addr = NSTLD.VERISIGN-GRS.COM
        serial  = 2009022400
        refresh = 1800 (30 mins)
        retry   = 900 (15 mins)
        expire  = 604800 (7 days)
        default TTL = 86400 (1 day)

------------
------------
SendRequest(), len 46
    HEADER:
        opcode = QUERY, id = 3, rcode = NOERROR
        header flags:  query, want recursion
        questions = 1,  answers = 0,  authority records = 0,  additional = 0

    QUESTIONS:
        tor-fs01.mycompany.pvt, type = AAAA, class = IN

------------
------------
Got answer (121 bytes):
    HEADER:
        opcode = QUERY, id = 3, rcode = NXDOMAIN
        header flags:  response, want recursion, recursion avail.
        questions = 1,  answers = 0,  authority records = 1,  additional = 0

    QUESTIONS:
        tor-fs01.mycompany.pvt, type = AAAA, class = IN
    AUTHORITY RECORDS:
    ->  (root)
        type = SOA, class = IN, dlen = 64
        ttl = 4448 (1 hour 14 mins 8 secs)
        primary name server = a.root-servers.net
        responsible mail addr = nstld.verisign-grs.com
        serial  = 2009022400
        refresh = 1800 (30 mins)
        retry   = 900 (15 mins)
        expire  = 604800 (7 days)
        default TTL = 900 (15 mins)

------------
*** tor-dc02.myclient.pvt can't find tor-fs01: Non-existent domain
>

As you can see, Vista happily adds my primary DNS suffix but does not fall back to the connection-specific DNS suffix when the first query fails.

What am I missing?
0
kdeanddd
Asked:
kdeanddd
1 Solution
 
kdeandddAuthor Commented:
The problem appears to be related to my wireless card.  My card is unable to bind to the local wireless network and so gets a local 169 address.  When I disconnect from that network, the problem goes away.
It appears to be a Vista bug.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Cloud Class® Course: Amazon Web Services - Basic

Are you thinking about creating an Amazon Web Services account for your business? Not sure where to start? In this course you’ll get an overview of the history of AWS and take a tour of their user interface.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now