Hello,
I would like to thank the following people for having taken the time to
answer my question:
"Richard A. Muirden" <richard_at_rmit.EDU.AU>
Jonathan Rozes <jrozes_at_gumbo.tcs.tufts.edu>
"Anil Khullar, Computer Center" <Anil.Khullar_at_mailhub.gc.cuny.edu>
Eric Bennett <bennett_at_hpel.cees.edu>
Hans Ranke <Hans.Ranke_at_Regent.E-Technik.TU-Muenchen.DE>
Mike Iglesias <iglesias_at_draco.acs.uci.edu>
Dave Newbold <phdmn_at_siva.bris.ac.uk>
Sean Watson <swatson_at_tuolumne.lib.csubak.edu>
Dan Riley <dsr_at_lns598.lns.cornell.edu>
UFPEL - CPMET <ufpelrm_at_eu.ansp.br>
Andy speed-racer Wagliardo <awagliar_at_hubcap.core-dump.com>
Barry Treahy <treahy_at_ael1.allianceelec.com>
Carlos A M dos Santos <casantos_at_conesul.com.br>
Jeff Alerta <jalerta_at_earthlink.net>
Craig Shrimpton <craigs_at_os.com>
They all agreed that it is not a peculiarity of the Digital named program
but that lame delegation logging is a standard feature of bind 4.9.3.
Dave Newbold pointed me to the RIPE document ripe-114 that describes
"LAMERS" in agreement with what many other replies have stated as follows:
"A lame delegation is a serious error in DNS configurations, yet a
(too) common one. It happens when a nameserver is listed in the NS
records for some domain, and in fact it is not a server for that
domain. Queries are thus sent to the wrong servers, who don't know
nothing (at least not as expected) about the queried domain.
Furthermore, sometimes the hosts in question (if they exist!) don't
even run nameservers. As a result, queries are timed out and resent,
only to fail, thus creating (more) unnecessary traffic on the
Internet. ... "
The problems related to our own nameserver ip-dns-1.cern.ch will hopefully
be fixed in the near future.
Dietrich Wiegandt
CERN CN Division
CH-1211 Geneve 23
Switzerland
Received on Wed Apr 24 1996 - 19:42:40 NZST