[SOLVED] Bind9: Unable to ping "domain.local" even though there are no apparent errors.

chronoloraptor · 03-25-2013, 02:48 PM

I've tried running named-checkconfig -z, and it shows all zones as loaded. Also ran it on each "named.conf" and it doesn't turn up any errors.

Any help would be appreciated!

Nmap localhost:

Code:

53/tcp  open  domain

named.conf.options:

Code:

 dnssec-validation auto;

        auth-nxdomain no;    # conform to RFC1035
        listen-on-v6 { any; };
};

named.conf.local:

Code:

//
// Do any local configuration here
//

// Consider adding the 1918 zones here, if they are not used in your
// organization
include "/etc/bind/zones.rfc1918";

zone "domain.local" {
        type master;
        file "/etc/bind/db.hnet.local";
};

zone "0.0.10.in-addr.arpa" {
        type master;
        notify no;
        file "/etc/bind/db.10";
};
~
~

db.domain.local

Code:

;
; BIND data file for hnet.local
;
$ORIGIN domain.local.

$TTL    604800
@       IN      SOA     ns.domain.local. root.domain.local. (
                      201303253         ; Serial
                         604800         ; Refresh
                          86400         ; Retry
                        2419200         ; Expire
                         604800 )       ; Negative Cache TTL
;
@       IN      NS      ns.domain.local.
ns      IN      A       10.0.0.3
box     IN      A       10.0.0.3
www     IN      A       10.0.0.4

db.10

Code:

;
; BIND reverse data file for local loopback interface
;
$TTL    604800
@       IN      SOA     ns.domain.local. root.domain.local. (
                      201303252         ; Serial
                         604800         ; Refresh
                          86400         ; Retry
                        2419200         ; Expire
                         604800 )       ; Negative Cache TTL
;
@       IN      NS      ns.
1.0.0   IN      PTR     ns.domain.local.

21      IN      PTR     www.domain.local.

acid_kewpie · 03-25-2013, 04:33 PM

As my falky reading of zone files goes.. there is no A record for "domain.local".

Don't try to just ping stuff, can you actually resolve these records directly against the domain? does www resolve?

chronoloraptor · 03-26-2013, 11:26 AM

EDIT: WAIT, IT'S WORKING! Turned out to be an issue in my resolv.conf file where it was looking it up through 8.8.8.8 rather than 10.0.0.3. nslookup did the trick.

Thanks again.

I've added

Code:

domain.local IN      A       10.0.0.3

Should've also mentioned I have tried using dig to troubleshoot, and this is the reply:

Code:

flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

When successful it should return an ANSWER for each A record as well as the A records themselves.

chrism01 · 03-28-2013, 02:31 AM

Conventionally, for a given IP, you'd use one A rec, then you'd use a CNAME record for each subsequent rec that points to the same IP
http://www.linuxtopia.org/online_boo...3-bind-zone-rr