When this message happens name service times out.

[Jim Reid]

>>>>> "Mark" == Cinense, Mark <macinen at sandia.gov> writes:

    Mark> May 9 07:04:40 ns4 named[22432]: There may be a name server already running on [127.0.0.1].53
    Mark> May 9 07:04:40 ns4 named[22432]: deleting interface [127.0.0.1].53 May 9 07:06:40

Now these messages *are* self-explanatory. You're probably running two
name servers for some reason. The first one starts a listener on port
53 of the loopback interface, 127.0.0.1. The second one complains
because it can't do that because something has already bound to that
address and port number. When the second name server process realises
its attempt to bind() to port 53 of 127.0.0.1, it gives up trying to
use that interface. The same thing then happens for tne name server's
actual network interface, 134.253.16.5 and then the name server prints
the message "not listening on any interfaces" and does nothing except
try to bind to those interfaces every so often.

You've probably got an error in the /etc/rc scripts which causes two
name server processes to get started at boot time.