0

I am trying to configure a reverse DNS zone on my new dedicated server. I have tried several things but for some reason i cannot get my reverse zone to properly resolve.

When checking my dns, i get Could not find reverse address for my.masked.ip (my.masked.ip.in-addr.arpa.). PTR record(s) for the address could not be found in the .arpa-zone. (ip6.arpa. for IPv6 addresses and in-addr.arpa. for IPv4).

Here is my reverse zone.

 @ IN SOA ns1.domain.com. support.domain.com. (
                    2013120101
                    28800 
                    604800
                    604800
                    86400 
)

                IN    NS     ns1.domain.com.
                IN    NS     ns2.domain.com.
                IN    PTR    Domain.com.
  ns1           IN    A       Ip
  ns2           IN    A       2ip

Bind9 && Ubuntu 13.10.

9
  • Did your provider actually delegate the reverse DNS to you? Dec 2, 2013 at 1:43
  • yes i believe so. I will check now. Is my dns record correct?
    – Ray Hughes
    Dec 2, 2013 at 1:44
  • 1
    There doesn't appear to be any reverse DNS delegation to you here. Contact your server provider for information on setting up reverse DNS. Dec 2, 2013 at 1:51
  • How are you able to tell?
    – Ray Hughes
    Dec 2, 2013 at 1:51
  • 1
    You need to contact Broadriver. There's nothing we can do for you right now. Dec 2, 2013 at 1:55

1 Answer 1

1

This is a strange reverse zone. I'd expect to see some of the following:

  • $ORIGIN 2.0.192.in-addr.arpa. (replace with your IP and put before PTR records but not other records). This indicates context for the PTR records.
  • Some PTR records for IPs in your subnet, such as 1 IN PTR host.example.net..
  • An additional rDNS zone with the applicable entries for IPv6

If you are using DDNS from dhcpd, you can get away without specifying any of the PTR records yourself.

If this reverse zone is for only one delegated IP address, you can ignore that; your zone will work in that case. However, you do need the delegation.

To test before you get the delegation, you can use dig. Specify dig -x @192.0.2.1 192.0.2.2 where 192.0.2.1 is your DNS server and 192.0.2.2 is the IP with rDNS (it's OK if they are the same). You should get IN PTR example.net., given your example data, assuming named.conf is also correct.

Not the answer you're looking for? Browse other questions tagged .