Re: Reverse DNS Issue
From: Jonathan de Boyne Pollard (J.deBoynePollard_at_Tesco.NET)
Date: 04/13/04
- Next message: pre-installed: "dhcp permission"
- Previous message: Jonathan de Boyne Pollard: "Re: DNS server order in TCP/IP settings when mixing local and remote (ISP) DNS servers"
- In reply to: Ed Gartin: "Reverse DNS Issue"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 13 Apr 2004 18:13:46 +0100
EG> the mail gets returned or stuck in their spam filter because
EG> it cannot do a Reverse DNS lookup on our domain.
The Brigade has obviously been proselytising.
<URL:http://homepages.tesco.net./~J.deBoynePollard/FGA/dns-avoid-double-reverse.html>
EG> But when we do a Reverse lookup we get no PTR records found ?
Correct.
EG> How do we get the PTR records to show up ?
They already show up.
[C:\]dnsqry /serverip:12.3.228.227 ptr 229.228.3.12.in-addr.arpa.
[0.0.0.0:0000] -> [12.3.228.227:0035] 43
Header: 0000 1+0+0+0, Q, , query, no_error
Question: 229.228.3.12.in-addr.arpa. IN PTR
[12.3.228.227:0035] -> [0.0.0.0:0000] 285
Header: 0000 1+10+0+0, R, RA|AUTH, query, no_error
Question: 229.228.3.12.in-addr.arpa. IN PTR
Answer: 229.228.3.12.in-addr.arpa. IN PTR 3600 leeperderose-syr.leeperderose-syr.com.
Answer: 229.228.3.12.in-addr.arpa. IN PTR 3600 sommeradvantage.com.
Answer: 229.228.3.12.in-addr.arpa. IN PTR 3600 pezrow.com.
Answer: 229.228.3.12.in-addr.arpa. IN PTR 3600 cmn.pezrow.com.
Answer: 229.228.3.12.in-addr.arpa. IN PTR 3600 asmnep.com.
Answer: 229.228.3.12.in-addr.arpa. IN PTR 3600 leeperderose-syr.com.
Answer: 229.228.3.12.in-addr.arpa. IN PTR 3600 cmn.asmnep.com.
Answer: 229.228.3.12.in-addr.arpa. IN PTR 3600 msxram05.asmnep.com.
Answer: 229.228.3.12.in-addr.arpa. IN PTR 3600 msxram05.pezrow.com.
Answer: 229.228.3.12.in-addr.arpa. IN PTR 3600 msxram05.cmn.asmnep.com.
[C:\]
The problem is not on your content DNS server. The problem is that the
owners of the "3.12.in-addr.arpa." content DNS servers (at 12.127.16.69,
12.127.16.70, 199.191.128.105, and 199.191.128.106) are breaking things.
Get them to delegate reverse lookup domains in the _normal_ manner, not
in the unnecessary and (in order to interoperate with the features of
your DNS server software, which you are using) incorrect RFC 2317 style.
<URL:http://homepages.tesco.net./~J.deBoynePollard/FGA/avoid-rfc-2317-delegation.html>
- Next message: pre-installed: "dhcp permission"
- Previous message: Jonathan de Boyne Pollard: "Re: DNS server order in TCP/IP settings when mixing local and remote (ISP) DNS servers"
- In reply to: Ed Gartin: "Reverse DNS Issue"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|