In message <b86f8bceeed5184ca225e0cc10ff61163ec...@bdc03srv04.bdc.int>, "Frank
Pikelner" writes:
> This is a multi-part message in MIME format.
>
> --===============3881074899120402985==
> Content-class: urn:content-classes:message
> Content-Type: multipart/alternative;
> boundary="----_=_NextPart_001_01C9EABF.A23632E2"
>
> This is a multi-part message in MIME format.
>
> ------_=_NextPart_001_01C9EABF.A23632E2
> Content-Type: text/plain;
> charset="iso-8859-1"
> Content-Transfer-Encoding: quoted-printable
>
>
> Every now and then we get a bounce on emails that are sent through one =
> of our mails servers located on 64.187.3.170. The bounce messages look =
> as follows and appear to indicate that our reverse zone is missing a =
> record, though the record is there and resolves through nslookup. The =
> ISP delegates a number of IP addresses from the zone back to us (16 IP =
> addresses). So my guess is that our zone file needs to be rewritten or =
> there may be something else I'm missing.
>
>
> <first_l...@some_domain.com>: host mx.some_domain.com[xxx.xx.xx.xx] =
> said: 450 4.7.1 Client
> host rejected: cannot find your hostname, [64.187.3.170] (in reply =
> to RCPT
> TO command)
>
>
> Performing a manual reverse lookup correctly displays the correct name =
> for 170.3.187.64.in-addr.arpa. Our zone file looks as follows (other =
> records removed):
ns1.blue-dot.ca is NOT configured to serve
162-27.3.187.64.in-addr.arpa. It should be so configured.
Mark
162-27.3.187.64.in-addr.arpa. 86400 IN NS ns3.blue-dot.ca.
162-27.3.187.64.in-addr.arpa. 86400 IN NS ns1.blue-dot.ca.
162-27.3.187.64.in-addr.arpa. 86400 IN NS ns2.blue-dot.ca.
;; Received 115 bytes from 209.135.99.3#53(ns2.toroon.grouptelecom.net) in 249
ms
3.187.64.in-addr.arpa. 1800 IN SOA ns1.blue-dot.ca.
dnsadmin.ns1.blue-dot.ca. 2009011401 1800 900 604800 1800
;; Received 110 bytes from 64.187.3.170#53(ns3.blue-dot.ca) in 679 ms
>
> $ORIGIN .
> $TTL 86400 ; 1 day
> 3.187.64.in-addr.arpa IN SOA ns1.blue-dot.ca. =
> dnsadmin.ns1.blue-dot.ca. (
> 2009011401 ; serial
> 1800 ; refresh (30 minutes)
> 900 ; retry (15 minutes)
> 604800 ; expire (1 week)
> 1800 ; minimum (30 minutes)
> )
> NS ns1.blue-dot.ca.
> NS ns2.blue-dot.ca.
> NS ns3.blue-dot.ca.
> $ORIGIN 3.187.64.in-addr.arpa.
> 170 PTR smtp3.netcraftcommunications.com.
>
> ------_=_NextPart_001_01C9EABF.A23632E2
> Content-Type: text/html;
> charset="iso-8859-1"
> Content-Transfer-Encoding: quoted-printable
>
> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
> <HTML>
> <HEAD>
> <META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
> charset=3Diso-8859-1">
> <META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
> 6.5.7651.59">
> <TITLE>Assistance with reverse lookup zone</TITLE>
> </HEAD>
> <BODY>
> <!-- Converted from text/plain format -->
> <BR>
>
> <P><FONT SIZE=3D2>Every now and then we get a bounce on emails that are =
> sent through one of our mails servers located on 64.187.3.170. The =
> bounce messages look as follows and appear to indicate that our reverse =
> zone is missing a record, though the record is there and resolves =
> through nslookup. The ISP delegates a number of IP addresses from the =
> zone back to us (16 IP addresses). So my guess is that our zone file =
> needs to be rewritten or there may be something else I'm missing.<BR>
> <BR>
> <BR>
> <first_l...@some_domain.com>: host =
> mx.some_domain.com[xxx.xx.xx.xx] said: 450 4.7.1 Client<BR>
> host rejected: cannot find your hostname, =
> [64.187.3.170] (in reply to RCPT<BR>
> TO command)<BR>
> <BR>
> <BR>
> Performing a manual reverse lookup correctly displays the correct name =
> for 170.3.187.64.in-addr.arpa. Our zone file looks as follows (other =
> records removed):<BR>
> <BR>
> $ORIGIN .<BR>
> $TTL 86400 ; 1 day<BR>
> 3.187.64.in-addr.arpa IN SOA ns1.blue-dot.ca. =
> dnsadmin.ns1.blue-dot.ca. (<BR>
> &=
> nbsp; &n=
> bsp; 2009011401 ; serial<BR>
> &=
> nbsp; &n=
> bsp; =
> 1800 ; refresh (30 minutes)<BR>
> &=
> nbsp; &n=
> bsp; =
> 900 ; retry (15 minutes)<BR>
> &=
> nbsp; &n=
> bsp; 604800 =
> ; expire (1 week)<BR>
> &=
> nbsp; &n=
> bsp; =
> 1800 ; minimum (30 minutes)<BR>
> &=
> nbsp; &n=
> bsp; )<BR>
> &=
> nbsp; =
> NS ns1.blue-dot.ca.<BR>
> &=
> nbsp; =
> NS ns2.blue-dot.ca.<BR>
> &=
> nbsp; =
> NS ns3.blue-dot.ca.<BR>
> $ORIGIN 3.187.64.in-addr.arpa.<BR>
> 170 &nbs=
> p; =
> PTR smtp3.netcraftcommunications.com.<BR>
> </FONT>
> </P>
>
> </BODY>
> </HTML>
> ------_=_NextPart_001_01C9EABF.A23632E2--
>
> --===============3881074899120402985==
> Content-Type: text/plain; charset="us-ascii"
> MIME-Version: 1.0
> Content-Transfer-Encoding: 7bit
> Content-Disposition: inline
>
> _______________________________________________
> bind-users mailing list
> bind-users@lists.isc.org
> https://lists.isc.org/mailman/listinfo/bind-users
> --===============3881074899120402985==--
--
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742 INTERNET: ma...@isc.org
_______________________________________________
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
