Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 24 Sep 1999 10:25:14 -0400
From:      Mitch Collinsworth <mkc@Graphics.Cornell.EDU>
To:        Cliff Addy <fbsdlist@federation.addy.com>
Cc:        Dan Busarow <dan@dpcsys.com>, questions@FreeBSD.ORG
Subject:   Re: DNS setup problem, "Can't find server name" 
Message-ID:  <199909241425.AA052523114@broccoli.graphics.cornell.edu>
In-Reply-To: Your message of "Thu, 23 Sep 1999 23:04:07 EDT." <Pine.BSF.3.95q.990923225448.4580A-100000@federation.addy.com> 

next in thread | previous in thread | raw e-mail | index | archive | help

>On Thu, 23 Sep 1999, Dan Busarow wrote:
>
>> On Thu, 23 Sep 1999, Cliff Addy wrote:
>> > Actually, I think I may have found it.  The new named *insists* that
>> > certain files be located in /etc/namedb, even if named.conf tells it to
>>
>> No it doesn't.  My zone files and named.conf are in 
>> /usr/local/lib/named and everything works fine.  You can also 
>> give the hints file any name you want.  named.conf controls
>> all.  You _do_ need to tell named where to find named.conf if it's
>> not in /etc/namedb by using the -b /path/to/named.conf flag.
>
>Well, that's precisely what I *had* set up.  It was finding the named.conf
>fine, with this at the top:
>
>  options {
>      directory "/etc/named.data";
>      listen-on { 207.239.68.71; };
>  };
>
>However, the error logs stated it could not find localhost.rev.  I created
>one in /etc/named.data, but the same message showed up.  ONLY when I moved
>it to /etc/namedb did the message disappear.  According to what I
>understand of named, the option above should have kept it from looking
>anywhere but /etc/named.data

Not keep it from looking elsewhere, but default to looking there for
files without absolute paths.

>So, then I moved all my other conf files into named.data and voila, all
>worked fine.

I assume you mean /etc/namedb 

>Just out of curiousity, which version of named/bind are you
>using?  The old system is only a few months old and did not even want/need
>this "localhost.rev" file and worked fine with the identical directory
>structure I was originally using on the new box. I'm thinking this
>prediliction for /etc/namedb is unique to one version. 

I'm thinking that either a) your named wasn't reading the named.conf
you thought it was, or b) the above directory line was commented out.
Check carefully.  The v8 named accepts those dratted C-style /* */
comments that can wipe out data on multiple lines they don't even appear
on.

Do you have the 3rd edition of the cricket book, "DNS and BIND"?
There's enough difference between bind4 and bind8 configurations to
really mess you up if you don't read up and re-educate yourself.

-Mitch



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message




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