0

I recently created a BIND docker container, I want to make it become my test environment DNS server which can resolve multiple domains include rDNS. However, my reverse DNS settings always complain out-of-zone.

Network information:

Host: 
vboxnet0: 192.168.56.1/24
docker1: 172.16.0.1/16

DNS Docker Container:
eth0: 172.16.0.2/16

named.conf

zone "box.com." IN {
    type master;
    file "/etc/bind/box.com.zone";
    allow-update {none;};
};

zone "56.168.192-IN-ADDR.ARPA." IN {
    type master;
    file "/etc/bind/box.com.rr.zone";
    allow-update {none;};
};

zone "drive.com." IN {
    type master;
    file "/etc/bind/drive.com.zone";
    allow-update {none;};
};

zone "16.172-IN-ADDR.ARPA." IN {
    type master;
    file "/etc/bind/drive.com.rr.zone";
    allow-update {none;};
};

box.com.zone

$ORIGIN box.com.
$TTL 86400
@       IN      SOA     ns1.drive.com.        hostmaster.drive.com. (
                20190829    ; Serial
                21600       ; Refresh after 6hrs
                3600        ; Retry after 1hr
                604800      ; Expire after 1w
                86400)      ; minTTL of 1d
@         IN    NS      ns1.drive.com.
;
@         IN    A       192.168.56.20
mail      IN    A       195.168.56.20
box.com.  IN    MX  10  mail.box.com.

box.com.rr.zone

$ORIGIN 56.168.192.IN-ADDR-ARPA.
$TTL 86400
@       IN      SOA     ns1.drive.com.        hostmaster.drive.com. (
                        20180829    ; Serial
                        21600       ; Refresh after 6hrs
                        3600        ; Retry after 1h
                        604800      ; Expire after 1w
                        86400 )     ; MinTTL of 1d
;
;
56.168.192.IN-ADDR.ARPA.   IN      NS      ns1.drive.com.
20                         IN      PTR     mail.box.com.

drive.com.zone

$ORIGIN drive.com.
$TTL 86400
@       IN      SOA     ns1.drive.com.        hostmaster.drive.com. (
                20190829    ; Serial
                21600       ; Refresh after 6hrs
                3600        ; Retry after 1hr
                604800      ; Expire after 1w
                86400)      ; minTTL of 1d
            NS      ns1.drive.com.
ns1         A       172.16.0.2
;
mail        A       172.16.10.1
@           MX  10  mail.drive.com.

drive.com.rr.zone

$TTL 86400
$ORIGIN 16.172.IN-ADDR.ARPA.
@       IN      SOA     ns1.drive.com.        hostmaster.drive.com. (
                        20180829    ; Serial
                        21600       ; Refresh after 6hrs
                        3600        ; Retry after 1h
                        604800      ; Expire after 1w
                        86400 )     ; MinTTL of 1d
;
;
        IN      NS      ns1.drive.com.
2.0     IN      PTR     ns1.drive.com.
1.10    IN      PTR     mail.drive.com.

Bind Log:

...omitted...
09-Sep-2019 21:26:45.506 none:103: 'max-cache-size 90%' - setting to 14312MB (out of 15903MB)
09-Sep-2019 21:26:45.508 configuring command channel from '/etc/bind/rndc.key'
09-Sep-2019 21:26:45.508 couldn't add command channel 127.0.0.1#953: file not found
09-Sep-2019 21:26:45.508 configuring command channel from '/etc/bind/rndc.key'
09-Sep-2019 21:26:45.508 couldn't add command channel ::1#953: file not found
09-Sep-2019 21:26:45.508 not using config file logging statement for logging due to -g option
09-Sep-2019 21:26:45.508 managed-keys-zone: loaded serial 0
09-Sep-2019 21:26:45.508 /etc/bind/drive.com.rr.zone:3: ignoring out-of-zone data (16.172.IN-ADDR.ARPA)
09-Sep-2019 21:26:45.508 /etc/bind/box.com.rr.zone:3: ignoring out-of-zone data (56.168.192.IN-ADDR-ARPA)
09-Sep-2019 21:26:45.508 /etc/bind/drive.com.rr.zone:12: ignoring out-of-zone data (2.0.16.172.IN-ADDR.ARPA)
09-Sep-2019 21:26:45.508 /etc/bind/drive.com.rr.zone:13: ignoring out-of-zone data (1.10.16.172.IN-ADDR.ARPA)
09-Sep-2019 21:26:45.508 /etc/bind/box.com.rr.zone:11: ignoring out-of-zone data (56.168.192.IN-ADDR.ARPA)
09-Sep-2019 21:26:45.508 /etc/bind/box.com.rr.zone:12: ignoring out-of-zone data (20.56.168.192.IN-ADDR-ARPA)
09-Sep-2019 21:26:45.508 zone 16.172-IN-ADDR.ARPA/IN: has 0 SOA records
09-Sep-2019 21:26:45.508 zone 16.172-IN-ADDR.ARPA/IN: has no NS records
09-Sep-2019 21:26:45.508 zone 16.172-IN-ADDR.ARPA/IN: not loaded due to errors.
09-Sep-2019 21:26:45.508 zone 56.168.192-IN-ADDR.ARPA/IN: has 0 SOA records
09-Sep-2019 21:26:45.508 zone 56.168.192-IN-ADDR.ARPA/IN: has no NS records
09-Sep-2019 21:26:45.508 zone 56.168.192-IN-ADDR.ARPA/IN: not loaded due to errors.
09-Sep-2019 21:26:45.514 zone box.com/IN: loaded serial 20190829
09-Sep-2019 21:26:45.514 zone drive.com/IN: loaded serial 20190829
09-Sep-2019 21:26:45.514 all zones loaded
09-Sep-2019 21:26:45.515 running

named-checkzone

$ named-checkzone box.com box.com.zone 
zone box.com/IN: loaded serial 20190829
OK

$ named-checkzone drive.com drive.com.zone 
zone drive.com/IN: loaded serial 20190829
OK

$ named-checkzone 56.168.192.IN-ADDR-ARPA box.com.rr.zone 
box.com.rr.zone:11: ignoring out-of-zone data (56.168.192.IN-ADDR.ARPA)
zone 56.168.192.IN-ADDR-ARPA/IN: has no NS records
zone 56.168.192.IN-ADDR-ARPA/IN: not loaded due to errors.

$ named-checkzone 16.172.IN-ADDR.ARP drive.com.rr.zone 
drive.com.rr.zone:3: ignoring out-of-zone data (16.172.IN-ADDR.ARPA)
drive.com.rr.zone:12: ignoring out-of-zone data (2.0.16.172.IN-ADDR.ARPA)
drive.com.rr.zone:13: ignoring out-of-zone data (1.10.16.172.IN-ADDR.ARPA)
zone 16.172.IN-ADDR.ARP/IN: has 0 SOA records
zone 16.172.IN-ADDR.ARP/IN: has no NS records
zone 16.172.IN-ADDR.ARP/IN: not loaded due to errors.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.