Ok, so here's the setup. Laptop is connected to our company VPN (Juniper Network Connect 7.2.0). There are two DNS Search suffix's (domain1.com, domain2.local). From that laptop, while connected, nslookup polls the correct DNS server, returns the right IP. Pinging the IP works fine. Pinging the FQDN works fine. Pinging the unqualified domain name appears to be both using the hostname.domain.com suffix (even though that doesn't exist), and appears to be using the results from the local DNS server rather than the VPN DNS server.
More detail:
c:\> nslookup hostname
Server: hostname.domain2.local
Address: 10.0.0.10
Non-authoritative answer:
Name: hostname.domain2.local
Address: 10.0.0.10
c:\> nslookup hostname.domain2.local
Server: hostname.domain2.local
Address: 10.0.0.10
Non-authoritative answer:
Name: hostname.domain2.local
Address: 10.0.0.10
C:\> ping hostname
Pinging hostname.domain1.com [EXTERNAL/WRONG_IP] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for EXTERNAL/WRONG_IP:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
C:\> ping hostname.domain2.local
Pinging hostname.domain2.local [10.0.0.10] with 32 bytes of data:
Reply from 10.0.0.10: bytes=32 time=50ms TTL=128
Reply from 10.0.0.10: bytes=32 time=50ms TTL=128
Reply from 10.0.0.10: bytes=32 time=47ms TTL=128
Reply from 10.0.0.10: bytes=32 time=50ms TTL=128
Ping statistics for 10.0.0.10:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 47ms, Maximum = 50ms, Average = 49ms
So here's what I've tried so far:
- ipconfig /flushdns
- netsh int ip reset all
- Verified that the network adapters are in the right priority order in the advanced settings
- Verified that the TCP/IP routes are correct
- Verified that the hostname isn't in the hosts file.
So... does anyone know why it still seems to be using the wrong DNS server?
ipconfig /all
)?