thr3ads.net - nsd users - behavior of k.root-servers.net [Jul 2003]

If this information is useful, please help other people find it:
Share via:

Yasuhiro Orange Morishita / 森下泰宏

2003-Jul-17 01:17 UTC

behavior of k.root-servers.net

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.

Yasuhiro Orange Morishita / 森下泰宏

2003-Jul-17 01:30 UTC

head link

behavior of k.root-servers.net

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

--
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

Stephane Bortzmeyer

2003-Jul-17 07:03 UTC

head link

behavior of k.root-servers.net

On Thu, Jul 17, 2003 at 10:17:49AM +0900,
 Yasuhiro Orange Morishita / ?$B?92<BY9( <yasuhiro at jprs.co.jp> wrote
 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.

Marc Groeneweg

2003-Jul-17 07:18 UTC

head link

behavior of k.root-servers.net

> On Thu, Jul 17, 2003 at 10:17:49AM +0900,
>  Yasuhiro Orange Morishita / ?$B?92<BY9( <yasuhiro at jprs.co.jp>
wrote
>  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.I have noticed the same behavior at our location.

Erik Rozendaal

2003-Jul-17 07:45 UTC

head link

behavior of k.root-servers.net

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

Marc Groeneweg

2003-Jul-17 10:05 UTC

head link

behavior of k.root-servers.net

Erik,

What about NSD 1.0.3? We're running NSD 1.0.3 on ns5.domain-registry.nl.
> 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:
Marc Groeneweg

nsd users - Jul 2003 - behavior of k.root-servers.net

behavior of k.root-servers.net

behavior of k.root-servers.net

behavior of k.root-servers.net

behavior of k.root-servers.net

behavior of k.root-servers.net

behavior of k.root-servers.net