Bind IP reverse

U

urbee

Verified User
Joined
Mar 27, 2009
Messages
118
Hello,

we're trying to set up reverse on our /24 IP class but cannot find any usefull information on directadmin forums. As we own our IPs we need to add the appropriate authority in RIPE database. We're currently getting the following error:

***RDNS: (related to set) ERROR (20 points): The glue nameserver
ns2.domain.com must be within the domain that is being
delegated.

***RDNS: (related to set) ERROR (20 points): The glue nameserver
ns1.domain.com must be within the domain that is being
delegated.

***RDNS: (related to ns1.domain.com) ERROR (20 points): Could not
get an SOA record from ns1.domain.com (xxx.xxx.xxx.xxx).

***RDNS: (related to ns2.domain.com) ERROR (20 points): Could not
get an SOA record from ns2.domain.com (xxx.xxx.xxx.xxx).

I am guessing that something needs to be changed in named.conf to let RIPE know that the servers are ready but not sure what. I checked the directadmin reverse guide but i only got confused and i think that doesnt yet apply to us.

Thanks for all your help in advance
 
Hello,

PTR records for IP subnet can be set with named+directadmin without any modification to any of them. So you might be doing anything wrong. Show your zone file so we could check it.
 
Okay, i think i managed to fix it. I added some manual entries for the x.x.x.in-addr.arpa and created a new .db file manually. Seems to work now.

I'm guessing i was able to do this with directadmin also.. but i'm also guessing that adding it directly to named.conf isnt an issue? Directadmin wont rewrite it or anything?

Here's what i added if anyone has a similar question:

To named.conf:

Code: 
zone "1.168.192.in-addr.arpa" {
        type master;
        file "/etc/bind/1.168.192.in-addr.arpa.db";
};

And then in /etc/bind/1.168.192.in-addr.arpa.db file:

Code: 
$TTL 100
@       IN      SOA     ns1.domain.com.      root.domain.com. (
                                                2012020301
                                                100
                                                3600
                                                1209600
                                                86400 )

1.168.192.in-addr.arpa.        100     IN      NS      ns1.domain.com.
1.168.192.in-addr.arpa.        100     IN      NS      ns2.domain.com.

I'm guessing this is correct, if anyone can verify? The 192.168.1 IP is an example IP ofcourse.

This was added to both of my named.conf (i use multi server setup).
 
Ok on the second thought maybe i wasnt able to do this with DirectAdmin.

I needed to add a zone for 192.168.1 IP class and this created a 1.168.192.in-addr.arpa zone in DNS management - i couldnt of created this with directadmin as its not a full IP address. Also, i didnt need any PTR records on it, just two NS.

This needed to be done to make authority over the IP class from my two nameservers.

If i try to add a zone with 192.168.1 IP with directadmin it tells me i need a vailid IP,domain and NS.
 
If i try to add a zone with 192.168.1 IP with directadmin it tells me i need a vailid IP,domain and NS.
Click to expand...
That's normal behaviour. These are local (private) ip addresses, not to be used on the external internet. You should use real ip addresses.
 
Directadmin requires full formated IP 192.168.1.0 to be entered.
Later you'll be able to modify it via SSH, it means you should create Reverse IP Lookup for 192.168.1.0, and then update files and zone via SSH.
 
Richard G said:
That's normal behaviour. These are local (private) ip addresses, not to be used on the external internet. You should use real ip addresses.
Click to expand...

Directadmin does not forbid usage of local (private) ip addresses either with DNS or with Apache.
 
As i said this is just as an example. I'm not really using local ips on directadmin :)
 
Hi Jeff,

we already solved the issue and the solution (config) looks very much like ours but thanks for the post and the "howto" on reverse dns, i'm sure it will be helpfull to others also in the future!

There's really not much on reverse dns on directadmin forums atleast on how to set up the zone file for xxx.xxx.xxx (the whole class).
 
Well, there is now, but my bet is that most DirectAdmin users won't need it, as most of us don't have our own allocations. I've moved my post; it's now a How-To.

Jeff
 
You must log in or register to reply here.
Back
Top