notes@wdl1.UUCP (Notesfile maintainer) (07/13/90)
Hi, I used to get tha smae things on my suns. Yes, It has to do with the Name Server. In our case It was the nameserver was noty complete starting up when sendmail started. It modified the rc.boot and rc.local. I start in.named as soon as possible in rc.boot and then after rc.local is run, I start sendmail near the end of rc.boot. If the problem continues, put a "sleep 30" after you start the nameserver. This ensures that there is no other activity on the host for 30 seconds (or so). I had to do this on a Vax 11/780 that was our primary DNS host. Bill Lewandowski wrl@wdl1.wdl.fac.com
karl_kleinpaste@cis.ohio-state.edu (07/14/90)
If the problem with $w not being set properly is due to your
nameserver not having fully initialized, you'll find (sooner or later)
that simply waiting a little longer will not do the trick; over time,
you'll almost certainly change your configuration to make it more
complex (more host, more subdomains, doing secondary for other
domains, that sort of thing), which will take longer to initialize,
and eventually you'll get back to the same problem even if you put in
a "sleep 30."
A better solution is to start the nameserver and then just sit,
waiting for it to be able to answer queries. There's a little piece
of code called host.c writen by Chuck Hedrick/Rutgers which can be
invoked like this:
host -a -w localhost
It makes direct queries of the nameserver for the name given, and the
options tell it to ("-a") get all available info on the name, and
("-w") keep waiting and retrying the query until an answer comes back.
I use "host -a -w localhost" in my rc files immediately after starting
the nameserver. When I get output from host, I then go on to do the
interesting stuff such as starting NFS and sendmail.
You can get host from tut.cis.ohio-state.edu:pub/nameserver/host.[1c].
--karl7thSon@SLCS.SLB.COM (Chris Garrigues) (07/18/90)
From: karl_kleinpaste@cis.ohio-state.edu
Date: Fri, 13 Jul 90 15:36 CDT
I use "host -a -w localhost" in my rc files immediately after starting
the nameserver. When I get output from host, I then go on to do the
interesting stuff such as starting NFS and sendmail.
You can get host from tut.cis.ohio-state.edu:pub/nameserver/host.[1c].
What do I need to link this with to make it work?
--karl
Am I right in assuming that this will be less of a problem if I put my
local reverse mappings closer to the top of /etc/named.boot? I had my
local IN-ADDR.ARPA mappings below the seven domains (all parts of
SLB.COM) that I'm a secondary for.
Chris