Am getting errors with my zone files. Any pointers?

[Barry Margolin]

In article <9ilfga$eq9 at pub3.rc.vix.com>,
Dan Du Vall <sysop at quadtrax.com> wrote:
>Am getting errors with my zone files. Any pointers? Here is the latest log .
>
>Jul 12 16:48:58 quadlinux named[970]: starting (/etc/named.conf).  named
>8.2.3-REL Sat Jan 27 05:11:05 EST 2001
>^Iprospector at porky.devel.redhat.com:/usr/src/bs/BUILD/bind-8.2.3/src/bin/nam
>ed
>Jul 12 16:48:58 quadlinux named[970]: hint zone "" (IN) loaded (serial 0)
>Jul 12 16:48:58 quadlinux named[970]: Zone "quadtrax.net" (file
>db.quadtrax.net): No default TTL ($TTL <value>) set, using SOA minimum
>instead

You need to add a $TTL statement at the beginning of db.quadtrax.net to set
the default TTL.  Since you didn't, BIND is reverting to the pre-BIND8
behavior of using the MinTTL field in the SOA record as the default TTL.

>Jul 12 16:48:58 quadlinux named[970]: db.quadtrax.net: WARNING SOA refresh
>value is less than 2 * retry (3600 < 3600 * 2)

Don't worry about this.

>Jul 12 16:48:58 quadlinux named[970]: master zone "quadtrax.net" (IN) loaded
>(serial 2001070901)
>Jul 12 16:48:58 quadlinux named[970]: Zone "115.216.216.in-addr.arpa" (file
>quadtrax.net.rev): No default TTL ($TTL <value>) set, using SOA minimum
>instead

Same as above.

>Jul 12 16:48:58 quadlinux named[970]: quadtrax.net.rev:13: data
>"27.115.216.216.in-addr.arpa.216.216.in-addr.arpa" outside zone
>"115.216.216.in-addr.arpa" (ignored)
>Jul 12 16:48:58 quadlinux named[970]: quadtrax.net.rev:14: data
>"27.115.216.216.in-addr.arpa.216.216.in-addr.arpa" outside zone
>"115.216.216.in-addr.arpa" (ignored)
>Jul 12 16:48:58 quadlinux named[970]: quadtrax.net.rev:15: data
>"27.115.216.216.in-addr.arpa.216.216.in-addr.arpa" outside zone
>"115.216.216.in-addr.arpa" (ignored)
>Jul 12 16:48:58 quadlinux named[970]: quadtrax.net.rev:16: data
>"27.115.216.216.in-addr.arpa.216.216.in-addr.arpa" outside zone
>"115.216.216.in-addr.arpa" (ignored)

My guess is you have "$ORIGIN 216.216.in-addr.arpa." in the
quadtrax.net.rev file, and then you have lines like:

27.115.216.216.in-addr.arpa IN PTR ...

Since the first field doesn't end with ".", the origin is appended to it,
resulting in the name 27.115.216.216.in-addr.arpa.216.216.in-addr.arpa.
Since this file is for the 115.216.216.in-addr.arpa zone, any name that
doesn't end with that suffix doesn't belong in it.  Add the missing "."
after "arpa".

>Jul 12 16:48:58 quadlinux named[970]: master zone "115.216.216.in-addr.arpa"
>(IN) loaded (serial 2000102908)
>Jul 12 16:48:58 quadlinux named[970]: listening on [127.0.0.1].53 (lo)
>Jul 12 16:48:58 quadlinux named[970]: listening on [192.168.1.4].53 (eth0)
>Jul 12 16:48:58 quadlinux named[970]: Forwarding source address is
>[0.0.0.0].53
>Jul 12 16:48:58 quadlinux named[971]: Ready to answer queries.
>Jul 12 16:49:10 quadlinux named[971]: sysquery: findns error (NXDOMAIN) on
>ns1.granitecanyon.com.quadtrax.net?
>Jul 12 16:49:10 quadlinux named[971]: sysquery: findns error (NXDOMAIN) on
>ns2.granitecanyon.com.quadtrax.net?

In db.quadtrax.net, you have the lines:

  IN NS  ns1.granitecanyon.com
  IN NS  ns2.granitecanyon.com

Since you didn't end these hostnames with a ".", they got the zone name
appended to them, so it's as if you entered:

  IN NS  ns1.granitecanyon.com.quadtrax.net.
  IN NS  ns2.granitecanyon.com.quadtrax.net.

Obviously, these hosts don't exist.  Add the missing "." at the ends.

-- 
Barry Margolin, barmar at genuity.net
Genuity, Burlington, MA
*** DON'T SEND TECHNICAL QUESTIONS DIRECTLY TO ME, post them to newsgroups.
Please DON'T copy followups to me -- I'll assume it wasn't posted to the group.