<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 9/22/2015 2:25 PM,
<a class="moz-txt-link-abbreviated" href="mailto:bind-users-request@lists.isc.org">bind-users-request@lists.isc.org</a> wrote:<br>
</div>
<blockquote
cite="mid:mailman.42573.1442949906.26361.bind-users@lists.isc.org"
type="cite">
Message: 5 Date: Tue, 22 Sep 2015 14:24:57 -0500
From: Lyle Giese <a class="moz-txt-link-rfc2396E" href="mailto:lyle@lcrcomputer.net"><lyle@lcrcomputer.net></a>
To: <a class="moz-txt-link-abbreviated" href="mailto:bind-users@lists.isc.org">bind-users@lists.isc.org</a>
Subject: Re: How to Fix Reverse DNS?
Message-ID: <a class="moz-txt-link-rfc2396E" href="mailto:5601AB09.9080300@lcrcomputer.net"><5601AB09.9080300@lcrcomputer.net></a>
Content-Type: text/plain; charset="windows-1252"; Format="flowed"
You don't fix this, AT&T needs to be told to fix it. I assume
you have static IPv4 addresses? You don't seem to have an MX
record at all.
The way AT&T will update this is if your MX record(or backup
MX record) points to this ip address and then they should honor a
request to set the reverse lookup for you.
Lyle Giese
LCR Computer Services, Inc.
On 9/22/2015 2:08 PM, Ron Wingfield wrote:
<blockquote type="cite">
<pre wrap="">RE: BIND v9.10.2
I have recently converted from a "legacy" DSL service to AT&T's
U-verse . . .has been a painful experience. Heretofore, the following
from /var/named/named.conf
zone "233.202.162.in-addr.arpa" {
type master;
file "./zonefiles/db.233.202.162.rev";
};
. . .and the contents of the zone configuration file as follows:
$TTL 3h
@ IN SOA archaxis.net. root.archaxis.net. (
2015080601 ; Serial
3h ; Refresh
1h ; Retry
1w ; Expire
1h ) ; Negative cashing TTL
IN NS ns1.archaxis.net.
IN NS ns2.archaxis.net.
1 IN PTR archaxis.net.
1 IN PTR ns1.archaxis.net.
1 IN PTR ns2.archaxis.net.
AT&T (in all of their surliness) is rejecting email from my SMTP
(SendMail) server and issuing the following typical complaint:
----- The following addresses had permanent fatal errors -----
<a class="moz-txt-link-rfc2396E" href="mailto:/addressee-changed/@sbcglobal.net"></addressee-changed/@sbcglobal.net></a>
(reason: 550 5.7.1 Connections not accepted from servers without a valid sender domain.alph161 Fix reverse DNS for 162.202.233.81)
----- Transcript of session follows -----
... while talking to al-ip4-mx-vip1.prodigy.net.:
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> MAIL From:<a class="moz-txt-link-rfc2396E" href="mailto:Ron.Wingfield@Archaxis.net"><Ron.Wingfield@Archaxis.net></a>
</pre>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">
<<< 550 5.7.1 Connections not accepted from servers without a valid sender domain.alph161 Fix reverse DNS for 162.202.233.81
554 5.0.0 Service unavailable
I am at a loss for resolution of this problem. How am I supposed to
"Fix reverse DNS"? The configuration scenario previously worked since
2002. Can someone suggest a fix?
Thanks,
Ron W.
_______________________________________________
Please visit <a class="moz-txt-link-freetext" href="https://lists.isc.org/mailman/listinfo/bind-users">https://lists.isc.org/mailman/listinfo/bind-users</a> to unsubscribe from this list
bind-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:bind-users@lists.isc.org">bind-users@lists.isc.org</a>
<a class="moz-txt-link-freetext" href="https://lists.isc.org/mailman/listinfo/bind-users">https://lists.isc.org/mailman/listinfo/bind-users</a>
</pre>
</blockquote>
<pre wrap="">
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <a class="moz-txt-link-rfc2396E" href="https://lists.isc.org/pipermail/bind-users/attachments/20150922/32cf9fb1/attachment.html"><https://lists.isc.org/pipermail/bind-users/attachments/20150922/32cf9fb1/attachment.html></a>
------------------------------
_______________________________________________
bind-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:bind-users@lists.isc.org">bind-users@lists.isc.org</a>
<a class="moz-txt-link-freetext" href="https://lists.isc.org/mailman/listinfo/bind-users">https://lists.isc.org/mailman/listinfo/bind-users</a>
End of bind-users Digest, Vol 2206, Issue 1
*******************************************
</pre>
</blockquote>
RE: <br>
<blockquote>
<pre wrap="">You don't fix this, AT&T needs to be told to fix it. I assume you have
static IPv4 addresses? You don't seem to have an MX record at all.
The way AT&T will update this is if your MX record(or backup MX record)
points to this ip address and then they should honor a request to set
the reverse lookup for you.
</pre>
</blockquote>
<br>
Yes, I have static IPs.<br>
I do have an MX record as follows (in the zone file) . . .plus the
SPF TXT record added today to make Google happy:<small><br>
</small>
<blockquote><font face="Courier New, Courier, monospace"><small>archaxis.net.
IN A 123.456.789.123<br>
|<----I had failed to include this period (for
some reason probably lost when edit-adding the SPF TXT)<br>
archaxis.net. IN MX 10 archaxis.net.<br>
archaxis.net. IN TXT "v=spf1 a
include:_spf.google.com ~all"</small><br>
<br>
</font></blockquote>
<font face="Helvetica, Arial, sans-serif">After correction of the
missing period, dig now returns the following:<br>
<small><font face="Courier New, Courier, monospace"><br>
</font></small></font>
<blockquote><small><font face="Courier New, Courier, monospace">#
dig -t MX archaxis.net</font></small><br>
<br>
<small><font face="Courier New, Courier, monospace">;
<<>> DiG 9.10.2 <<>> -t MX
archaxis.net</font></small><br>
<small><font face="Courier New, Courier, monospace">;; global
options: +cmd</font></small><br>
<small><font face="Courier New, Courier, monospace">;; Got answer:</font></small><br>
<small><font face="Courier New, Courier, monospace">;;
->>HEADER<<- opcode: QUERY, status: NOERROR, id:
41951</font></small><br>
<small><font face="Courier New, Courier, monospace">;; flags: qr
rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1</font></small><br>
<br>
<small><font face="Courier New, Courier, monospace">;; OPT
PSEUDOSECTION:</font></small><br>
<small><font face="Courier New, Courier, monospace">; EDNS:
version: 0, flags:; udp: 512</font></small><br>
<small><font face="Courier New, Courier, monospace">;; QUESTION
SECTION:</font></small><br>
<small><font face="Courier New, Courier, monospace">;archaxis.net.
IN MX</font></small><br>
<br>
<small><font face="Courier New, Courier, monospace">;; AUTHORITY
SECTION:</font></small><br>
<small><font face="Courier New, Courier, monospace">archaxis.net.
328 IN SOA archaxis.net.
rtwingfield.archaxis.net. 2015092201 10800 3600 604800 3600</font></small><br>
<br>
<small><font face="Courier New, Courier, monospace">;; Query time:
39 msec</font></small><br>
<small><font face="Courier New, Courier, monospace">;; SERVER:
8.8.8.8#53(8.8.8.8)</font></small><br>
<small><font face="Courier New, Courier, monospace">;; WHEN: Tue
Sep 22 16:29:21 CDT 2015</font></small><br>
<small><font face="Courier New, Courier, monospace">;; MSG SIZE
rcvd: 89<br>
<br>
</font></small></blockquote>
<font face="Helvetica, Arial, sans-serif"><small>. . .but still
fails. Apparently, this is indeed an issue to take up with
AT&T.<br>
<br>
Thanks again to all, and </small></font>Lyle Giese
<br>
<br>
<font face="Helvetica, Arial, sans-serif"><small>Ron W.<br>
</small></font><br>
<br>
</body>
</html>