How to Fix Reverse DNS?

[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 at 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>
>>>          (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.Wingfield at 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?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: <https://lists.isc.org/pipermail/bind-users/attachments/20150922/8de8479c/attachment.bin>