When the machine boots, it take VERY long fo rit to initialize the
interfaces and set up the routing via the network-scripts. If I include
the search domain for our domain then it can take over an hour. Our
domain's name servers are actually the same machine using aliasing.
So the only DNS servers for our domain are on the same machine
which houses the domain. In other words, everything is on the same
machine.
The problem I am having is that the machine does not seem to use
it's /etc/hosts file no matter what I put in /etc/resolv.conf . The
machines name is shogun. The hosts file has
127.0.0.1 localhost
IP# www.domain.com shogun.domain.com shogun
other IP#s ... www.bla.org
I had to put a search domain in that was not my domain, but a
stable one which the resolver can compair too on bootup and fail against.
If the search is missing then I have to wait for the timeouts while the
machine times out lookin for resolutions.
I know this could be solved easily by actually getting secondary
DNS servers or by using another machine for a primary, but I would like to
continue to use the saem machine for everything.
This all worked fine with 3.0.3, which was installed by my
predecessor. Another curious side effect which started about the same time
all this started. I had upgraded from 2.0.9 to 2.0.18 and
telnet .
ftp .
stopped working. The . used to represent the localhost. This is
all very frustrating. Any fixes for these problems?
Sean Chisham
schisham@consul-tech.com
-- To unsubscribe: mail -s unsubscribe axp-list-request@redhat.com < /dev/null
Copyright © 1995-1997 Red Hat Software. Legal notices