Solved

Windows DNS Not Resolving Properly

Posted on 2007-11-15
17
1,698 Views
Last Modified: 2008-02-01
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.
0
Comment
Question by:bornskir
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
17 Comments
 
LVL 38

Expert Comment

by:ChiefIT
ID: 20289450
Sounds like the router lost the list of DNS servers.
0
 
LVL 25

Expert Comment

by:mikeleebrla
ID: 20289460
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?
0
 
LVL 12

Expert Comment

by:bhnmi
ID: 20289489
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?
0
Comparison of Amazon Drive, Google Drive, OneDrive

What is Best for Backup: Amazon Drive, Google Drive or MS OneDrive? In this free whitepaper we look at their performance, pricing, and platform availability to help you decide which cloud drive is right for your situation. Download and read the results of our testing for free!

 
LVL 2

Author Comment

by:bornskir
ID: 20289537
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.
0
 
LVL 12

Expert Comment

by:bhnmi
ID: 20289596
You have a wins server setup onthe network?
0
 
LVL 2

Author Comment

by:bornskir
ID: 20289701
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.
0
 
LVL 12

Expert Comment

by:bhnmi
ID: 20289714
WINS server are a great thing ;)
0
 
LVL 12

Expert Comment

by:bhnmi
ID: 20289724
Let me explain alittle...

Network browsing uses netbios and wins is a centralized updated list of netbios names and there ip's.
0
 
LVL 2

Author Comment

by:bornskir
ID: 20289894
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?
0
 
LVL 12

Expert Comment

by:bhnmi
ID: 20289910
If you have two there is not a need for more. Just utilize them.
0
 
LVL 2

Author Comment

by:bornskir
ID: 20290275
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.
0
 
LVL 2

Author Comment

by:bornskir
ID: 20291763
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.
0
 
LVL 2

Author Comment

by:bornskir
ID: 20291874
Evidently, restarting the DNS Client service also seems to resolve the problem.
0
 
LVL 9

Expert Comment

by:cooledit
ID: 20298146
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
0
 
LVL 2

Accepted Solution

by:
bornskir earned 0 total points
ID: 20653440
I managed to figure out the problem.  Through DHCP, I have all of our DNS servers (ie, all of our domain controllers, about 13 or so) being added to all DHCP clients.  We had a problem with one of our domain controllers so I demoted it and then shut it down.  However I forgot to remove this server from the DNS list.  It seems that every once in awhile, a computer would decide to use this shutdown server for a DNS lookup and since it was off, it would fail.

I ended up rebuilding this DC and bringing it back online.  Once I did that, all was well.

The only strange thing that I don't understand is that why would a host try to use this server for DNS if it was not listed as its primary.  And if a host did not get a response (because it was turned off), why did it not move on to the next server in the list.

A little strange, but it's working now.

I'm going to ask to have this question closed and have my points refunded.

Thank you all for your help though.
0
 
LVL 2

Expert Comment

by:Lunchy
ID: 20692207
Closed, 250 points refunded.
Lunchy
Friendly Neighbourhood Community Support Moderator
0

Featured Post

Free NetCrunch network monitor licenses!

Only on Experts-Exchange: Sign-up for a free-trial and we'll send you your permanent license!

Here is what you get: 30 Nodes | Unlimited Sensors | No Time Restrictions | Absolutely FREE!

Act now. This offer ends July 14, 2017.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

I've always wanted to allow a user to have a printer no matter where they login. The steps below will show you how to achieve just that. In this Article I'll show how to deploy printers automatically with group policy and then using security fil…
There have been a lot of times when we have seen the need to enter a large number of DNS entries in a forward lookup zone. The standard procedure would be to launch the DNS Manager console, create the Zone and start adding new hosts using the New…
In this video we outline the Physical Segments view of NetCrunch network monitor. By following this brief how-to video, you will be able to learn how NetCrunch visualizes your network, how granular is the information collected, as well as where to f…
Monitoring a network: why having a policy is the best policy? Michael Kulchisky, MCSE, MCSA, MCP, VTSP, VSP, CCSP outlines the enormous benefits of having a policy-based approach when monitoring medium and large networks. Software utilized in this v…

719 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question