Date: Fri, 21 Aug 2009 21:37:19 -0700 From: Nerius Landys <nlandys@gmail.com> To: FreeBSD Mailing List <freebsd-questions@freebsd.org> Subject: /etc/rc.d/named dilemma Message-ID: <560f92640908212137h7bd235bcqbcf6d7a727abf6e5@mail.gmail.com>
next in thread | raw e-mail | index | archive | help
I am trying to figure out why DNS lookups are not possible right after
the "named" process has been launched (during bootup). I am kind of a
newb at diagnosing these sorts of issues, but as an attempt to figure
out what's wrong, I added the following lines to the very bottom of my
/etc/rc.d/named:
case "$1" in
*start)
sleep 5
cat /etc/resolv.conf
ping -c 4 127.0.0.1
host google.com || true
;;
esac
And so, during bootup, I get the following messages, as expected:
Starting named.
domain nerius.com
nameserver 127.0.0.1
PING 127.0.0.1 ....
64 bytes from 127.0.0.1: icmp.....
...
4 packets transmitted, 4 packets received...
...
;; connection timed out; no servers could be reached
The last line is what I don't understand. named is listening on
127.0.0.1, and normal lookups can be done fine after bootup. Then why
can't I do a lookup right after named starts?
By the way, the underlying issue that I'm trying to address is that
ntpdate, which comes right after named in the boot sequence, is not
able to resolve the DNS for the time servers.
Thx.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?560f92640908212137h7bd235bcqbcf6d7a727abf6e5>