nslookup not working properly

Active Directory Integrated DNS.  2 windows 2003 dc's.
when on a workstation joined to the domain the error message i get is

Can't find server name for address 10.100.1.1 (ip address of dns server) Non-existent domain
Can't find server name for address 10.100.1.2 (ip address of other dns server) Non-existent domain
Default SErver: Unknown
Address 10.100.1.1

whats interesting is that it still resolves names when i punch in a computer name at the nslookup prompt

jamesmetcalf74Asked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Darius GhassemCommented:
Make sure you have a Reverse lookup zone.

Make sure you are only pointing to internal DNS servers.
0
jamesmetcalf74Author Commented:
im looking at the reverse dns zones and something seems a little strange.

my network is a 10.100.0.0\16
the reverse zone is 0.100.10.in-addr.arpa

shouldnt the reverse zone be
100.10.in-addr.arpa
0
mkeiwuaCommented:
hi jamesmetcalf74,

When you ping the faulty machine from another computer, do you get a reply?

Secondly, kindly open the DNS console and check for the A records in the forward lookup zone for the said machine and the PTR records in the reverse lookup zone

Thirdly, have you set "Register this connection's address in DNS" under DNS in the Advanced properties of TCP/IP of the LAN connection?

B Rgds,

Mkeiwua
0
Challenges in Government Cyber Security

Has cyber security been a challenge in your government organization? Are you looking to improve your government's network security? Learn more about how to improve your government organization's security by viewing our on-demand webinar!

Darius GhassemCommented:
Yeah it should be.
0
mkeiwuaCommented:
I don't think so because the Reverse Lookup Wizard normally tells you to enter the first three octects of the IP Address e.g

A.B.C and then it sets up the name of the Reverse Lookup Zone as : C.B.A.in-addr.arpa

B Rgds,

Mkeiwua

see attached


Reverse.Lookup.png
0
DrDave242Commented:
But he's got a 16-bit subnet mask, so it should indeed be 100.10.in-addr.arpa.
0
mkeiwuaCommented:
Yes but as per attached diagram, doesn't the reverse lookup wizard need all three octects and as it says

"If you use a zero in the network ID, it will appear in the zone name......."

i.e. 10.100.0.0/16 would become 0.100.10.in-addr.arpa?


Or am i missing something?

B Rgds,

Mkeiwua
0
rrcrajesh2003Commented:
IT seems that the first part of DNS look up itself is getting failed. First you must need to focus on right DNS server configuration on the properties of you LAN card on workstation.
0
nole172Commented:
mkeiwua: you are correct, reverse lookup zone are listed with the octets reversed.  Actually the screenshot above gives an example of 10.0 being listed as 0.10...

0
mkeiwuaCommented:
yes nole, i think with the author's consent we can go back to solving the problem....as in his reverse lookup zone is okay as it is.
0
Suliman Abu KharroubIT Consultant Commented:
make sure that the subnet mask on the network adapter is /16.
0
DrDave242Commented:
Even though the reverse lookup zone wizard provides blanks for three octets, you do not have to fill them all in, and with a 16-bit mask, you should leave the last blank empty.  This will create the 100.10.in-addr.arpa reverse lookup zone, which is the correct zone for this network.  0.100.10.in-addr.arpa is definitely not correct.
0
mkeiwuaCommented:
Totally missed that! He should then be having DNS resolution issues on the other machines/network as well.

B Rgds,

Mkeiwua
0
DrDave242Commented:
The clients should get the same "Can't find server name for address..." error when they first run nslookup, but all that error signifies is that nslookup wasn't able to resolve the server's IP address to a hostname using reverse lookup; it doesn't indicate any kind of failure beyond that, which is why forward lookups are still working normally.

I don't like that error message, personally.  It makes you think something is really wrong, when in actuality everything except reverse lookup could be working just fine...and aside from mail servers, how often does anyone use reverse lookup in day-to-day operations anyway?  :)
0
mkeiwuaCommented:
yeah, i agree. i had initially thought that it was just one machine with the problem, thats why was quick to look away from the reverse lookup suggestion...

Thanks Dave.

B Rgds,

Mkeiwua
0
jamesmetcalf74Author Commented:
sorry for the long delay.
you seem to have the symptons nailed.
all workstations on the domain have the same symptons.

im going to post the known symptons.
first attachment is the original error messages when i start nslookup.
it does resolve host names on our network.

the second is the dns event viewer which has a ton of erros that are identical except that they refer to different subnets on our network. (branch office vpns)
the reverse address circled in black is the one that was created by default.
the one circled in red is the one i created yesterday.
the address blackened out is our public ip address.... should that be in there?

nslookup-error-and-name-res.JPG
dns-event-viewer.JPG
0
jamesmetcalf74Author Commented:
one more sympton
the reverse zone i created.
100.10i-addr.arpa   is not in the other domain controller
neither is the 0.in.-addr.arpa
0
Darius GhassemCommented:
Run dcdiag then post results.
0
jamesmetcalf74Author Commented:
Domain Controller Diagnosis

Performing initial setup:
   Done gathering initial info.

Doing initial required tests
   
   Testing server: Site 1\SERVERNAME
      Starting test: Connectivity
         ......................... SERVERNAME passed test Connectivity

Doing primary tests
   
   Testing server: Site 1\SERVERNAME
      Starting test: Replications
         ......................... SERVERNAME passed test Replications
      Starting test: NCSecDesc
         ......................... SERVERNAME passed test NCSecDesc
      Starting test: NetLogons
         ......................... SERVERNAME passed test NetLogons
      Starting test: Advertising
         ......................... SERVERNAME passed test Advertising
      Starting test: KnowsOfRoleHolders
         ......................... SERVERNAME passed test KnowsOfRoleHolders
      Starting test: RidManager
         ......................... SERVERNAME passed test RidManager
      Starting test: MachineAccount
         Warning:  Attribute userAccountControl of SERVERNAME is: 0x82020 = ( UF_PASSWD_NOTREQD | UF_SERVER_TRUST_ACCOUNT | UF_TRUSTED_FOR_DELEGATION )
         Typical setting for a DC is 0x82000 = ( UF_SERVER_TRUST_ACCOUNT | UF_TRUSTED_FOR_DELEGATION )
         This may be affecting replication?
         ......................... SERVERNAME passed test MachineAccount
      Starting test: Services
         ......................... SERVERNAME passed test Services
      Starting test: ObjectsReplicated
         ......................... SERVERNAME passed test ObjectsReplicated
      Starting test: frssysvol
         ......................... SERVERNAME passed test frssysvol
      Starting test: frsevent
         ......................... SERVERNAME passed test frsevent
      Starting test: kccevent
         ......................... SERVERNAME passed test kccevent
      Starting test: systemlog
         An Error Event occured.  EventID: 0x825A0011
            Time Generated: 04/12/2010   15:20:12
            (Event String could not be retrieved)
         ......................... SERVERNAME failed test systemlog
      Starting test: VerifyReferences
         ......................... SERVERNAME passed test VerifyReferences
   
   Running partition tests on : ForestDnsZones
      Starting test: CrossRefValidation
         ......................... ForestDnsZones passed test CrossRefValidation
      Starting test: CheckSDRefDom
         ......................... ForestDnsZones passed test CheckSDRefDom
   
   Running partition tests on : DomainDnsZones
      Starting test: CrossRefValidation
         ......................... DomainDnsZones passed test CrossRefValidation
      Starting test: CheckSDRefDom
         ......................... DomainDnsZones passed test CheckSDRefDom
   
   Running partition tests on : Schema
      Starting test: CrossRefValidation
         ......................... Schema passed test CrossRefValidation
      Starting test: CheckSDRefDom
         ......................... Schema passed test CheckSDRefDom
   
   Running partition tests on : Configuration
      Starting test: CrossRefValidation
         ......................... Configuration passed test CrossRefValidation
      Starting test: CheckSDRefDom
         ......................... Configuration passed test CheckSDRefDom
   
   Running partition tests on : ci
      Starting test: CrossRefValidation
         ......................... ci passed test CrossRefValidation
      Starting test: CheckSDRefDom
         ......................... ci passed test CheckSDRefDom
   
   Running enterprise tests on : "domain name"
      Starting test: Intersite
         ......................... "domain name" passed test Intersite
      Starting test: FsmoCheck
         ......................... "domain name" passed test FsmoCheck
0
Darius GhassemCommented:
All looks good. Doesn't make sense.
0
DrDave242Commented:
When you created the 100.10.in-addr.arpa zone, did you configure it to be AD-integrated?  If so, you may have a replication issue between the DCs preventing the zone from showing up on the other one.  Dcdiag looks good, but you might want to run "repadmin /showrepl" on both DCs to make sure it doesn't indicate any failures.  This is assuming the zone is AD-integrated, of course.

Uou can delete the 0.100.10.in-addr.arpa zone.  It's not needed.  Also, I noticed you've got a zone named 0.in-addr.arpa.  That's...strange.  Is there anything in that zone?
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
jamesmetcalf74Author Commented:
repadmin /showrepl was successful for all tests on both dc's

there is 2 records in 0.in-addr.arpa

start of authority record and ns record
0
Darius GhassemCommented:
Do you have PTR records in your reverse lookup zone.
0
DrDave242Commented:
Upon further review, the 0.in-addr.arpa and 255.in-addr.arpa zones normally show up in advanced-view mode (which you're in), so you can ignore them.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
DNS

From novice to tech pro — start learning today.