Lame delegation to server with cached NS data.
Jonathan de Boyne Pollard
J.deBoynePollard at Tesco.NET
Thu Nov 18 04:43:12 UTC 2004
TD> While this is more of a DNS question than a BIND question [...]
... and thus belongs in a different newsgroup ...
TD> As far as I understand it that means the egate.net name server is
TD> sending out the request for a question it already has the answer too
TD> thereby creating a loop. Would that be correct?
No. It's a lot simpler than that. The "ca." content DNS servers
delegate "wecdsb.on.ca." to the two content DNS servers at 220.127.116.11
and 18.104.22.168. In its turn, the "wecdsb.on.ca." content DNS server
at 22.214.171.124 delegates "wecdsb.on.ca." to 126.96.36.199 and back to
itself. That's the loop.
TD> "Probable cause is lame delegation to server with cached NS data"
And that's precisely what is happening in this case. The
"wecdsb.on.ca." content DNS server at 188.8.131.52 is vainly trying to
wear all of the hats at once, and provide proxy DNS service as well as
content DNS service (when it should really be configured to provide only
the latter). It only knows about the "wecdsb.on.ca." delegation in the
first place because at some point, less than a day ago, someone used it
for proxy DNS service and caused it to look the delegation up.
Eventually, the delegation information will expire from its cache, and
instead of publishing a self-referral (in answer to "*.wecdsb.on.ca."
questions) it will start publishing a *backwards* referral, for either
"ca." or ".", until the next time that someone comes along and uses it
for proxy DNS service to look up something in "wecdsb.on.ca.".
TD> How can I educate this customer that the 'problem' in question does
TD> not exist on our network but his network layout?
Depending from who your customer actually is, the problem may not be
anything to do with your customer, either.
The people who need to fix things are the owner of the content DNS
server at 184.108.40.206 and the owner of "wecdsb.on.ca.". The latter
needs to talk to the former, and persuade/pay him/her to configure
his/her content DNS server to hold the "wecdsb.on.ca." DNS data in its
database and to publish them.
More information about the bind-users