Reverse lookup on secondary

[Larry]

After checking it appears that the reverse lookup zones do not replicate to
the secondary server. Have I mis-configured something or is this a manual
task?

Larry

 

[Herb Martin]

After checking it appears that the reverse lookup zones do not replicate
to

the secondary server. Have I mis-configured something or is this a manual
task?

Create the Reverse zone on the "secondary" if that is what you want -- point
it to the "primary" (as master) or other secondary for that SAME ZONE.

Reverse lookup zones have NO technical relationship to
forward zones.

People often confuse this -- just because we humans recognize
that 192.168.2.0 is the address range used by DomainYYY.com,
does NOT mean the computers or DNS know this relationship.

[Note: I have LearnQuick.Com machines in another state that have
completely different IPs, appear in completely different reverse zones.]

A "Secondary" is also a confusing term when more than ONE DOMAIN
is involved -- more than one whether it is forward, reverse, or a mix.

A "secondary DNS" server or a "secondary zone" is REALY ONLY a
"secondary server for a PARTICULAR zone".

A secondary for one zone might be a Primary for other zones, AD-integrated
(if it's a DC) for others, and have no relationship to some zones.

Create the Reverse zone on the "secondary" if that is what you want -- point
it to the "primary" (as master) or other secondary for that SAME ZONE.

 

[Larry]

Create the Reverse zone on the "secondary" if that is what
you want -- point it to the "primary" (as master) or other
secondary for that SAME ZONE.

Thanks. Being the dumbass that I am sometimes it never occured
to me that the reverse lookup on the secondary should have been
configured as a secondary zone. All I really needed is a PTR
record for the mail server to prevent mail from being rejected.

 

[Kevin D. Goodknecht Sr. [MVP]]

In Larry <[email protected]>
posted their concerrns,
Then Kevin D4Dad added his reply at the bottom.
All I really needed is a PTR

record for the mail server to prevent mail from being rejected.

Chances are I would bet that creating a reverse lookup on your DNS server
will not stop your mail from being rejected if it is being rejected due to
not having a reverse lookup for your mail server's IP address.

The reason you say?
First your ISP owns the reverse lookup on your IP address unless they have
delegated it to your DNS server. It is very unlikely that your ISP has done
this, and rarely they will for just one or even a few IP addresses.
If you go to www.dnsstuff.com there is a tool for checking the reverse
lookup from the internet, I'd almost bet good money you will find that your
ISP is still authoritative for the reverse lookup.
In which case, you can ask them to delegate it to you or have them create
the PTR for you.

 

[Herb Martin]

What Kevin said....

Odds are, you are not authoritative for the REVERSE zone so
that no one OUTSIDE your net will ever find the reverse records
you add to these.

 

[Larry]

The reason you say?
First your ISP owns the reverse lookup on your IP address
unless they have delegated it to your DNS server. It is
very unlikely that your ISP has done this, and rarely they
will for just one or even a few IP addresses. If you go to
www.dnsstuff.com there is a tool for checking the reverse
lookup from the internet, I'd almost bet good money you
will find that your ISP is still authoritative for the
reverse lookup. In which case, you can ask them to delegate
it to you or have them create the PTR for you.

Interesting, I'll look into that.