behavior of k.root-servers.net

Yasuhiro Orange Morishita /森下泰宏 yasuhiro at jprs.co.jp
Thu Jul 17 11:17:49 CEST 2003


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,
--
Yasuhiro 'Orange' Morishita
DNS Technical Engineer
Research and Development department, Japan Registry Service Co.,Ltd. (JPRS)
E-Mail: yasuhiro at jprs.co.jp / orange at jprs.co.jp

--- cut ------ cut ------ cut ------ cut ------ cut ------ cut ---

1)Querying long name (it has 246-255 chars) to k.root-servers.net, it
  returns 'FORMERR'.

$ 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.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.123456789.1234567890.jp @k.root-servers.net
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: FORMERR, id: 41
;; flags: qr; QUERY: 0, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; Query time: 370 msec
;; SERVER: 193.0.14.129#53(k.root-servers.net)
;; WHEN: Thu Jul 17 09:53:05 2003
;; MSG SIZE  rcvd: 12

2)But, the same name is querying a.root-servers.net, the corrent
  answer is returned.

$ 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.123456789.1234567890.jp @a.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.123456789.1234567890.jp @a.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.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.

;; 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: 380 msec
;; SERVER: 198.41.0.4#53(a.root-servers.net)
;; WHEN: Thu Jul 17 09:52:57 2003
;; MSG SIZE  rcvd: 504

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.


More information about the nsd-users mailing list