Reverse Lookup Strange Problem

[Frank A, Zanotti]

Hi All,
I have a strange problem, here is the scenario. I have two DNS servers
on the first dns server (DNS01) I have abc.com as a Secondary zone and on
the second server (DNS02) is the Primary zone for abc.com. I also have a
Primary Reverse look Zone on the first DNS server (DNS01)192.168.1.0 and on
the second DNS server (DNS02) I have a the secondary zone 192.168.1.0. The
servers are setup correctly to do Zone transfers. Now here is the weird
part, I have a client pointing to DNS01 which the secondary zone for abc.com
resides, dynamic update worked fine I was testing pointing clients to a
server that stores the secondary zone to make sure that the updates are sent
to DNS02 which is the primary for abc.com and that DNS01 would get the
update via zone transfer, everything worked fine except the update to the
reverse zone I actually see the update for the PTR record but I see it only
on the secondary zone, when I goto the server that is primary for the zone I
don't see the PTR record there, which seems not to be possible because the
secondary zone is not writable, it has to write to the Primary then the
secondary gets the update via a zone transfer. How the secondary has the
record but the primary does not is beyond me how can this be.

OS DNS02 = Windows Server 2003
OS DNS01 = Windows Advanced Server 2000
No Active Directory Intergrated Zones
No DNS server is a Domain Controller
DNS01 has the latest Service packs
DNS02 has the latest updates

Thanks in Advance
Frank A, Zanotti
(e-mail address removed)

 

[Jonathan de Boyne Pollard]

FAZ> I actually see the update for the PTR record but I see it
FAZ> only on the secondary zone, when I goto the server that is
FAZ> primary for the zone I don't see the PTR record there, [...]

What is the "MNAME" field of the "SOA" resource record at the "zone" apex ?

 

[Michael Johnston [MSFT]]

Frank,
This does sound strange. Since the client was pointing at DNS1 and according to your notes DNS1 is the primary for the reverse lookup, the PTR record will
show up on DNS1. Is that not what you are seeing? Verify that the zone's properties indicate that the zone is indeed set to the correct type for the server that it
is on. Next, you may want to take a trace so that you can see the registration happening on the wire. The client will query for the SOA for the reverse zone. It
will then query to see if the PTR record exists. Then it will send an Update request to the server that holds the SOA. If this goes to the server holding the
secondary, you will want to verify the SOA record for the zone is question is correct.

Thank you,
Mike Johnston
Microsoft Network Support
--

This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this message are best directed to the newsgroup/thread from which they originated.

 

[Frank A, Zanotti]

Michael,
Thanks for answering me. I was testing 3 other machines the day after I
wrote this and it worked fine and the machine I was having the problem with
showed up as well. I Installed the Network Monitor from SMS and as I was
testing the other machines I was capturing packets at the same time and its
quite amazing to see what's going on. I see everything. Thanks for all the
help.
Sincerely
Frank A, Zanotti
(e-mail address removed)

Frank,
This does sound strange. Since the client was pointing at DNS1 and

according to your notes DNS1 is the primary for the reverse lookup, the PTR
record will

show up on DNS1. Is that not what you are seeing? Verify that the zone's

properties indicate that the zone is indeed set to the correct type for the
server that it

is on. Next, you may want to take a trace so that you can see the

registration happening on the wire. The client will query for the SOA for
the reverse zone. It

will then query to see if the PTR record exists. Then it will send an

Update request to the server that holds the SOA. If this goes to the server
holding the

secondary, you will want to verify the SOA record for the zone is question is correct.

Thank you,
Mike Johnston
Microsoft Network Support

rights. Use of included script samples are subject to the terms specified at

http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this

message are best directed to the newsgroup/thread from which they
originated.