--- Giuliano Gavazzi wrote:

> Resending as previously sent from wrong address, so it was blocked.
>
> On M 27 Oct, 2008, at 17:13 , Stephen Liu wrote:
>
> > Hi folks,
> >
> >
> > I'm following;
> > BIND
> > http://www.postfixvirtual.net/dnsbind.html#
> >
> >
> > to install and configure bind without success. The DNS server

> seems
> > not starting.
> >
> > # /usr/local/bind/sbin/named -u named -t /usr/local/bind -c
> > /etc/named.conf

>
> dear Stephen, you are starting bind with the chroot option (-t /usr/
> local/bind).
> Even if I have never used that option, I am pretty sure that means
> that any absolute path you give in the configuration file will be
> relative to that chroot (/usr/local/bind).
> So, what in the configuration file is defined as / will be
> /usr/local/
> bind in your filesystem, and what is /etc will be
> /usr/local/bind/etc.



Hi Giuliano,


You're correct. Both named.root and named.conf are on
/usr/local/bind/etc/


# ls /usr/local/bind/etc/ | grep named.conf
named.conf

ls /usr/local/bind/etc/ | grep named.root
named.root

# ls -l /usr/local/bind/etc/named.conf
-rw-r--r-- 1 root staff 231 Oct 28 12:48 /usr/local/bind/etc/named.conf

# ls -l /usr/local/bind/etc/named.root
-rw-r--r-- 1 root staff 2878 Oct 28 03:49
/usr/local/bind/etc/named.root

# grep staff /etc/group
staff:x:50:


On running the command;

# /usr/local/bind/sbin/named -u named -t /usr/local/bind -c
/etc/named.conf -g

/etc/named.conf can be found.


But /etc/named.root on the named.conf file can't be found.


# cat /usr/local/bind/etc/named.conf
options {
directory "/namedb";
version "I do not give any version info";
pid-file "/var/run/named.pid";
allow-transfer { none ;};
};

zone "." IN {
type hint;
file " /etc/named.root";
};


# find / -name namedb -type d
/usr/local/bind/namedb


# locate named.pid
No printout.



B.R.
Stephen

Send instant messages to your online friends http://uk.messenger.yahoo.com