How to Fix Reverse DNS?

[Ron Wingfield]

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 -----
<addressee-changed@sbcglobal.net>
    (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.:

MAIL From:<Ron.Wi...@Archaxis.net>

<<< 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.

[Reindl Harald]

you jsut control the reverse DNS until the ISP/Provider who owns the
network delegates the PTR zone to your namsservers - that's it

Am 22.09.2015 um 21:08 schrieb Ron Wingfield:
> 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 -----

> </addressee-changed/@sbcglobal.net>

[Reindl Harald]

- you just
+ you just *do not*

[Lyle Giese]

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:

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 -----

<addressee-changed@sbcglobal.net>

    (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.:

MAIL From:<Ron.Wi...@Archaxis.net>

<<< 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 https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list

bind-users mailing list
bind-...@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users

[Reindl Harald]

in other words: i doubt you operate "ns1.swbell.net", "ns2.swbell.net"
and "ns3.sbcglobal.net" and as long the zone don't point to your
namesevrer the world don't care about your configuration

[harry@srv-rhsoft:~]$ dig NS 233.202.162.in-addr.arpa.
; <<>> DiG 9.10.2-P4-RedHat-9.10.2-5.P4.fc22 <<>> NS
233.202.162.in-addr.arpa.
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 11397
;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1024
;; QUESTION SECTION:
;233.202.162.in-addr.arpa. IN NS

;; ANSWER SECTION:
233.202.162.in-addr.arpa. 3600 IN NS ns2.swbell.net.
233.202.162.in-addr.arpa. 3600 IN NS ns1.swbell.net.
233.202.162.in-addr.arpa. 3600 IN NS ns3.sbcglobal.net.

Am 22.09.2015 um 21:21 schrieb Reindl Harald:
> - you just
> + you just *do not*
>
> Am 22.09.2015 um 21:20 schrieb Reindl Harald:
>> you jsut control the reverse DNS until the ISP/Provider who owns the
>> network delegates the PTR zone to your namsservers - that's it
>>
>> Am 22.09.2015 um 21:08 schrieb Ron Wingfield:

>>> 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 -----

>>> </addressee-changed/@sbcglobal.net>

[Ron Wingfield]

On 9/22/2015 2:25 PM, bind-user...@lists.isc.org wrote:

    <<< 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 https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list

bind-users mailing list
bind-...@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/bind-users/attachments/20150922/32cf9fb1/attachment.html>

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

_______________________________________________
bind-users mailing list
bind-...@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users

End of bind-users Digest, Vol 2206, Issue 1
*******************************************

RE:  

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.

Yes, I have static IPs.
I do have an MX record as follows (in the zone file) . . .plus the SPF TXT record added today to make Google happy:

archaxis.net.           IN      A       123.456.789.123
            |<----I had failed to include this period (for some reason probably lost when edit-adding the SPF TXT)
archaxis.net.   IN      MX      10 archaxis.net.
archaxis.net.   IN      TXT     "v=spf1 a include:_spf.google.com ~all"

After correction of the missing period, dig now returns the following:

# dig -t MX archaxis.net

; <<>> DiG 9.10.2 <<>> -t MX archaxis.net

;; global options: +cmd
;; Got answer:

;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 41951
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;archaxis.net.                  IN      MX

;; AUTHORITY SECTION:
archaxis.net.           328     IN      SOA     archaxis.net. rtwingfield.archaxis.net. 2015092201 10800 3600 604800 3600

;; Query time: 39 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Tue Sep 22 16:29:21 CDT 2015
;; MSG SIZE  rcvd: 89

. . .but still fails.  Apparently,  this is indeed an issue to take up with AT&T.

Thanks again to all, and Lyle Giese

Ron W.

[Marc Haber]

On Tue, Sep 22, 2015 at 04:54:45PM -0500, Ron Wingfield wrote:
> 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.

Your provider has used a RFC2317 scheme to delegate the reverse DNS to
you:

81.233.202.162.in-addr.arpa. 7200 IN CNAME 81.80/29.233.202.162.in-addr.arpa.
80/29.233.202.162.in-addr.arpa. 7200 IN NS ns2.archaxis.net.
80/29.233.202.162.in-addr.arpa. 7200 IN NS ns1.archaxis.net.

so you need

zone "80/29.233.202.162.in-addr.arpa." {
...
}

Btw, this diagnosis would not have been possible if you had obfuscated
the IP address. Thanks for being open, showing your real data,
allowing swift and easy help.

Greetings
Marc


--
-----------------------------------------------------------------------------
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany | lose things." Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature | How to make an American Quilt | Fax: *49 6224 1600421