Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Windows using the DNS suffix search list on all lookups, even valid FQDNs.


  • Please log in to reply
No replies to this topic

#1 RealityGone

RealityGone

  • Members
  • 1 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Austin, TX
  • Local time:08:52 PM

Posted 09 January 2010 - 03:44 PM

When doing DNS lookups 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.

For some reason the problem doesn't seem to effect browsing or a lot of other activities but say if I try to browse to a computer on my internal network I cannot use \\servername.eondream.com\sharename\ only the IP address will work because it is resolving the incorrect domain name.

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

[codebox]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. . . . . . . . . . . . : 192.168.13.32
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.13.13
DNS Servers . . . . . . . . . . . : 192.168.19.19[/codebox]

[codebox]C:\>nslookup
Default Server: shardik.eondream.com
Address: 192.168.19.19

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

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

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

------------
Non-authoritative answer:
Name: www.microsoft.com.eondream.com
Address: 208.69.36.132[/codebox]
(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.

BC AdBot (Login to Remove)

 





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users