Re: named[353]: sysquery: no addrs found for root NS ..........
On Wed, 8 Sep 2004 07:28:11 +0900 horio shoichi <[EMAIL PROTECTED]> wrote: > On Tue, 7 Sep 2004 14:24:37 +0300 > "Toomas Aas" <[EMAIL PROTECTED]> wrote: > > Hi! > > > > > >From time to time I get this: > > > > > > Sep 7 12:57:44 it named[353]: sysquery: no addrs found for root NS > > > (d.root-servers.net) > > > Sep 7 12:57:44 it named[353]: sysquery: no addrs found for root NS > > > (a.root-servers.net) > > > Sep 7 12:57:44 it named[353]: sysquery: no addrs found for root NS > > > (c.root-servers.net) > > > Sep 7 12:57:45 it named[353]: sysquery: no addrs found for root NS > > > (h.root-servers.net) > > > Sep 7 12:57:45 it named[353]: sysquery: no addrs found for root NS > > > (f.root-servers.net) > > > Sep 7 12:57:45 it named[353]: sysquery: no addrs found for root NS > > > (b.root-servers.net) > > > > > > > This problem plagued me for a long time on several FreeBSD 4 servers > > running BIND 8 from the base system. Google finds numerous discussions > > on this problem in various lists/newsgroups but a solution is rarely > > offered. > > > > Finally, I found someone's theory in a NetBSD (or was it OpenBSD) > > forum. I can't tell whether it is true or not, but it makes sense > > to me. > > > > If your BIND is configured to use a forwarder and this forwarder is > > really good then BIND (almost) never needs to contact the root servers. > > The root zone times out in memory and it is not reloaded from disk. It > > is only loaded when BIND is started. Thus, if your BIND finally needs > > to contact a root name server after a long time of getting all > > responses from forwarder, it turns out that the data for root zone is > > not available... > > > > Now, as I said, I cannot tell whether this theory is true or not. What > > I can say is that on all 4 machines where I run BIND I configured > > one of two workarounds: > > - use "forward only" so you *never* need to check the root zone > > - do not use forwarders at all so you check the root zone fairly > > frequently. > > > > I did this almost a year ago, and after that I never have had this > > problem again. HTH. > > Hmm, then the easiest cure against OP's would be > periodically (say, per week) requesting purposely > wrong request (e.g., nslookup example.heh) ? Actually the uptime was 3 days (I've upgraded to 5.3B3) and I'm _sure_ to have entered some non-existent addresses in my web browser. -- IOnut Unregistered ;) FreeBSD "user" 5.3-BETA3 - try `sysctl debug.witness_watch=0` and prepare to fly :-) ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: named[353]: sysquery: no addrs found for root NS ..........
On Tue, 7 Sep 2004 14:24:37 +0300 "Toomas Aas" <[EMAIL PROTECTED]> wrote: > Hi! > > > >From time to time I get this: > > > > Sep 7 12:57:44 it named[353]: sysquery: no addrs found for root NS > > (d.root-servers.net) > > Sep 7 12:57:44 it named[353]: sysquery: no addrs found for root NS > > (a.root-servers.net) > > Sep 7 12:57:44 it named[353]: sysquery: no addrs found for root NS > > (c.root-servers.net) > > Sep 7 12:57:45 it named[353]: sysquery: no addrs found for root NS > > (h.root-servers.net) > > Sep 7 12:57:45 it named[353]: sysquery: no addrs found for root NS > > (f.root-servers.net) > > Sep 7 12:57:45 it named[353]: sysquery: no addrs found for root NS > > (b.root-servers.net) > > > > This problem plagued me for a long time on several FreeBSD 4 servers > running BIND 8 from the base system. Google finds numerous discussions > on this problem in various lists/newsgroups but a solution is rarely > offered. > > Finally, I found someone's theory in a NetBSD (or was it OpenBSD) > forum. I can't tell whether it is true or not, but it makes sense > to me. > > If your BIND is configured to use a forwarder and this forwarder is > really good then BIND (almost) never needs to contact the root servers. > The root zone times out in memory and it is not reloaded from disk. It > is only loaded when BIND is started. Thus, if your BIND finally needs > to contact a root name server after a long time of getting all > responses from forwarder, it turns out that the data for root zone is > not available... > > Now, as I said, I cannot tell whether this theory is true or not. What > I can say is that on all 4 machines where I run BIND I configured > one of two workarounds: > - use "forward only" so you *never* need to check the root zone > - do not use forwarders at all so you check the root zone fairly > frequently. > > I did this almost a year ago, and after that I never have had this > problem again. HTH. > -- > Toomas Aas | [EMAIL PROTECTED] | http://www.raad.tartu.ee/~toomas/ > * Press any key to continue or any other key to quit. > > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > Hmm, then the easiest cure against OP's would be periodically (say, per week) requesting purposely wrong request (e.g., nslookup example.heh) ? horio shoichi ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: named[353]: sysquery: no addrs found for root NS ..........
On Tue, 7 Sep 2004 14:41:08 +0200 "Robert Eckardt" <[EMAIL PROTECTED]> wrote: > On Tue, 7 Sep 2004 13:07:05 +0300, Ion-Mihai Tetcu wrote > > On Tue, 7 Sep 2004 13:00:47 +0300 > > Ion-Mihai Tetcu <[EMAIL PROTECTED]> wrote: > > > > > Hi, > > > > > > > > > From time to time I get this: > > > > > > Sep 7 12:57:44 it named[353]: sysquery: no addrs found for root NS > (d.root-servers.net) > > > Sep 7 12:57:44 it named[353]: sysquery: no addrs found for root NS > (a.root-servers.net) > > > Sep 7 12:57:44 it named[353]: sysquery: no addrs found for root NS > (c.root-servers.net) > > Hi, > > I had the same problem a while ago. > I had configured my ISP's name-server (actually several of them) to > forward requests to. It happened that one of them became unreachable. > From (just quickly) looking at the source, I found that named ends in > this very loop as it does not try to actually request adresses for the > root name-servers but rather writes out error messages. Kinda' funny since it has named.root handy. > The funny thing was that the forwarders are managed in the same list > as the root servers. > After removing any forwarders from my named-config and relying > completely on the root servers I never had the problem again. > (Before this it happend after a few hours up to several weeks of > named's run-time.) Yes that what was happening here too; and that loop nice loaded the system. Thanks. BTW, 5.3 with debug.witness_watch=0 just rocks; the load is a half :) -- IOnut Unregistered ;) FreeBSD "user" ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: named[353]: sysquery: no addrs found for root NS ..........
On Tue, 7 Sep 2004 13:07:05 +0300, Ion-Mihai Tetcu wrote > On Tue, 7 Sep 2004 13:00:47 +0300 > Ion-Mihai Tetcu <[EMAIL PROTECTED]> wrote: > > > Hi, > > > > > > From time to time I get this: > > > > Sep 7 12:57:44 it named[353]: sysquery: no addrs found for root NS (d.root-servers.net) > > Sep 7 12:57:44 it named[353]: sysquery: no addrs found for root NS (a.root-servers.net) > > Sep 7 12:57:44 it named[353]: sysquery: no addrs found for root NS (c.root-servers.net) Hi, I had the same problem a while ago. I had configured my ISP's name-server (actually several of them) to forward requests to. It happened that one of them became unreachable. >From (just quickly) looking at the source, I found that named ends in this very loop as it does not try to actually request adresses for the root name-servers but rather writes out error messages. The funny thing was that the forwarders are managed in the same list as the root servers. After removing any forwarders from my named-config and relying completely on the root servers I never had the problem again. (Before this it happend after a few hours up to several weeks of named's run-time.) Regards, Robert ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: named[353]: sysquery: no addrs found for root NS ..........
On Tue, 7 Sep 2004 14:24:37 +0300 "Toomas Aas" <[EMAIL PROTECTED]> wrote: > Hi! > > > >From time to time I get this: > > > > Sep 7 12:57:44 it named[353]: sysquery: no addrs found for root NS > > (d.root-servers.net) > > Sep 7 12:57:44 it named[353]: sysquery: no addrs found for root NS > > (a.root-servers.net) > > Sep 7 12:57:44 it named[353]: sysquery: no addrs found for root NS > > (c.root-servers.net) > > Sep 7 12:57:45 it named[353]: sysquery: no addrs found for root NS > > (h.root-servers.net) > > Sep 7 12:57:45 it named[353]: sysquery: no addrs found for root NS > > (f.root-servers.net) > > Sep 7 12:57:45 it named[353]: sysquery: no addrs found for root NS > > (b.root-servers.net) > > > > This problem plagued me for a long time on several FreeBSD 4 servers > running BIND 8 from the base system. Google finds numerous discussions > on this problem in various lists/newsgroups but a solution is rarely > offered. > > Finally, I found someone's theory in a NetBSD (or was it OpenBSD) > forum. I can't tell whether it is true or not, but it makes sense > to me. > > If your BIND is configured to use a forwarder and this forwarder is > really good then BIND (almost) never needs to contact the root servers. > The root zone times out in memory and it is not reloaded from disk. It > is only loaded when BIND is started. Thus, if your BIND finally needs > to contact a root name server after a long time of getting all > responses from forwarder, it turns out that the data for root zone is > not available... > > Now, as I said, I cannot tell whether this theory is true or not. What > I can say is that on all 4 machines where I run BIND I configured > one of two workarounds: > - use "forward only" so you *never* need to check the root zone > - do not use forwarders at all so you check the root zone fairly > frequently. It makes some sense; I have a forwarder on the LAN router that doesn't do much besides routing and dns caching. Thanks. -- IOnut Unregistered ;) FreeBSD "user" ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: named[353]: sysquery: no addrs found for root NS ..........
Hi! > >From time to time I get this: > > Sep 7 12:57:44 it named[353]: sysquery: no addrs found for root NS > (d.root-servers.net) > Sep 7 12:57:44 it named[353]: sysquery: no addrs found for root NS > (a.root-servers.net) > Sep 7 12:57:44 it named[353]: sysquery: no addrs found for root NS > (c.root-servers.net) > Sep 7 12:57:45 it named[353]: sysquery: no addrs found for root NS > (h.root-servers.net) > Sep 7 12:57:45 it named[353]: sysquery: no addrs found for root NS > (f.root-servers.net) > Sep 7 12:57:45 it named[353]: sysquery: no addrs found for root NS > (b.root-servers.net) > This problem plagued me for a long time on several FreeBSD 4 servers running BIND 8 from the base system. Google finds numerous discussions on this problem in various lists/newsgroups but a solution is rarely offered. Finally, I found someone's theory in a NetBSD (or was it OpenBSD) forum. I can't tell whether it is true or not, but it makes sense to me. If your BIND is configured to use a forwarder and this forwarder is really good then BIND (almost) never needs to contact the root servers. The root zone times out in memory and it is not reloaded from disk. It is only loaded when BIND is started. Thus, if your BIND finally needs to contact a root name server after a long time of getting all responses from forwarder, it turns out that the data for root zone is not available... Now, as I said, I cannot tell whether this theory is true or not. What I can say is that on all 4 machines where I run BIND I configured one of two workarounds: - use "forward only" so you *never* need to check the root zone - do not use forwarders at all so you check the root zone fairly frequently. I did this almost a year ago, and after that I never have had this problem again. HTH. -- Toomas Aas | [EMAIL PROTECTED] | http://www.raad.tartu.ee/~toomas/ * Press any key to continue or any other key to quit. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: named[353]: sysquery: no addrs found for root NS ..........
On Tue, 7 Sep 2004 13:00:47 +0300 Ion-Mihai Tetcu <[EMAIL PROTECTED]> wrote: > Hi, > > > From time to time I get this: > > Sep 7 12:57:44 it named[353]: sysquery: no addrs found for root NS > (d.root-servers.net) > Sep 7 12:57:44 it named[353]: sysquery: no addrs found for root NS > (a.root-servers.net) > Sep 7 12:57:44 it named[353]: sysquery: no addrs found for root NS > (c.root-servers.net) > Sep 7 12:57:45 it named[353]: sysquery: no addrs found for root NS > (h.root-servers.net) > Sep 7 12:57:45 it named[353]: sysquery: no addrs found for root NS > (f.root-servers.net) > Sep 7 12:57:45 it named[353]: sysquery: no addrs found for root NS > (b.root-servers.net) > > Doing here a named.reload and : Actually it requires a named.restart, a reload only makes it work for a couple of seconds and the it starts again. Sep 7 13:03:25 it named[15916]: starting (/etc/namedb/named.conf). named 8.3.7-REL Mon Aug 30 13: 23:41 EEST 2004 [EMAIL PROTECTED]:/usr/obj/usr/src/usr.sbin/named Sep 7 13:03:25 it named[15916]: limit files set to fdlimit (1024) -- IOnut Unregistered ;) FreeBSD "user" ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
named[353]: sysquery: no addrs found for root NS ..........
Hi, >From time to time I get this: Sep 7 12:57:44 it named[353]: sysquery: no addrs found for root NS (d.root-servers.net) Sep 7 12:57:44 it named[353]: sysquery: no addrs found for root NS (a.root-servers.net) Sep 7 12:57:44 it named[353]: sysquery: no addrs found for root NS (c.root-servers.net) Sep 7 12:57:45 it named[353]: sysquery: no addrs found for root NS (h.root-servers.net) Sep 7 12:57:45 it named[353]: sysquery: no addrs found for root NS (f.root-servers.net) Sep 7 12:57:45 it named[353]: sysquery: no addrs found for root NS (b.root-servers.net) Doing here a named.reload and : Sep 7 12:57:45 it named[353]: sysquery: no addrs found for root NS () Sep 7 12:57:45 it named[353]: reloading nameserver Sep 7 12:57:45 it named[353]: Ready to answer queries. Anyone could tell me where to look for the problem ? I can see no pattern. it doesn't happen on a load, it was happening on 5.2 now also on 5.3BETA3. Thanks, -- IOnut Unregistered ;) FreeBSD "user" ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: sysquery: no addrs found for root NS
On Fri, 14 Nov 2003, Toomas Aas wrote: > I understand what the message is saying, but I don't understan what > causes it to say such a thing. It's hard to believe that there is > something wrong with my root zone file, because 99.9% of the time the > problem does not happen and DNS lookups work just fine (including > commands like 'host e.root-servers.net'). > The named.root file is standard one installed by FreeBSD and I haven't > touched it: > ; $FreeBSD: src/etc/namedb/named.root,v 1.9.2.1 2002/11/06 > 09:24:12 dougb Exp $ > > -- > Toomas Aas | [EMAIL PROTECTED] | http://www.raad.tartu.ee/~toomas/ Didn't I see a blurb a few months ago that the root server cache file was going to be updated? Google on that and see what you get. You can update by ftp-ing the new file from ICANN or somewhere. Sorry for lack of specifics. KeS ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: sysquery: no addrs found for root NS
> Date: Fri, 14 Nov 2003 12:57:19 -0800 (PST) > From: Kevin Stevens <[EMAIL PROTECTED]> > On Fri, 14 Nov 2003, Toomas Aas wrote: > > > The named.root file is standard one installed by FreeBSD and I haven't > > touched it: > > > ; $FreeBSD: src/etc/namedb/named.root,v 1.9.2.1 2002/11/06 > > 09:24:12 dougb Exp $ > > Didn't I see a blurb a few months ago that the root server cache file was > going to be updated? Google on that and see what you get. You can update > by ftp-ing the new file from ICANN or somewhere. Sorry for lack of > specifics. I checked the named.root file on ftp.internic.net and it's still dated 2002/11/05. -- Toomas Aas | [EMAIL PROTECTED] | http://www.raad.tartu.ee/~toomas/ * When I say 'literally', I literally mean 'literally'. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
sysquery: no addrs found for root NS
Hello!
I have seen this problem two times on one RELENG_4_8 machine and now I
just saw it on a freshly installed 4.9-RELEASE. I've tried to google
but the results i've found haven't helped me this far.
On the machines where the problem happens, I'm running BIND from the
base sytem (8.3.4 and 8.3.6 respectively) as a caching-only nameserver
without any local zones defined (except the 'localhost' zones created
by make-localhost.sh).
Suddenly, out of the blue, syslogd starts writing the following into
the log:
Nov 14 21:31:23 machine named[81]: sysquery: no addrs found for root NS
(E.ROOT-SERVERS.NET)
Nov 14 21:31:23 machine named[81]: sysquery: no addrs found for root NS
(D.ROOT-SERVERS.NET)
Nov 14 21:31:23 machine named[81]: sysquery: no addrs found for root NS
(E.ROOT-SERVERS.NET)
Nov 14 21:31:23 machine named[81]: sysquery: no addrs found for root NS
(H.ROOT-SERVERS.NET)
Nov 14 21:31:23 machine named[81]: sysquery: no addrs found for root NS
(I.ROOT-SERVERS.NET)
Nov 14 21:31:23 machine named[81]: sysquery: no addrs found for root NS
(J.ROOT-SERVERS.NET)
and it logs A LOT of these messages. First time it happened on a
RELENG_4_8 machine, the log filled up my 1 GB /var partition. The
second time it logged ca 30 000 lines in 3 seconds and then everything
returned to normal without any intervention. The third time, on
4.9-RELEASE machine, when I was actually present at the time it started
happening, I restarted the machine and this returned things to normal.
I understand what the message is saying, but I don't understan what
causes it to say such a thing. It's hard to believe that there is
something wrong with my root zone file, because 99.9% of the time the
problem does not happen and DNS lookups work just fine (including
commands like 'host e.root-servers.net').
The relevant portion of named.conf:
< cut >-
forwarders {
194.126.106.110;
194.126.115.18;
};
zone "." {
type hint;
file "named.root";
};
< cut >-
The named.root file is standard one installed by FreeBSD and I haven't
touched it:
; $FreeBSD: src/etc/namedb/named.root,v 1.9.2.1 2002/11/06
09:24:12 dougb Exp $
--
Toomas Aas | [EMAIL PROTECTED] | http://www.raad.tartu.ee/~toomas/
* Error reading FAT record: Try the SKINNY one? (Y/N)
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
