Reverse Lookup Zone and NSlookup

[ahspao]

I have a 2003 server with DNS, i'm getting a Event 1054 error and DNS fails so i'm testing things with NSLOOKUP. I type nslookup google.com and it gives me the two ip addresses for google, but when i type nslookup "x.x.x.x" it doesn't tell me that belongs to google. It does resolve workstations on the local network though.

 

[ShackDaddy]

That just means that Google doesn't have raddr records for those ip's. For a reverse lookup to work, you have to specifically create all the reverse lookup records, and not all public hosts on the internet maintain them. They are only critical for a few things like spam server identification and other mail-related schemes.

By default, if you have a reverse lookup zone created, each new A record that gets created will also get a matching reverse record, so it's not surprising that it works within your network.

Where are you getting the 1054 event? On the server, or on some of the clients?

ShackDaddy

 

[ahspao]

I was getting the Event 1054 on the Server. I traced the problem down to a registry setting that the OCE technician changed in order to get SMB signing turned off. That basically killed communication between Workstation and Server withing the server itself and brought it down to its knees. Problem was solved.