bill perkins wrote:
Richard England wrote:
I have a set of 3 Linux boxes, LaptopFC6, DesktopFC5, and
DesktopFC6. On the two FC6 machines named is no longer a services (
I'm not sure who took it's place, since I'm a networking neophyte)
but everything seems to be working to allow me access to the net via
my DSL modem/router and to each of the machines from each other....
. . . except (you knew there had to be an exceptions, else why would
I bother with this)
DesktopFC5 (didius) periodically looses contact with the (net)world.
It can't be pinged, I can ssh to it, and I can't get to an external
site, at least by name. When I discovered this I fell back on my
Unix experience and restarted and named and, voila!, everything was
back in order.
I have NetworkManager running on all three machines.
I keep all three of them as close to current in updates as I can.
Can anyone tell me why named periodically goes into limbo? or tell
me how I can start to investigate this?
/var/log/messages
seems to show the following when I can no longer use the name of the
site/machine
Jan 16 23:01:03 didius NetworkManager: <WARNING>
add_ip4_config_to_named (): Could not set forwarders for zone '.'.
Error: 'No reply within specified time'.
When I restart named I get the following in /var/log/messages
Jan 16 23:00:38 didius named[2410]: shutting down: flushing changes
Jan 16 23:00:38 didius named[2410]: stopping command channel on
127.0.0.1#953
Jan 16 23:00:38 didius named[2410]: no longer listening on 127.0.0.1#53
Jan 16 23:00:38 didius named[2410]: no longer listening on
192.168.1.45#53
Jan 16 23:00:38 didius named[2410]: exiting
Jan 16 23:00:38 didius named[2532]: starting BIND 9.3.3rc2 -u named -D
Jan 16 23:00:38 didius named[2532]: found 1 CPU, using 1 worker thread
Jan 16 23:00:38 didius named[2532]: loading configuration from
'/etc/named.conf'Jan 16 23:00:38 didius named[2532]: listening on
IPv4 interface lo, 127.0.0.1#53Jan 16 23:00:38 didius named[2532]:
listening on IPv4 interface eth0, 192.168.1.45#53
Jan 16 23:00:38 didius named[2532]: command channel listening on
127.0.0.1#953
Jan 16 23:00:38 didius named[2532]: zone 0.in-addr.arpa/IN: loaded
serial 42
Jan 16 23:00:38 didius named[2532]: zone 0.0.127.in-addr.arpa/IN:
loaded serial 1997022700
Jan 16 23:00:38 didius named[2532]: zone 255.in-addr.arpa/IN: loaded
serial 42
Jan 16 23:00:38 didius named[2532]: zone
0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa/IN:
loaded serial 1997022700
Jan 16 23:00:38 didius named[2532]: zone localdomain/IN: loaded
serial 42
Jan 16 23:00:38 didius named[2532]: zone localhost/IN: loaded serial 42
Jan 16 23:00:38 didius named[2532]: D-BUS dhcdbd subscription enabled.
Jan 16 23:00:38 didius named[2532]: D-BUS service enabled.
Jan 16 23:00:38 didius named[2532]: running
Sometimes I can go for several hours with out a problem. Other times
it is a matter of minutes.
Any help gratefully appreciated.
~~R
Looks to me like you might not be configured quite right; what does
/etc/resolv.conf look like on your system? This will tell us who the
machine thinks are the local DNS servers.
Thanks Bill.
I wondered about resolv.conf and here is what it says. Note that I
have NetworkManager running:
$ cat /etc/resolv.conf
# generated by NetworkManager, do not edit!
; Use a local caching nameserver controlled by NetworkManager
search myhome.westell.com
nameserver 127.0.0.1
myhome.westell.com is the DSL modem/router . I was expecting to see
nameserver 192.168.1.1
instead of 127.0.0.1, since that is how my FC6 machine is running, but
I've not been able to determine where I should change the configuration
so this occurs. Since NetworkManager is running changing resolve.conf
directly fixes nothing since it changes it on the fly.
~~R
