Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 23 Jun 2005 03:56:26 +0300
From:      Giorgos Keramidas <keramida@ceid.upatras.gr>
To:        Gary Kline <kline@tao.thought.org>
Cc:        freebsd-questions@freebsd.org
Subject:   Re: private/internal db file question...
Message-ID:  <20050623005626.GB1523@gothmog.gr>
In-Reply-To: <20050623001343.GA63523@thought.org>
References:  <20050623001343.GA63523@thought.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On 2005-06-22 17:13, Gary Kline <kline@tao.thought.org> wrote:
> Folks,
> After years or trying, I may have my private/internal DNS db files
> working.  From a colo machine I can reach my internal servers.  One
> small question for the DNS wizards out there:: are the last
> ".in-addr.arpa" lines considered good-form?  Can I blow them away or
> uncomment them?

Strip them off.

You didn't specify which zone this file was a database for, but looking at the
commented lines it seems like it's the reverse resolution database for
10.0.0.0/8 (your internal network).  DNS records in zone files like this one
refer to addresses "relative" to the zone itself, which is probably defined as
the following in your named.conf configuration file:

    zone "0.0.10.IN-ADDR.ARPA" {
            type master;
            file "master/10.0.0.rev";
    };

This definition of the zone in named.conf declares that addresses of the form
10.0.0.X will be looked up as PTR records of X in the file "master/10.0.0.rev"
under you named server root directory, i.e.

	ADDRESS		DB-FILE				RECORD
	10.0.0.1	master/10.0.0.rev		1
	10.0.0.2	master/10.0.0.rev		2
	...
	10.0.0.254	master/10.0.0.rev		254

Usually, the most tricky part is grasping that "1.0.0.10.IN-ADDR.ARPA." is
what BIND looks up to find the name (or names) associated with the address
10.0.0.1 (note the reversed byte order of the address parts).

> ;name    ttl    class    type    data
> 1        IN    PTR    localhost
> 1       IN    PTR    sage
> 220     IN    PTR    ethic
> 247     IN    PTR    tao
> 249     IN    PTR    zen

These look mostly ok, but you may want to fix the following:

  - "localhost" is usually assigned to 127.0.0.1, not 10.0.0.1
  - the "IN" column is *NOT* the TTL (time to live) of a record

> ;
> ;;  below may not be necessary
> ;

True; they're not.

> ;;;220.0.0.10.in-addr.arpa.        IN      PTR     ethic.thought.org.
> ;;;247.0.0.10.in-addr.arpa.        IN      PTR     tao.thought.org.
> ;;;249.0.0.10.in-addr.arpa.        IN      PTR     zen.thought.org.
>
> ;;;220.0.0.10.in-addr.arpa.        IN      PTR     ethic
> ;;;247.0.0.10.in-addr.arpa.        IN      PTR     tao
> ;;;249.0.0.10.in-addr.arpa.        IN      PTR     zen

Note that O'Reilly has an excellent book ("DNS & BIND") which you may
find immensely useful in setting up practically any sort of DNS server.




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050623005626.GB1523>