NSLint and PTR Record

Barry Margolin barmar at genuity.net
Mon May 22 21:21:28 UTC 2000


In article <LGgW4.1230$6x.40900 at news0.telusplanet.net>,
David Cost <dcost at post.com> wrote:
>Thanks. When I try to create a PTR record using standard syntax for a
>PTR record in the zone NSLINT rejects it. I was hoping someone may have
>in fact successfully created a PTR record at Granite that worked for
>them and did not get rejected by NSLINT.
>
>If I use nslookup it would appear the reverse domain resolves back to my
>ISP's server, (I was unaware that I had to do something special with the
>ISP whenever their DHCP Server reassigns an IP address every few months,
>thanks for pointing this out).
>
>The main problem that I am trying to overcome is the fact that because
>most large ISP's will not accept mail from an SMTP server unless they
>can complete a reverse lookup, I thought that I just needed a PTR record
>that would at least resolve "some" server. Even if it resolves back to
>my ISP's server instead of mine, it may at least still enable me to send
>mail simply because there is a PTR record that resolves.

Correct.  If you get your address dynamically, the ISP usually won't offer
reverse delegation to you.  They should provide their own reverse DNS for
all their addresses, which should be sufficient for the servers you connect
to.  It doesn't matter that you also have another A record of your own that
also points to the address.

-- 
Barry Margolin, barmar at genuity.net
Genuity, Burlington, MA
*** DON'T SEND TECHNICAL QUESTIONS DIRECTLY TO ME, post them to newsgroups.
Please DON'T copy followups to me -- I'll assume it wasn't posted to the group.



More information about the bind-users mailing list