a death loop with DNS query

2011-07-06 Thread Feng He
When I dig this: dig s1.mytest.blogchina.org +trace I got many these info: mytest.blogchina.org. 600 IN NS ns1.dnsv5.com. mytest.blogchina.org. 600 IN NS ns2.dnsv5.com. ;; BAD (HORIZONTAL) REFERRAL ;; Received 95 bytes from 183.60.59.217#53(ns1.dnsv5.com) in 6 ms

Re: a death loop with DNS query

2011-07-06 Thread Lyle Giese
On 7/6/2011 5:52 AM, Feng He wrote: When I dig this: dig s1.mytest.blogchina.org +trace I got many these info: mytest.blogchina.org. 600 IN NS ns1.dnsv5.com. mytest.blogchina.org. 600 IN NS ns2.dnsv5.com. ;; BAD (HORIZONTAL) REFERRAL ;; Received 95 bytes from

Re: a death loop with DNS query

2011-07-06 Thread Stephane Bortzmeyer
On Wed, Jul 06, 2011 at 08:23:45AM -0500, Lyle Giese l...@lcrcomputer.net wrote a message of 56 lines which said: That is not a loop at all. I disagree. As dig clearly says, there is an horizontal referral: the name servers are supposed to be authoritative for blogchina.org and

named web statistics

2011-07-06 Thread King, Harold Clyde (Hal)
Hi; I know there is a web front end to DNS stats, but I can not remember the option in the named.conf that defines the port. I'm running 9.8.0-P4 (just now being able to upgrade to a version that supports the statistics) Does anyone remember this? -- Hal King - h...@utk.edumailto:h...@utk.edu

Re: named web statistics

2011-07-06 Thread Jeremy C. Reed
On Wed, 6 Jul 2011, King, Harold Clyde (Hal) wrote: I know there is a web front end to DNS stats, but I can not remember the option in the named.conf that defines the port. I'm running 9.8.0-P4 (just now being able to upgrade to a version that supports the statistics) statistics-channels

Re: named web statistics

2011-07-06 Thread King, Harold Clyde (Hal)
Thanks! -- Hal King - h...@utk.edu Systems Administrator Office of Information Technology Systems: Business Information Systems The University of Tennessee 135D Kingston Pike Building 2309 Kingston Pk. Knoxville, TN 37996 Phone: 974-1599 On 7/6/11 11:15 AM, Jeremy C. Reed jr...@isc.org

Re: update bind

2011-07-06 Thread Eivind Olsen
saravanan subramani wrote: Can I upgrade our existing version 9.5 to 9.8 directly or do I have to do multiple updates. You shouldn't need to do intermediate / multiple updates, no. You might need to go quickly over your named.conf, zonefiles etc., to make sure they still work with the new

Re: update bind

2011-07-06 Thread Evan Hunt
Can I upgrade our existing version 9.5 to 9.8 directly or do I have to do multiple updates. You should have no trouble with a direct update, but if you want to be cautious, get 9.8.0-P4, build it but don't install it, and from within the build tree, run bin/check/named-checkconf -z on your

Re: Doubt with towiresorted

2011-07-06 Thread Kevin Darcy
On 7/6/2011 4:36 AM, Vignesh Gadiyar wrote: Got your point. I meant answer sections in the Response from the DNS server itself. It contains 4 sections namely Question, Answer, Authoritative and Additional sections right. I used the rrset-order in named.conf to set order to random which was

Re: Key foo: Delaying activation to match the DNSKEY TTL.

2011-07-06 Thread Paul B. Henson
On Tue, Jul 05, 2011 at 07:34:22PM -0700, Evan Hunt wrote: The key is being published now, and its activation date (i.e., when it will start to be used to sign records) is in the near future: less than the TTL of the DNSKEY record from now. When the key starts signing, then someone could

about AUTHORITY SECTION

2011-07-06 Thread pangj
Hello, I got two different forms of AUTHORITY SECTION from the dig, for example, $ dig mydots.net @ns7.dnsbed.com ; DiG 9.4.2-P2.1 mydots.net @ns7.dnsbed.com ;; global options: printcmd ;; Got answer: ;; -HEADER- opcode: QUERY, status: NOERROR, id: 36520 ;; flags: qr aa rd; QUERY: 1,

Re: Key foo: Delaying activation to match the DNSKEY TTL.

2011-07-06 Thread Evan Hunt
Hmm, thanks for the explanation. However, for this case, while the activation date was in the near future, the *publish* date was far in the past. Apparently it thought this was the first time it was being published, anyway. That information doesn't come from the publication date but from