news.bbc.co.uk NXDOMAIN problem fixed

itojun@iijlab.net itojun@iijlab.net
Thu, 25 Apr 2002 15:08:31 +0900


------- =_aaaaaaaaaa0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <28866.1019714895.1@itojun.org>

	wow, it was quick!

itojun

------- =_aaaaaaaaaa0
Content-Type: message/rfc822
Content-ID: <28866.1019714895.2@itojun.org>
Content-Description: forwarded message

Return-Path: simonl@rd.bbc.co.uk
Delivery-Date: Thu Apr 25 15:06:45 2002
Return-Path: <simonl@rd.bbc.co.uk>
Delivered-To: itojun@itojun.org
Received: from gateh.kw.bbc.co.uk (gateh.kw.bbc.co.uk [132.185.132.17])
	by coconut.itojun.org (Postfix) with ESMTP id CE88E4B24
	for <itojun@itojun.org>; Thu, 25 Apr 2002 15:06:42 +0900 (JST)
Received: from sunf0.rd.bbc.co.uk (ddmailgate.rd.bbc.co.uk [132.185.128.104])
	by gateh.kw.bbc.co.uk (8.11.2/8.11.2) with SMTP id g3P66Zx23641;
	Thu, 25 Apr 2002 07:06:35 +0100 (BST)
Received: from sunf25.rd.bbc.co.uk by sunf0.rd.bbc.co.uk; Thu, 25 Apr 02 07:06:34 BST
Date: Thu, 25 Apr 2002 07:06:32 +0100
From: Simon Lockhart <simonl@rd.bbc.co.uk>
To: Jun-ichiro itojun Hagino <itojun@itojun.org>
Cc: nanog@nanog.org
Subject: Re: incorrect NXDOMAIN response from DNS server
Message-Id: <20020425060630.GA3290@rd.bbc.co.uk>
References: <26629.1019701827@itojun.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <26629.1019701827@itojun.org>
User-Agent: Mutt/1.3.25i
X-Filter: mailagent [version 3.0 PL73] for itojun@itojun.org

On Thu Apr 25, 2002 at 11:30:27AM +0900, Jun-ichiro itojun Hagino wrote:
> 	there are name server implementations (probably load balancing product)
> 	that responds with NXDOMAIN, when it should respond with NOERROR with
> 	empty reply.  one example is news.bbc.co.uk.  

Guilty as charged. Seems to only have been a problem since the deployment
of IPv6

> 	do you know:
> 	- name of particular implementation which have/had this bug?

"BBC Intelligent Load Balancing DNS Server"

> 	- other examples of nameservers that behave like this?
> 	  (windowsupdate.microsoft.com behaved like this in Feb 2002, but
> 	  they are already fixed)

Oh, so it's not just us.

> 	- how can we get people to fix it?  (client side workaround should
> 	  not be populated, just to be sure)

Name and shame seems to work ;-) I believe I have now fixed it. Please let me
know if you think otherwise.

Simon
-- 
Simon Lockhart                       |   Tel: +44 (0)1737 839676 
Internet Engineering Manager         |   Fax: +44 (0)1737 839516 
BBC Internet Services                | Email: Simon.Lockhart@bbc.co.uk 
Kingswood Warren,Tadworth,Surrey,UK  |   URL: http://support.bbc.co.uk/

------- =_aaaaaaaaaa0--