Re: How to Fix Reverse DNS?

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

Re: How to Fix Reverse DNS?

You don't fix this, AT 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 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

Re: How to Fix Reverse DNS?

- 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

Re: How to Fix Reverse DNS?

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's U-verse . . .has been a painful

How to Fix Reverse DNS?

RE:  BIND v9.10.2 I have recently converted from a "legacy" DSL service to AT's U-verse . . .has been a painful experience.  Heretofore, the following from /var/named/named.conf zone "233.202.162.in-addr.arpa" {    

Options for non-recursive servers

for non-recursive (authoritative only) servers I have: options { directory "/var/cache/bind"; allow-query { any; }; allow-query-cache { none; }; allow-recursion { none; }; listen-on { 127.0.0.1; }; listen-on { 172.26.99.117; }; listen-on-v6

How to Fix Reverse DNS?

On 9/22/2015 2:25 PM, bind-users-requ...@lists.isc.org wrote: Message: 5 Date: Tue, 22 Sep 2015 14:24:57 -0500 From: Lyle Giese To: bind-users@lists.isc.org Subject: Re: How to Fix Reverse DNS? Message-ID: