Windows Forum

Ask something
Discussion Locked

DNS Reverse Lookup failing

0 helpful
10 replies

by razorren

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Hi. I'm in the process of transfering the host of my DNS domain to a locally managed server. I have the server configured with foward and reverse lookup zones in Windows 2000. However when I do a nslookup on the Primary DNS servers IP address I get the following...
c:> nslookup -q =ptr 53.21.100.1
Server: name1.mydomain.com
Address: 53.21.100.1
*** name1.mydomain.com cant find =ptr Server failed

Why can't I do a reverse lookup on this address ?

rbowe@familyguardian.com

10 replies

by poo_music

Is this AD integrated DNS? If yes, do check your _tcp records. Besides, you need to check your name server of your Reverse Lookup Zone. Are they available? Do check it out.

Cheers!

by rkelly

Hi,

you've got a syntax problem. Try one of these, as both should work.

nslookup q=ptr 53.21.100.1

or

nslookup 53.21.100.1

The easiest way to do a reverse lookup is simply to use nslookup IPAddress, it then resolves the IPAddress intoa name if at all possible.

Thanks

by rkelly

Just a note about the previous answer. It has NOTHING to do with _tcp records. These records are used by Windows 2000 clients to find an authenticating domain controller, NOT to find a DNS server!

by jack republic

IT IS SIMPLE
YOU DID NOT CREATE "PTR" RECORD FOR DNS SERVER IN THE REVERSE LOOKUP ZONE .AND YOU NEED "A" RECORD IN FORWORD LOOKUP ZONE

This discussion is closed to new replies.