newbie quest bought the book but need help

Pete Ehlke pde at ehlke.net
Sat Jul 27 13:18:58 UTC 2002


On Fri, Jul 26, 2002 at 09:33:09PM -0700, rickster wrote:
> 
> Bought DNS and Bind but need help?
> Get the following error 
> 
> Jul 26 21:17:52 gate named[1567]: dns_master_load: ihomesforyou.db:3:
> ignoring out-of-zone data (ihomesforyou.com)
> Jul 26 21:17:52 gate named[1567]: zone 67.112.164.in-addr.arpa/IN:
> could not find NS and/or SOA records
> Jul 26 21:17:52 gate named[1567]: zone 67.112.164.in-addr.arpa/IN: has
> 0 SOA records
> Jul 26 21:17:52 gate named[1567]: zone 67.112.164.in-addr.arpa/IN: has
> no NS records
> Jul 26 21:17:52 gate named[1567]: dns_master_load: db.ihomesforyou:3:
> ihomesforyou.com.ihomesforyou.com: not at top of zone
> Jul 26 21:17:52 gate named[1567]: zone ihomesforyou.com/IN: loading
> master file db.ihomesforyou: not at top of zone
> 
> named.conf
> 
> zone "ihomesforyou.com" in {
> type master;
> notify no;
> file "db.ihomesforyou";
        ^^^^^^^^^^^^^^^

> };
> 
> zone "67.112.164.in-addr.arpa" {
>            type master;
>            file "ihomesforyou.db";
                   ^^^^^^^^^^^^^^^

Just a stylistic point here: this seems incredibly confusing. You can
call your zone file "the-man-in-the-moon" if you want to, it doesn't
really matter, but most people have their zone file names encode the
zone that they represent.

>                            /* This is an example entry for a generic
>                             * subnet, it's syntax will be the same as
>                             * the localhost.db as they serve similar
>                             * functions
>                             */
>    };
> 
>  db.ihomesforyou
> $TTL    86400
> $ORIGIN ihomesforyou.com
          
You define the zone as ihomesforyou.com, but then you explicitly set the
origin to a string that is not dot-terminated. The defined origin is
always appended to non-terminated data, so from this point forward, you
are defining records for ihomesforyou.com.ihomesforyou.com. Either
delete this $ORIGIN statement, or dot-terminate it.

> @       IN      SOA     ns1.ihomesforyou.com. ns2.ihomesforyou.com. (
>                         1 ; Serial, todays date + todays serial
>                         80000      ; Refresh
>                         20000   ; Retry
>                         604800      ; Expire
>                         86400
>                           )     ; Minimum TTL
> 
> ihomesforyou.com. IN NS ns1.ihomesforyou.com.
> ihomesforyou.com. IN NS ns2.ihomesforyou.com.
> ns1.ihomesforyou.com. IN A 67.112.164.194
> ns2.ihomesforyou.com. IN A 67.112.164.194
> 
Since these records are dot-terminated, and are not within your current
origin of ihomesforyou.com.ihomesforyou.com, they are rejected.

> ihomesforyou.db
> 
> $TTL    86400
> $ORIGIN ihomesforyou.com.

This zone was defined as 67.112.164.in-addr.arpa, but now you're
restting the origin to ihomesforyou.com. Why?

> @       IN      SOA     ns1.ihomesforyou.com. ns2.ihomesforyou.com. (
>                         1 ; Serial, todays date + todays serial
>                         80000      ; Refresh
>                         20000   ; Retry
>                         604800      ; Expire
>                         86400
>                           )     ; Minimum TTL
>          NS        ns1.ihomesforyou.com.


More information about the bind-users mailing list