I am running MS DNS Server on Windows 2000 Server SP3. This server is the primary DNS server listed for all clients. It's a domain controller running 1 active directory-integrated zone. It's also configured to use forwarders pointing to our ISP's DNS servers for external name resolution.
As of 2 days ago, some clients are intermittently not able to resolve internal hosts by their FQDN. However, they can still resolve all external names. For some reason, the fix is to release and renew their DHCP lease. I should note that the secondary DNS server issued to clients by DHCP is currently offline (its been offline for 2 weeks, and this hasn't caused any problems thus far). Here's a capture of the symptoms from one client:
C:\>ping prod.mycompany.com
Unknown host prod.mycompany.com.
C:\>ipconfig /all
Windows 2000 IP Configuration
Host Name . . . . . . . . . . . . : workstat90
Primary DNS Suffix . . . . . . . : mycompany.com
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : mycompany.com
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . : mycompany.com
Description . . . . . . . . . . . : Realtek RTL8139(A)-based PCI Fast E hernet Adapter
Physical Address. . . . . . . . . : 00-30-F1-11-99-23
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.30.60
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.30.1
DHCP Server . . . . . . . . . . . : 192.168.35.8
DNS Servers . . . . . . . . . . . : 192.168.5.250
192.168.35.5
Primary WINS Server . . . . . . . : 192.168.5.250
Secondary WINS Server . . . . . . : 192.168.35.5
Lease Obtained. . . . . . . . . . : Tuesday, January 28, 2003 7:45:36 A
Lease Expires . . . . . . . . . . : Friday, January 31, 2003 7:45:36 AM
C:\>ping
www.yahoo.comPinging
www.yahoo.akadns.net [64.58.76.179] with 32 bytes of data:
Reply from 64.58.76.179: bytes=32 time=78ms TTL=48
Reply from 64.58.76.179: bytes=32 time=78ms TTL=48
Reply from 64.58.76.179: bytes=32 time=47ms TTL=48
Reply from 64.58.76.179: bytes=32 time=47ms TTL=48
Ping statistics for 64.58.76.179:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds:
Minimum = 47ms, Maximum = 78ms, Average = 62ms
C:\>ping zeus
Pinging zeus [192.168.5.250] with 32 bytes of data:
Reply from 192.168.5.250: bytes=32 time<10ms TTL=127
Reply from 192.168.5.250: bytes=32 time<10ms TTL=127
Reply from 192.168.5.250: bytes=32 time<10ms TTL=127
Reply from 192.168.5.250: bytes=32 time<10ms TTL=127
Ping statistics for 192.168.5.250:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
C:\>ping zeus.mycompany.com
Unknown host zeus.mycompany.com.
C:\>ipconfig /release
Windows 2000 IP Configuration
IP address successfully released for adapter "Local Area Connection"
C:\>ipconfig /renew
Windows 2000 IP Configuration
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . : mycompany.com
IP Address. . . . . . . . . . . . : 192.168.30.60
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.30.1
C:\>ping prod.mycompany.com
Pinging prod.mycompany.com [192.168.1.80] with 32 bytes of data:
Reply from 192.168.1.80: bytes=32 time<10ms TTL=63
Reply from 192.168.1.80: bytes=32 time<10ms TTL=63
Reply from 192.168.1.80: bytes=32 time<10ms TTL=63
Reply from 192.168.1.80: bytes=32 time<10ms TTL=63
Ping statistics for 192.168.1.80:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
Sorry for the lengthy post, but I figured this info would be useful in figuring out the problem.
