NSLOOKUP Fails,  Pings are successful.

Posted on 2007-08-08
Last Modified: 2013-12-05
Changed IP Scheme through out the domain.  All machines can ping the DC's, all machines can resolve to the outside world.   All machines can resolve to internal addresses also.  

NSLOOKUP fails:   cannot find  yadda yadda...

But We can Ping the  DC's both forwards and reverse, and NSlookup resolves the IP addresses of the DC's correctly...

During the IP Change over, we Deleted all RECORDS in each zone, but did not delete the zone's themselves.

We have seen the Opposite problem with an NSLOOKUP that works, but fails to ping devices, please do not mix the two up, we cannot NSLOOKUP, but can Ping....


Question by:cvvood
    LVL 7

    Accepted Solution

    are there valid NS records in those zones?
    LVL 3

    Expert Comment

    check that your workstations' primary DNS suffix is correct and consistent; if you're using DNS suffix search list make sure it contains correct zones in the correct order; and double-check local HOSTS files to make sure there's no conflicting information in them... all of the above can be scripted to update all workstations in the domain from a central console and/or through a GPO if using Active Directory.
    LVL 70

    Assisted Solution

    NSLookup will always return a 'failed' message first unless you have a reverse lookup zone.
    LVL 5

    Author Comment

    Thank you northcide, as your answer brought me to what KCTS answered. First look at the network, NSlookup failed,  didn't put 2 and 2 together...

    Thanks all.


    Write Comment

    Please enter a first name

    Please enter a last name

    We will never share this with anyone.

    Featured Post

    Free Trending Threat Insights Every Day

    Enhance your security with threat intelligence from the web. Get trending threat insights on hackers, exploits, and suspicious IP addresses delivered to your inbox with our free Cyber Daily.

    Welcome to my series of short tips on migrations. Whilst based on Microsoft migrations the same principles can be applied to any type of migration. My first tip is around source server preparation. No migration is an easy migration, there is a…
    Know what services you can and cannot, should and should not combine on your server.
    This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…
    This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles from a Windows Server 2008 domain controller to a Windows Server 2012 domain controlle…

    779 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

    Need Help in Real-Time?

    Connect with top rated Experts

    9 Experts available now in Live!

    Get 1:1 Help Now