Re: named[353]: sysquery: no addrs found for root NS ..........

2004-09-08 Thread Ion-Mihai Tetcu
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 ..........

2004-09-07 Thread Ion-Mihai Tetcu
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]


Re: named[353]: sysquery: no addrs found for root NS ..........

2004-09-07 Thread Toomas Aas
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 ..........

2004-09-07 Thread Ion-Mihai Tetcu
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 ..........

2004-09-07 Thread Robert Eckardt
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 ..........

2004-09-07 Thread Ion-Mihai Tetcu
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 ..........

2004-09-07 Thread horio shoichi
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]