Hello NSD folks,
My name is Yasuhiro Orange Morishita at JPRS.
I found strange behavior on k.root-servers.net as described below.
I heard that k.root-servers.net is running NSD, so I think that the
cause of the strange behavior is the bug of NSD.
Now, I'm attending the IETF57 meeting at Vienna.
If possible, I want to talk with the code maintainer of NSD, and I
also want to inform the problem to the administrator of
k.root-servers.net.
Regards,
I'm correcting a typo and addendum to my previous email. Sorry.
-- Yasuhiro Orange Morishita
2)But, the same name is querying a.root-servers.net, the corrent
^^^^^^^correct
answer is returned.
3)the name reducing to 245 characters, k.root-servers.net returns
the correct answer.
$ dig +norec -t a 123456789.123456789.123456789.123456789.123456789.123456789.123456789.123456789.123456789.123456789.123456789.123456789.123456789.123456789.123456789.123456789.123456789.123456789.123456789.123456789.123456789.123456789.123456789.1234567890.jp @k.root-servers.net
; <<>> DiG 9.2.2 <<>> +norec -t a 123456789.123456789.123456789.123456789.123456789.123456789.123456789.123456789.123456789.123456789.123456789.123456789.123456789.123456789.123456789.123456789.123456789.123456789.123456789.123456789.123456789.123456789.123456789.1234567890.jp @k.root-servers.net
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 41
;; flags: qr; QUERY: 1, ANSWER: 0, AUTHORITY: 6, ADDITIONAL: 6
;; QUESTION SECTION:
;123456789.123456789.123456789.123456789.123456789.123456789.123456789.123456789.123456789.123456789.123456789.123456789.123456789.123456789.123456789.123456789.123456789.123456789.123456789.123456789.123456789.123456789.123456789.1234567890.jp. IN A
;; AUTHORITY SECTION:
jp. 172800 IN NS dns0.spin.ad.jp.
jp. 172800 IN NS ns-jp.sinet.ad.jp.
jp. 172800 IN NS ns0.iij.ad.jp.
jp. 172800 IN NS ns0.nic.ad.jp.
jp. 172800 IN NS ns-jp.nic.ad.jp.
jp. 172800 IN NS e.dns.jp.
* I've mistaken on cut&paste. Please add this.
;; ADDITIONAL SECTION:
dns0.spin.ad.jp. 172800 IN A 165.76.0.98
ns-jp.sinet.ad.jp. 172800 IN A 150.100.2.3
ns0.iij.ad.jp. 172800 IN A 202.232.2.34
ns0.nic.ad.jp. 172800 IN A 202.12.30.131
ns-jp.nic.ad.jp. 172800 IN A 61.120.151.100
e.dns.jp. 172800 IN A 192.50.43.53
;; Query time: 748 msec
;; SERVER: 193.0.14.129#53(k.root-servers.net)
;; WHEN: Thu Jul 17 10:16:21 2003
;; MSG SIZE rcvd: 494
a message of 100 lines which said:
I heard that k.root-servers.net is running NSD, so I think that the
cause of the strange behavior is the bug of NSD.
I see the same problem with my own instance of nsd so, yes, this may
be a nsd problem.
Yasuhiro Orange Morishita wrote:
Hello NSD folks,
My name is Yasuhiro Orange Morishita at JPRS.
I found strange behavior on k.root-servers.net as described below.
Thanks. I'll take a look at this.
Erik
Erik Rozendaal wrote:
Yasuhiro Orange Morishita wrote:
Hello NSD folks,
My name is Yasuhiro Orange Morishita at JPRS.
I found strange behavior on k.root-servers.net as described below.
Thanks. I'll take a look at this.
Ok. I've opened a bug about this: <URL:http://www.nlnetlabs.nl/bugs/show_bug.cgi?id=59>\. The attached patch fixes this problem for NSD 1.2.0 (and the just released 1.2.1 which does not include this patch).
Erik
(attachments)
bug59.patch (644 Bytes)
Erik-san;
Thank you for your quick action.
Please apply this patch to NSD on K.root-servers.net.
Regards,
Yasuhiro Orange Morishita wrote:
Erik-san;
Thank you for your quick action.
To: administrators of k.root-servers.net;
Please apply this patch to NSD on K.root-servers.net.
Actually, k.root-servers.net is running NSD 1.0.2:
$ dig @k.root-servers.net version.server chaos txt
; <<>> DiG 9.2.1 <<>> @k.root-servers.net version.server chaos txt
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 39488
;; flags: qr; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;version.server. CH TXT
;; ANSWER SECTION:
version.server. 0 CH TXT "NSD-1.0.2"
;; Query time: 37 msec
;; SERVER: 193.0.14.129#53(k.root-servers.net)
;; WHEN: Thu Jul 17 11:04:37 2003
;; MSG SIZE rcvd: 54
The previous patch won't apply, use the attached patch for 1.0.2.
Erik
(attachments)
bug59-1.0.2.patch (1.75 KB)
Dave-san, thank you for your reply.
I found the new version of NSD (1.2.2) has been released. I think that
it is suitable to apply to k.root.