HELP! DNS woes

HELP! DNS woes

Post by Joe Hylkem » Thu, 12 Sep 2002 00:04:19



I hope somebody can tell me what I'm doing wrong with getting DNS to work.

I upgrade to bind9 on my OpenBSD box and run the bind9-enable script.  I
put the config files in /var/named.  I attempt to start bind with the
"named" command.  It only lets me do it as a non-privileged user.  So, I
attempt to chroot() it, and I get "chroot(): Operation not permitted."
Then, I attempt to chroot() it as root and it cannot find the "named"
executable - even when I switch to the directory it's in!

Finally, I break down and copy /var/named/etc/named.conf to /etc.  I run
it (as a nonprivileged user, the only way it will take it) and, after it
*es about some syntax errors which I correct, I try again.  This time,
I get, in /var/log/messages:

Sep 11 00:04:26 chianti named[26863]: starting BIND 9.2.0
Sep 11 00:04:26 chianti named[26863]: could not listen on UDP socket:
permission denied
Sep 11 00:04:26 chianti named[26863]: creating IPv4 interface lo0 failed;
interface ignored
Sep 11 00:04:26 chianti named[26863]: could not listen on UDP socket:
permission denied
Sep 11 00:04:26 chianti named[26863]: creating IPv4 interface sis0 failed;
interface ignored
Sep 11 00:04:26 chianti named[26863]: not listening on any interfaces
Sep 11 00:04:27 chianti named[26863]: could not configure root hints from
'db.cache': file not found
Sep 11 00:04:27 chianti named[26863]: loading configuration: file not fou


PLEASE HELP!

Thanks.

 
 
 

HELP! DNS woes

Post by Dave Uhrin » Fri, 13 Sep 2002 01:13:23



> I hope somebody can tell me what I'm doing wrong with getting DNS to
> work.

> I upgrade to bind9 on my OpenBSD box and run the bind9-enable script.
> I
> put the config files in /var/named.  I attempt to start bind with the
> "named" command.  It only lets me do it as a non-privileged user.  So,
> I attempt to chroot() it, and I get "chroot(): Operation not
> permitted." Then, I attempt to chroot() it as root and it cannot find
> the "named" executable - even when I switch to the directory it's in!

To enable the chroot with BIND you have to invoke the daemon as root
thus:

# /usr/local/sbin/named -u named -t /var/named

The named.conf file MUST be in /var/named/etc and that file should
contain the lines:

[/var/named/etc]# cat named.conf
options {
        directory "/namedb";
        pid-file "/var/run/named.pid";
        };

/var/run/var/run must be owned by the user 'named' so that the PID can
be written.  The zone files must then be in /var/named/namedb.

/var/named/etc should also contain the localtime file copied from the
appropriate directory in /usr/share/zoneinfo.

Quote:> Finally, I break down and copy /var/named/etc/named.conf to /etc.  I
> run it (as a nonprivileged user, the only way it will take it) and,
> after it
> *es about some syntax errors which I correct, I try again.  This
> time, I get, in /var/log/messages:

> Sep 11 00:04:26 chianti named[26863]: starting BIND 9.2.0
> Sep 11 00:04:26 chianti named[26863]: could not listen on UDP socket:
> permission denied
> Sep 11 00:04:26 chianti named[26863]: creating IPv4 interface lo0
> failed; interface ignored
> Sep 11 00:04:26 chianti named[26863]: could not listen on UDP socket:
> permission denied
> Sep 11 00:04:26 chianti named[26863]: creating IPv4 interface sis0
> failed; interface ignored
> Sep 11 00:04:26 chianti named[26863]: not listening on any interfaces
> Sep 11 00:04:27 chianti named[26863]: could not configure root hints
> from 'db.cache': file not found

                   ^^^^^^^^^^^^^^

Because you have moved your files!

 
 
 

1. CD-RW mounting woes in Mandrake 7.0 woe oh woe oh woe!

I hate to ask the often answered, but I have a TDK VeloCD CD-RW in my PII
233 machine installed as a master on the secondary IDE. I'm running
Mandrake-linux 7.0, and of course I get the bad link problem. I have run the
fix suggested on Mandrake's Web-page, but I can't figure a way to make the
fix either permenant or automatic. The fix (in case you haven't seen it is
to run "cdrecord -scanbus" to check for the presence of a working CD-RW,
then to type "cd /dev && rm cdrom && ln -s scd0 cdrom" in a terminal) This
fix works but there's got to be a better way...any thoughts.

2. uuencode/uudecode-specification

3. XF86 Config set-up woes & woes & woes

4. Welcome to comp.unix.shell [Biweekly posting]

5. DNS and sendmail woes

6. Can't boot

7. DNS woes

8. Please Help me!

9. errr... help help help! modem woes

10. DNS zone file woes

11. Netscape DNS woes