Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!uunet!mcsun!hp4nl!charon!piet
From: piet@cwi.nl (Piet Beertema)
Newsgroups: comp.protocols.tcp-ip.domains
Subject: Re: bind 4.8.3 : malformed response - worry ?
Message-ID: <2929@charon.cwi.nl>
Date: 13 Feb 91 08:48:35 GMT
References: <2302@tuvie.UUCP> <2303@tuvie.UUCP>
Sender: news@cwi.nl
Organization: CWI, Amsterdam
Lines: 30


	>but every other day it comes up with a burst (20 or so) of messages like
	>
	>Feb  8 08:29:44 vlsivie named[116]: Malformed response from 192.16.202.1
	>Feb  8 08:30:30 vlsivie named[116]: Malformed response from 192.48.96.2
	>Feb  8 08:31:14 vlsivie named[116]: Malformed response from 137.39.1.2
	>( 90% of these responses come from uunet.uu.net , some from mcsun.eu.net )
	>
	>What can lead to this behaviour ?
	>
	>FYI : I'm running primary server for vlsivie.tuwien.ac.at. , 
	>      uunet.uu.net is a secondary (?) for at. All rootservers are at
	>      least 300ms away ...

One problem is that it's *not* uunet.uu.net, but ns.uu.net
that is secondary server for the AT top level domain (and
for many other top level domains). The addresses above are
both of uunet.uu.net, not of ns.uu.net (137.39.1.3).
Another problem is that in the AT zone file there is a glue
record "assigning" ns.uu.net the address (192.48.96.2) of
uunet.uu.net. Needless to say that this caused a mess all
over the place and requires an immediate fix. The fix that
Andrew Partan of UUnet posted in this newsgroup prevents
such bogus addresses/assignments from showing up in the
zone files on the secondary servers, but the patch for sure
won't have been implemented everywhere.


-- 
	Piet Beertema, CWI, Amsterdam	(piet@cwi.nl)