Two domains reporting errors

/dev/rob0 rob0 at
Wed Sep 10 10:55:49 UTC 2014

I know you said, "Never mind," but you seem to be misunderstanding 
something here ...

On Tue, Sep 09, 2014 at 07:42:56PM -0600, LuKreme wrote:
> # named-checkconf -z | grep -v loaded
> master/bt.tld:3: ignoring out-of-zone data (bt.tld)
> master/bt.tld:15: ignoring out-of-zone data (
> _default/dw.tld/IN: bad zone
> master/bt.tld:16: ignoring out-of-zone data (
> zone dw.tld/IN: has 0 SOA records
> zone dw.tld/IN: has no NS records
> So, line 3 in bt.tld is the SOA line which looks as far as I can 
> tell, basically identical to every other file:

You said this several times, but at least one was significantly 

> ==> master/ <==
> $TTL 86400      ; 1 day
>              IN SOA (

You set "$ORIGIN ." so your unqualified "" is in fact 
"" (fully qualified.)

> ==> master/bt.tld <==
> $TTL 86400      ; 1 day
> bt.tld    IN SOA  bt.tld. (

Here also.

> For the second domain, I don't understand the _default/dw.tld/IN 
> error at all, and the file starts like all the others:
> # head -3  master/dw.tld 
> $TTL     86400
> @        IN      SOA     dw.tld.  (

"@" refers to the current $ORIGIN.  When a zone file is initially 
loaded, $ORIGIN is implicitly set to the name of the zone.  But you 
changed that, it's now the root!  So "@" here means ".", and no, a 
zone file with "@" is not the same as a zone file with an explicit 
owner name for the SOA.

My style recommendation: do not use $ORIGIN lines in zone files.
Whilst named does it, you do not have to copy named.  Leave out 
$ORIGIN, use @ to refer to the name of the zone, and unqualified 
owner names beneath @.

$TTL 1d
@		IN	SOA	ns hostmaster ( ...
@		IN	NS	ns
@		IN	NS	ns1
@		IN	NS	ns2
@		IN	MX	0 mail
mail		IN	A
ns		IN	A
ns1		IN	A
ns2		IN	A

Note that there are only relative names in my example.  This could 
load as any zone name.  You might want to use some fully-qualified 
names on the RHS, such as "" as the SOA RNAME.
  Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:

More information about the bind-users mailing list