Help setting a DNS server.

[Wagner Garcia Campagner]

Hello,

Thanks for all the help.
I think now the DNS server is running all right.
I'm using the chroot enviroment. And i specified an include "/etc/rndc.key";
entry in the named.conf file.... it is working and answering the requests of 
my domain (patchwork.com.br).

Thanks again for all the help...

Next thing is that i want to add my ISP DNS as a forwarder.

I included the following lines inside the options section of my named.conf 
file:

forward first;
forwarders {
200.204.0.10
};

But when i do it and dig some domain, i get a wrong answer... i think i'll 
not use forward....

Thanks,
Wagner.



>From: "Sandifer, Stephen (DISA Oklahoma City)" 
<SSandifer at okc.disa.mil>
>To: "'edwardspl at ita.org.mo'" <edwardspl at ita.org.mo>, 
Wagner Garcia Campagner <wcampagner at hotmail.com>
>CC: bind-users at isc.org
>Subject: RE: Help setting a DNS server.
>Date: Tue, 17 Aug 2004 13:53:34 -0500
>
>
>
> > -----Original Message-----
> > From: edwardspl at ita.org.mo [mailto:edwardspl at ita.org.mo]
> > Sent: Tuesday, August 17, 2004 12:34
> > To: Wagner Garcia Campagner
> > Cc: bind-users at isc.org
> > Subject: Re: Help setting a DNS server.
> >
> >
> > Wagner Garcia Campagner wrote:
> >
> > > Hello Danny,
> > >
> > > Thanks, i found another two named.conf files:
> > >
> > > /var/named/chroot/etc/named.conf
> > > /var/named/chroot/var/named/chroot/etc/named.conf
> > >
> > > so i copied the /etc/named.conf find to this two files and
> > now i get the
> > > following error in the /var/log/messages:
> > >
> > > Aug 17 11:34:34 wawa named[9883]: starting BIND 9.2.2-P3 -u 
named -t
> > > /var/named/chroot
> > > Aug 17 11:34:34 wawa named[9883]: using 1 CPU
> > > Aug 17 11:34:34 wawa named[9883]: loading configuration from
> > > '/etc/named.conf'
> > > Aug 17 11:34:34 wawa named[9883]: no IPv6 interfaces found
> > > Aug 17 11:34:34 wawa named[9883]: listening on IPv4 interface 
lo,
> > > 127.0.0.1#53
> > > Aug 17 11:34:34 wawa named[9883]: listening on IPv4 interface 
eth0,
> > > 200.161.16.93#53
> > > Aug 17 11:34:34 wawa named[9883]: listening on IPv4 interface 
eth1,
> > > 192.168.10.1#53
> > > Aug 17 12:34:34 wawa named: named startup succeeded
> > > Aug 17 11:34:34 wawa named[9883]: /etc/named.conf:21:
> > couldn't find key
> > > 'rndc_key' for use with command channel 127.0.0.1#953
> > > Aug 17 11:34:34 wawa named[9883]: command channel listening
> > on 127.0.0.1#953
> > > Aug 17 11:34:34 wawa named[9883]: zone
> > 0.0.127.in-addr.arpa/IN: loaded
> > > serial 1997022700
> > > Aug 17 11:34:34 wawa named[9883]: zone localhost/IN: loaded
> > serial 42
> > > Aug 17 11:34:34 wawa named[9883]: running
> > >
> > > Is there a any to configure named to look in the
> > /etc/named.conf file
> > > instead of these other files???
> > >
> > > Thanks a lot in advance,
> > > Wagner.
> >
> > Please sure is there "rndc_key" in your system !
> >
>No, not quite right.  Wagner, the first thing you'll have to decide is 
if
>you wish to run BIND 9.2.2 as "named" in a chroot'ed 
environment, or as
>"root" in a regular environment.  You can find many resources 
on the
>Internet to make that choice, though you should choose the chroot option 
if
>you can.
>
>The reason you have /var/named/chroot/etc and
>/var/named/chroot/var/named/chroot/etc is the way BIND was compiled to 
look
>for its rndc key file.  Mark can provide gory details about why this was
>done.
>
>The main thing you should be looking for is an "rndc_key" 
statement on line
>21 of your "named.conf" file. This construction was allowed 
for
>BIND8-backwards-compatibility, and has been devalued.  What you should 
do is
>cut those lines into a separate file, "rndc.conf".  You may 
place this under
>/etc or under /var/named/chroot/etc, depending on your answer to the 
first
>question.  BIND will quit looking for a key, and start properly.

_________________________________________________________________
MSN Messenger: instale grátis e converse com seus amigos. 
http://messenger.msn.com.br