Windows DNS Not Resolving Properly
We're having some strange issues with name resolution. All users are running Windows XP and all DNS servers are Windows 2003 Domain Controllers.
When I try to connect to a system by name, (with RDP, to a share, to AD, etc), I get an error that I could not connect. If I try to ping the name, I get "Ping request could not find host". However, I've checked in DNS and the entries are there. Also, NSLOOKUP resolves the names correctly.
Why can I perform NSLOOKUP but cannot PING?
This is getting bad and is starting to affect a number of users.
Thanks.
When I try to connect to a system by name, (with RDP, to a share, to AD, etc), I get an error that I could not connect. If I try to ping the name, I get "Ping request could not find host". However, I've checked in DNS and the entries are there. Also, NSLOOKUP resolves the names correctly.
Why can I perform NSLOOKUP but cannot PING?
This is getting bad and is starting to affect a number of users.
Thanks.
ChiefIT
Sounds like the router lost the list of DNS servers.
can you elaberate a little bit more about your DNS setup? Are you clients only pointed to your AD DNS server? Does your AD DNS server have any forwarding going on? Conditional forwarding? What is this host you are trying to ping? Is it internal, external? Are you having this trouble with just one host?
Verify that the computer is using the correct IP for the DNS server. Clear your arp cache and flush your DNS on your local machine. When you run NSLOOKUP from a member workstation does your DNS server show as authoritative?
ASKER
Sorry. These are internal hosts that I am trying to connect to. Internet works fine.
I started looking further and I don't think it is actually a DNS issue, because NSLOOKUP works fine. I ran WireShark and it looks like my PC is trying to do a NetBIOS lookup rather than DNS. Since the host is on another subnet, the NetBIOS broadcast won't find it.
Note that when I try to ping, neither the hostname nor hostname.domain.com will resolve.
Thanks.
I started looking further and I don't think it is actually a DNS issue, because NSLOOKUP works fine. I ran WireShark and it looks like my PC is trying to do a NetBIOS lookup rather than DNS. Since the host is on another subnet, the NetBIOS broadcast won't find it.
Note that when I try to ping, neither the hostname nor hostname.domain.com will resolve.
Thanks.
You have a wins server setup onthe network?
ASKER
We currently have 2 WINS servers, but we wanted to phase them out. They were only there when we still had NT4 workstations.
I don't have the WINS servers configured in my network settings.
I don't have the WINS servers configured in my network settings.
WINS server are a great thing ;)
Let me explain alittle...
Network browsing uses netbios and wins is a centralized updated list of netbios names and there ip's.
Network browsing uses netbios and wins is a centralized updated list of netbios names and there ip's.
ASKER
Are WINS servers still that necessary? I thought that MS was doing away with that and making everything DNS.
Should I be adding more WINS servers?
Should I be adding more WINS servers?
If you have two there is not a need for more. Just utilize them.
ASKER
I added a third WINS server local at my site and set all 3 to replicate with each other.
I updated DHCP to assign the WINS servers and I refreshed my IP to get the new settings.
I'm going to let it sit and cook for a bit and see if it resolves my issues.
The strange thing though is that I haven't had this problem at other sites where they do not have the WINS servers assigned via DHCP and have no local WINS servers.
Very odd.
Thanks.
I updated DHCP to assign the WINS servers and I refreshed my IP to get the new settings.
I'm going to let it sit and cook for a bit and see if it resolves my issues.
The strange thing though is that I haven't had this problem at other sites where they do not have the WINS servers assigned via DHCP and have no local WINS servers.
Very odd.
Thanks.
ASKER
The new WINS server did not fix the problem. The odd thing is it seems to be intermittent. I will not be able to resolve a host and then some time later, it will start working.
Also, if I do an ipconfig /release and /renew it will fix the problem temporarily.
It seems to want to do NBT lookups instead of DNS. It's like it's not even trying to do a DNS lookup.
Also, if I do an ipconfig /release and /renew it will fix the problem temporarily.
It seems to want to do NBT lookups instead of DNS. It's like it's not even trying to do a DNS lookup.
ASKER
Evidently, restarting the DNS Client service also seems to resolve the problem.
hi, there
try this from a client
nslookup does it point to the dns server straight away. if not look int the dhcp scope.
All your clients should be shown in the Subnet zone under the dns settings.
Ex. 192.168.0.1 should then list all clients.
if there is no reverse lookup then create one for each different subnet that you have.
Is there a Proxy server device somewhere on the network, sound in that direction as when you restart the dns server it works for a little while. Check for MAC addresses on the server versus the client.
Cooledit
try this from a client
nslookup does it point to the dns server straight away. if not look int the dhcp scope.
All your clients should be shown in the Subnet zone under the dns settings.
Ex. 192.168.0.1 should then list all clients.
if there is no reverse lookup then create one for each different subnet that you have.
Is there a Proxy server device somewhere on the network, sound in that direction as when you restart the dns server it works for a little while. Check for MAC addresses on the server versus the client.
Cooledit
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Closed, 250 points refunded.
Lunchy
Friendly Neighbourhood Community Support Moderator
Lunchy
Friendly Neighbourhood Community Support Moderator