On Jun 12, 2009, at 9:37 AM, Frank Pikelner wrote:
Thank you for everyone's assistance. I have updated the zone files.
After the updates and restarting BIND, I run "dig +trace ptr
170.3.187.64.in-addr.arpa" and the result stops just prior to
getting to
my DNS server and correctly resolving the
Frank Pikelner wrote:
Thank you for everyone's assistance. I have updated the zone files.
After the updates and restarting BIND, I run "dig +trace ptr
170.3.187.64.in-addr.arpa" and the result stops just prior to getting to
my DNS server and correctly resolving the name of the IP address. I'm
new
On Fri, 2009-06-12 at 11:42 +1000, Mark Andrews wrote:
> In message ,
> "Frank
> Pikelner" writes:
> > 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
Hi
As others have indicated, this block has been delegated to you using RFC2317
- Classless IN-ADDR.ARPA delegation.
You have to make configure a zone in your named.conf named
162-27.3.187.64.in-addr.arpa.
Then populate this zone with your data. Something like
...
$ORIGIN 162-27.3.187.64.in-addr
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
Frank Pikelner wrote:
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 nslo
On Thursday 11 June 2009, 20:08 Frank Pikelner wrote:
> : 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)
ns2.toroon.grouptelecom.net, which is a nameserver for 3.187.64.in-addr.arpa
according
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
8 matches
Mail list logo
