asked on

DNS Reverse lookup Zones

Hey Guys,

I was just wondering whether under DNS running on DC (Server 2003) under reverse lookup zone,

The IP address of the DC needs to be added with the full local hostname?
I have noticed after adding the record once, it wen away.

Is that required?

Also have notices once it goes away, and if I go to nslookup, it tells me that the server is unavailable, once created again, it find the DC. Please guide whats needed.

Also, we are having four servers, one is DC rest dont have AD installed. Under DHCP of DC-scope options: DNS Servers, I see all four servers IP addresses listed, 192.168.1.2, 4, 6, 8

And all clients are getting all four IP in the DNS servers from DHCP.

Is that right. Please guide.

thanks

Shivtek

ASKER

I just saw in the reverse lookup zones, that 192.168.1.2 i had added for the DC's hostname, is gone again...

Please guide.

ASKER CERTIFIED SOLUTION

Premkumar Yogeswaran

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Kaffiend

Unless the other non-DC servers are running DNS (not very likely), remove them from the list of DNS servers in the DHCP options. Your network will run better that way !

Shivtek

ASKER

So while editing the NS, when I right click on NS record. Click on properties...in the list, I removed DC.domainname.local and insteat added domainname.local.

Is that right?

SOLUTION

Premkumar Yogeswaran

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Shivtek

ASKER

So I leave dc.domainname.local in the list and add another one point to the parent record?

SOLUTION

Premkumar Yogeswaran

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Shivtek

ASKER

I did everything you wrote... Just removed the dc.domainname.local fron the ns record list... I will that now...

Shivtek

ASKER

Now when I go nslookup... I see domainname.local with the ip on the bottom... Is that right? Or it should should show dc name?

SOLUTION

Premkumar Yogeswaran

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Shivtek

ASKER

Hello,

Again the the reverse lookup zpne, the IP record for the DC.domanname.local has disappeared.
And when I got to nslookup, I get the IP address and unknown server.

In the forward lookup zone:
I have the following
Data: domainname.local (NS)
Right click properties - 2 records:
1) domainname.local IP 192.168.1.2
2) dc.domainname.local IP 192.168.1.2

Data: DC.domainname.local (NS)
Right click properties - 2 records:
1) domainname.local IP 192.168.1.2
2) dc.domainname.local IP 192.168.1.2

Data: 192.168.1.2 (A)
Data: [3298], DC.domainname.local (SOA)

All (4) above have name: (same as parent folder)

In thje reverse lookup zone:
(same as parent folder) NS - DC.domainname.local
(same as parent folder) SOA - [344], DC.domainname.local

Please guide and clarify whats wrong here.
Thanks in advance.

SOLUTION

Premkumar Yogeswaran

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

ChiefIT

Very few applications actually use the reverse lookup zone.

What is the problem, maybe we can fix it.

You can delete the reverse lookup zone, recreate it and make sure dynamic updates are enabled.

Also, check your server's nic config to make sure it dynamically updates as well.

Shivtek

ASKER

"Instead of creating the record manually in reverse lookup can you check the by creating a record in Forward zone with of the DC.domainname.local by checking PTR which will create the Record automatically in reverse lookup...!"

I did this, and after doing that I could see the server name in the nslookup, but now I checked nslookup again and it again says unknown server, and in the reverse lookup zone that record is missing...

I am unsure whats the problem.

Chris Dent

If you are using AD Integrated zones would you confirm:

1. Aging and Scavenging Settings (if configured) for the Reverse Lookup Zone
2. Dynamic Update options for the Reverse Lookup Zone

Are any other records present within the Reverse Lookup Zone (except for NS and SOA)?

If those check out, have you tried deleting and recreating this zone since discovering this problem? Zone corruption is not unheard of. I can provide explicit instructions if required.

Chris