Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 15 Dec 1998 15:40:21 -0800
From:      Don Lewis <Don.Lewis@tsc.tdk.com>
To:        Michael Moran <mmoran@veronet.net>, freebsd-isp@FreeBSD.ORG
Subject:   Re: Strange message
Message-ID:  <199812152340.PAA00778@salsa.gv.tsc.tdk.com>
In-Reply-To: Michael Moran <mmoran@veronet.net> "Strange message" (Dec 15, 11:52am)

next in thread | previous in thread | raw e-mail | index | archive | help
On Dec 15, 11:52am, Michael Moran wrote:
} Subject: Strange message
} 
} Anyone can tell me what is meant?
} 
} Dec 15 11:39:42 veronet named[74]: Lame server on
} '249.128/25.231.31.209.in-addr
} .arpa' (in '128/25.231.31.209.in-addr.arpa'?): [209.31.231.129].53
} 'ns1.newthoug
} ht.net': learnt (A=206.173.119.72,NS=206.173.119.72)

It means that your name server was asking about
249.128/25.231.31.209.in-addr.arpa.  The server at IP address
206.173.119.72 (tycho.concentric.net) told your server to send
this query to ns1.newthought.net because ns1.newthought.net is
supposed to be an authoritative server for the zone
128/25.231.31.209.in-addr.arpa, and the server at IP address 206.173.119.72
also told your server that the IP address of ns1.newthought.net is
209.31.231.129.  When your server sent the query to 209.31.231.129, the
response that it got indicated that the server at 209.31.231.129 is
not authoritative for the zone 128/25.231.31.209.in-addr.arpa.

This means that either
	tycho.concentric.net has the wrong server name for the
	zone 128/25.231.31.209.in-addr.arpa.  The server should not
	be ns1.newthought.net, but something else.

	tycho.concentric.net sent your server the incorrect IP
	address for ns1.newthought.net, possibly because its
	cache picked up the incorrect address from another server.

	ns1.newthought.net is supposed to be authoritative for
	128/25.231.31.209.in-addr.arpa but is somehow misconfigured.

Your choices are to either contact the operators of the broken servers
to let them know that they need to fix their problem, or to ignore this
message and the possible failure of your server to find the answer
to the query it is attempting to resolve.

This should all be documented in the BIND book.  Be glad that this
long explanation isn't syslogged every time your name server encounters
a broken server.

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-isp" in the body of the message



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199812152340.PAA00778>