resolv.conf

[Chris]

On Saturday 13 August 2005 01:40 pm, /dev/rob0 wrote:
> On Saturday 2005-August-13 12:46, Chris wrote:
> > I actually have two questions, the first being about my
> > /etc/resolv.conf.  I have in it 127.0.0.1 and the two addresses of
> > Earthlinks DNS servers.  Should all three be there?  Also, when I
>
> By having the ISP nameservers listed you will gain protection from
> failures of your local nameserver. That sounds good, but I think it's
> actually bad. A properly-running nameserver on working hardware and a
> properly-configured OS should be quite reliable, likely more so than
> your ISP's caching nameservers!
>
> With ONLY 127.0.0.1 listed, DNS failures are easier to see and to fix.

Thanks, I'll go back to 127.0.0.1 then

> > added the other two addresses I restarted named with service named
> > restart and the following was noted:
>
> Settings in resolv.conf control the system C libraries' resolver
> functions. This is entirely unrelated to BIND.
>
> > Stopping named: rndc: connection to remote host closed
> > This may indicate that the remote server is using an older version of
> > the command protocol, this host is not authorized to connect,
> > or the key is invalid.
> >
> > What might possibly be causing this?
>
> Perhaps named wasn't running, or you've configured it to reject rndc(8)
> connections from localhost, or the key is not valid. Any error
> conditions will be logged at syslog priority WARN or higher.

How about the fact that I neglected to place my rndc.key in the rndc.conf 
file.  Once that was entered the above error disappeared when restarting 
named.

Thanks for the help

-- 
Chris
Registered Linux User 283774 http://counter.li.org
15:49:39 up 10 days, 25 min, 2 users, load average: 1.30, 0.73, 0.36
Mandriva Linux 10.1 Official, kernel 2.6.8.1-12mdk