Re: Reverse DNS Issue
From: Herb Martin (news_at_LearnQuick.com)
Date: 04/13/04
- Next message: Herb Martin: "Re: Start of authority records in AD integrated DNS"
- Previous message: Jim Carlock: "Re: [WARNING] The DNS Resolver Cache service is not running."
- In reply to: Ed Gartin: "Reverse DNS Issue"
- Next in thread: Jonathan de Boyne Pollard: "Re: Reverse DNS Issue"
- Reply: Jonathan de Boyne Pollard: "Re: Reverse DNS Issue"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 13 Apr 2004 11:46:13 -0500
"Ed Gartin" <Ed.Gartin@asmnet.com> wrote in message
news:1c2bc01c42171$97db28c0$a101280a@phx.gbl...
> We currently host our own external DNS server with the
> service provider being the secondary. We have run into a
> problem where if we send mail to certain ISP's the mail
> gets returned or stuck in their spam filter because it
> cannot do a Reverse DNS lookup on our domain. We have
> check our server to make sure that all the PTR records
> are in the reverse lookup zone and they are there. But
> when we do a Reverse lookup we get no PTR records found ?
> How do we get the PTR records to show up ? Do we have
> something mis-configured ? Output below from Reverse DNS
> query:
For public addresses (which I am sure you are using for the public
email server -- or at least the transfer agent portion) you probably
CANNOT set the "reverse zone" or PTR records.
You don't "own the zone" for those records; some ISP (or NAP)
does.
You must ask your ISP to fix the PTR for your EMAIL server to
match the name that is uses for an MX record AND the name
it "reports" when sending email.
This last part confuses people (especially those with multiple email
domains) since they don't understand that the email server might
have a name that is NOT within any of the handled email domains.
(ISPs do this all the time: SMTP.myISP.com handles mail for
1000 client companies, etc but can only have ONE PTR record
effectively.)
ASK the ISP to do it.
-- Herb Martin > > Reverse DNS for 12.3.228.229 > Generated by www.DNSstuff.com > Country: UNITED STATES > > Preparation: > The reverse DNS entry for an IP is found by reversing > the IP, adding it to "in-addr.arpa", and looking up the > PTR record. > So, the reverse DNS entry for 12.3.228.229 is found by > looking up the PTR record for > 229.228.3.12.in-addr.arpa. > All DNS requests start by asking the root servers, and > they let us know what to do next. > See How Reverse DNS Lookups Work for more information. > > How I am searching: > Asking c.root-servers.net for 229.228.3.12.in-addr.arpa > PTR record: > c.root-servers.net says to go to dbru.br.ns.els- > gms.att.net. (zone: 12.in-addr.arpa.) > Asking dbru.br.ns.els-gms.att.net. for 229.228.3.12.in- > addr.arpa PTR record: Got CNAME referral to > dbru.br.ns.els-gms.att.net. (zone 229.224/28.228.3.12.in- > addr.arpa.) > Asking dbru.br.ns.els-gms.att.net. for > 229.224/28.228.3.12.in-addr.arpa. PTR record: > dbru.br.ns.els-gms.att.net says to go to > dmtu.mt.ns.els-gms.att.net. (zone: 224/28.228.3.12.in- > addr.arpa.) > Asking dmtu.mt.ns.els-gms.att.net. for > 229.224/28.228.3.12.in-addr.arpa. PTR record: > dmtu.mt.ns.els-gms.att.net says to go to > dmtu.mt.ns.els-gms.att.net. (zone: 224/28.228.3.12.in- > addr.arpa.) > Asking dmtu.mt.ns.els-gms.att.net. for > 229.224/28.228.3.12.in-addr.arpa. PTR record: > dmtu.mt.ns.els-gms.att.net says to go to > name1.pezrow.com. (zone: 224/28.228.3.12.in-addr.arpa.) > Asking name1.pezrow.com. for 229.224/28.228.3.12.in- > addr.arpa. PTR record: Reports that no PTR records exist. > > Answer: > No PTR records exist for 12.3.228.229. [Neg TTL=3600 > seconds] > > Details: > name1.pezrow.com. (an authoritative nameserver for > 228.3.12.in-addr.arpa., which is in charge of the reverse > DNS for 12.3.228.229) > says that there are no PTR records for 12.3.228.229. > > To get reverse DNS set up for 12.3.228.229, you need to > speak to your Internet provider. You could also > check with admin@, who is in charge of the 228.3.12.in- > addr.arpa. zone. > > Note that all Internet accessible hosts are expected to > have a reverse DNS entry (per RFC1912 2.1), > and many mailservers (such as AOL) will likely block E- > mail from mailservers with no reverse DNS entry. > To see the reverse DNS traversal, to make sure that all > DNS servers are reporting the correct results, you can > Click Here. > > >
- Next message: Herb Martin: "Re: Start of authority records in AD integrated DNS"
- Previous message: Jim Carlock: "Re: [WARNING] The DNS Resolver Cache service is not running."
- In reply to: Ed Gartin: "Reverse DNS Issue"
- Next in thread: Jonathan de Boyne Pollard: "Re: Reverse DNS Issue"
- Reply: Jonathan de Boyne Pollard: "Re: Reverse DNS Issue"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
