Win XP SP2 clients, Win 2K3 SP1 server, AD, server provides DHCP. DHCP
options set primary DNS = 192.168.1.10 (the Win2K3 server) and alternate DNS
= 192.168.1.1 (gateway device).
Clients do not ever use the alternate DNS server, even when the primary DNS
server is down. When I "net stop dns" on the server, clients cannot resolve
names - they do not query the alternate 192.168.1.1. I've verified this by
watching network traffic.
On the clients I can run nslookup interactively and set the server to
192.168.1.1 and it does resolve names. The problem is that the XP DNS
resolver client never uses the alternate server.
ipconfig /all from a client:
Windows IP Configuration
Host Name . . . . . . . . . . . . : system12
Primary Dns Suffix . . . . . . . : foo.local
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : foo.local
foo.local
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . : foo.local
Description . . . . . . . . . . . : GVC-REALTEK Ethernet 10/100 PCI
Adap
ter
Physical Address. . . . . . . . . : 00-C0-A8-8B-72-7A
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.112
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.10
DNS Servers . . . . . . . . . . . : 192.168.1.10
192.168.1.1
Lease Obtained. . . . . . . . . . : Wednesday, April 02, 2008
4:04:45 PM
Lease Expires . . . . . . . . . . : Thursday, April 10, 2008 4:04:45
PM
nslookup using alternate DNS server:
C:\TEMP>nslookup
www.msn.com 192.168.1.1
*** Can't find server name for address 192.168.1.1: Non-existent domain
Server: UnKnown
Address: 192.168.1.1
Non-authoritative answer:
Name: us.port.msn.com.nsatc.net
Address: 207.68.173.76
Aliases:
www.msn.com
Similar Threads
