question about reverse lookup

Brad Knowles brad.knowles at skynet.be
Thu Sep 20 22:52:03 UTC 2001


At 4:57 PM -0500 9/20/01, Boex,Matthew W. wrote:

>  we are having a mail problem with a domain.  na.bestfoods.com.  sendmail
>  seems to be choking on it's reverse lookup.  here is what i get when i run a
>  dig na.bestfoods.com and dig -x on their ip address.  correct me if i am
>  wrong but isn't having an alias for a reverse ip bad, wrong?  and could this
>  be hosing sendmail?

	No, the reverse delegation behaviour you're seeing is straight 
out of RFC 2317 (see <http://www.faqs.org/rfcs/rfc2317.html>). 
However, they don't appear to have gotten it quite right (this data 
from DNS Expert Professional 1.6, see 
<http://www.menandmice.com/2000/2100_dns_expert.html>):

                               DNS Expert
                   Detailed Report for bestfoods.com.
       9/21/01, 12:50 AM, using the analysis setting "Everything"
======================================================================

Information
----------------------------------------------------------------------
Serial number:           16
Primary name server:     dbru.br.ns.els-gms.att.net.
Primary mail server:     brands.bestfoods.com.
Number of records:       23 (2 NS, 11 MX, 10 A, 0 CNAME, 0 PTR, 0
                          Other)


Errors
----------------------------------------------------------------------
o There are no MX records for the zone
     The zone contains no MX records for the zone itself. This will
     cause delivery problems for mail sent to any account of the form
     user at zone. Every zone for which mail delivery is desired should
     contain at least one MX record.

o The reverse record "10.0/26.84.14.12.in-addr.arpa." does not refer
   to the host "na.bestfoods.com."
     The reverse record "10.0/26.84.14.12.in-addr.arpa." refers to
     "www.prodmaiz.com.", but it should refer to "na.bestfoods.com.".

o The reverse record "10.0/26.84.14.12.in-addr.arpa." does not refer
   to the host "wss3.na.bestfoods.com."
     The reverse record "10.0/26.84.14.12.in-addr.arpa." refers to
     "www.prodmaiz.com.", but it should refer to
     "wss3.na.bestfoods.com.".

o There is no PTR record for the host "wss1.asia.bestfoods.com."
     There is no PTR record available for the host
     "wss1.asia.bestfoods.com." which has the IP address 168.70.234.97.

o There is no PTR record for the host "wss2.asia.bestfoods.com."
     There is no PTR record available for the host
     "wss2.asia.bestfoods.com." which has the IP address
     168.70.234.126.

o There is no PTR record for the host "nordic.bestfoods.com."
     There is no PTR record available for the host
     "nordic.bestfoods.com." which has the IP address 194.52.178.236.

o There is no PTR record for the host "www.stars.bestfoods.com."
     There is no PTR record available for the host
     "www.stars.bestfoods.com." which has the IP address
     199.170.229.246.

o There is no PTR record for the host "www.bestfoods.com."
     There is no PTR record available for the host
     "www.bestfoods.com." which has the IP address 199.248.129.22.

o Lame delegation received from "dns01.unilever.com." for
   "129.248.199.in-addr.arpa."
     The server "dns01.unilever.com." is listed as being authoritative
     for "129.248.199.in-addr.arpa.", but "dns01.unilever.com." does
     not contain authoritative data for the zone.

o Lame delegation received from "dns02.unilever.com." for
   "129.248.199.in-addr.arpa."
     The server "dns02.unilever.com." is listed as being authoritative
     for "129.248.199.in-addr.arpa.", but "dns02.unilever.com." does
     not contain authoritative data for the zone.

o There is no PTR record for the host "brands.bestfoods.com."
     There is no PTR record available for the host
     "brands.bestfoods.com." which has the IP address 199.248.129.23.

o The server "dns1.3rdst.com." did not reply
     The server "dns1.3rdst.com." did not reply when it was queried
     for the name "211.128-25.185.175.216.in-addr.arpa.".  This
     indicates that the server is not running, or it is currently
     unreachable.

o The server "dns2.3rdst.com." did not reply
     The server "dns2.3rdst.com." did not reply when it was queried
     for the name "211.128-25.185.175.216.in-addr.arpa.".  This
     indicates that the server is not running, or it is currently
     unreachable.


Warnings
----------------------------------------------------------------------
o Lame delegation received from "ns-east.cerf.net." for
   "san.cerf.net."
     The server "ns-east.cerf.net." is listed by "ns-east.cerf.net."
     as being authoritative for "san.cerf.net.", but
     "ns-east.cerf.net." does not contain authoritative data for the
     zone.

o The Retry field in the SOA record contains an unusually high value
     The value 10000 of the Retry field in the SOA record is unusually
     high.  The value for this field should be within the range 300 -
     7200.

o The zone contains more than one A record with the address
   194.52.178.236
     There is more than one A record in the zone with the IP address
     194.52.178.236.

o The zone contains more than one A record with the address
   12.14.84.10
     There is more than one A record in the zone with the IP address
     12.14.84.10.

o The zone contains no A record with the zone name
     There is no A record in the zone with the zone name
     "bestfoods.com."

o Lame delegation received from "dns02.unilever.com." for
   "129.248.199.in-addr.arpa."
     The server "dns02.unilever.com." is listed by
     "arrowroot.arin.net." as being authoritative for
     "129.248.199.in-addr.arpa.", but "dns02.unilever.com." does not
     contain authoritative data for the zone.

o Lame delegation received from "dns01.unilever.com." for
   "129.248.199.in-addr.arpa."
     The server "dns01.unilever.com." is listed by
     "arrowroot.arin.net." as being authoritative for
     "129.248.199.in-addr.arpa.", but "dns01.unilever.com." does not
     contain authoritative data for the zone.

---------------------------------------------------

-- 
Brad Knowles, <brad.knowles at skynet.be>

H4sICIFgXzsCA2RtYS1zaWcAPVHLbsMwDDvXX0H0kkvbfxiwVw8FCmzAzqqj1F4dy7CdBfn7
Kc6wmyGRFEnvvxiWQoCvqI7RSWTcfGXQNqCUAnfIU+AT8OZ/GCNjRVlH0bKpguJkxiITZqes
MxwpSucyDJzXxQEUe/ihgXqJXUXwD9ajB6NHonLmNrUSK9nacHQnH097szO74xFXqtlbT3il
wMsBz5cnfCR5cEmci0Rj9u/jqBbPeES1I4PeFBXPUIT1XDSOuutFXylzrQvGyboWstCoQZyP
dxX4dLx0eauFe1x9puhoi0Ao1omEJo+BZ6XLVNaVpWiKekxN0VK2VMpmAy+Bk7ZV4SO+p1L/
uErNRS/qH2iFU+iNOtbcmVt9N16lfF7tLv9FXNj8AiyNcOi1AQAA


More information about the bind-users mailing list