I am having an issue with my networks mail... I am getting host name lookup failures for the IP that corresponds to my network's router/firewall/proxy.
I made sure to include a reverse lookup zone for this domain but for some reason, I am getting lookup failures.
Here is a copy of the latest returned piece of mail:
From: Mail Delivery Subsystem <MAILER-DAEMON@localhost.localdomain>
> Date: Wed Apr 30, 2003 8:11:37 PM America/New_York
> To: <eran@route1a.com>
> Subject: Warning: could not send message for past 4 hours
>
> **********************************************
> ** THIS IS A WARNING MESSAGE ONLY **
> ** YOU DO NOT NEED TO RESEND YOUR MESSAGE **
> **********************************************
>
> The original message was received at Wed, 30 Apr 2003 16:06:57 -0400
> from [192.168.5.2]
>
> ----- Transcript of session follows -----
> 451 4.4.1 reply: read error from mail.erie.net.
> ... while talking to backup1.mx.stargate.net.:
> <<< 450 Client host rejected: cannot find your hostname, [4.67.9.18]
> <damon@fishtankcreative.com>,<damon@ourwebpage.com>... Deferred: Name
> server: backup1.mx.stargate.net.: host name lookup failure
> Warning: message still undelivered after 4 hours
> Will keep trying until message is 5 days old
> Reporting-MTA: dns; localhost.localdomain
> Arrival-Date: Wed, 30 Apr 2003 16:06:57 -0400
>
> Final-Recipient: RFC822;
damon@ourwebpage.com
> Action: delayed
> Status: 4.5.0
> Diagnostic-Code: SMTP; 450 Client host rejected: cannot find your
> hostname, [4.67.9.18]
> Last-Attempt-Date: Wed, 30 Apr 2003 20:11:37 -0400
> Will-Retry-Until: Mon, 5 May 2003 16:06:57 -0400
No I have configured my named.conf with this entry:
zone "9.67.4.in-addr.arpa" in
{
type master;
notify yes;
file "/var/named/db.4.67.9.16";
};
Our network is 4.67.9.16/28
What I am most confused about is the zone statement
zone "9.67.4.in-addr.arpa" in.
Should it be
zone "16.9.67.4.in-addr.arpa" in?
I am not authoritative for the entire 4.67.9 subnet, I only have authority for 32 of these IP's. Should I even care? I created this reverse lookup zone at the most a week ago. Maybe the DNS info has not proliferated?
I dunno... what are you're thoughts... I will gladly elaborate some more if needed...
