NSLOOKUP works but pinging FQDN does not on WIndows 7 machines

Hi All

I have a few machines with strange DNS issues that are also intermittent

Issue

Accessing an internal system jira.mydomain.com normally works OK however on occasions some users reports it fails, if we then try and ping jira.mydomain.com from the users machine it says unable to resolve, if I do an nslookup it resolves fine. If you leave it a while it just starts working again.

My own machine has never had an issue yet we are on the same VLAN and have same DNS servers configured

Steps I have checked so far

DNS servers they get are correct
DNS search suffixes are configured
Firewall is disabled
No obvious errors on DNS servers ( AD integrated Zones )

iconfig /flushdns does not fix


Anyone got any ideas, I see a lot of people report the same issue but cant seem to find a conclusive post with a fix
LVL 5
ncomperAsked:
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

x
 
footechConnect With a Mentor Commented:
For intermittent issues like this it is almost always due to different DNS servers being used (i.e. it works when one server is queried, but doesn't when another one is queried).  This can happen when a client is configured to use a DNS server inside the network as preferred, and an ISP's or other public DNS server as alternate.  Or if the client is using internal DNS servers for both preferred and alternate, if both servers don't have the same records because there is a problem with replication (assuming the use of AD integrated zones like you mentioned you have), or in different environments with zone transfers, etc.  A network capture when the problem is occurring could tell you exactly which DNS server is being queried.  When you did your nslookup queries, did you try multiple servers?
0
 
SandeshdubeySenior Server EngineerCommented:
Ensure correct dns setting is set as this http://abhijitw.wordpress.com/2012/03/03/best-practices-for-dns-client-settings-on-domain-controller/

Check the health of DCs by dcdiag /q and repadmin /replsum.When the issue occur check the event log on workstation and server too for any errors and warning and post the same.

I you have antivirus installed disable the same temporarly.
0
 
ncomperAuthor Commented:
Thanks

I have been doing some research and it appears that its a client side issue with the DNS resolver, when doing an nslookup the query is always sent to the DNS server (Which works)

When pinging by fqdn it uses the hosts local cache first and this is where I believe its failing and the request never makes it to the DNS server
0
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

 
footechCommented:
It's true that nslookup uses its own resolver.
Did you do a network capture during a period when the name can't be resolved?
0
 
ncomperAuthor Commented:
No that's my next step thanks
0
 
ncomperAuthor Commented:
Thanks, after all that it turned out there was a legacy efficient IP box that some users where querying that was missing some A records
0
All Courses

From novice to tech pro — start learning today.