newbie question: Lame server?

[Barry Margolin]

In article <kw_Y4.2876$MY6.48526 at newsread2.prod.itd.earthlink.net>,
John Riehl <riehl.nospam at earthlink.net> wrote:
>
>I am getting periodic messages like this:
>May 30 18:35:17 speedy named[397]: Lame server on 'flyntdigital.net' (in
>'flyntdigital.net'?): [208.145.170.6].53 'NSF1.FLYNTDIGITAL.COM'
>May 30 18:35:17 speedy named[397]: Lame server on 'flyntdigital.net' (in
>'flyntdigital.net'?): [204.70.25.234].53 'NS3.CW.NET'
>
>what the hey?  Reading about lame servers, I am not so sure that I
>understand this correctly.   This is some sort of zone misconfiguration,
>where there was a delegation of a subdomain to a child name server, and the
>child is not authoratative.
>
>So, the parent said the child was authoratative, but the child doesnt think
>it is authoratative?  How would you make the child authoritative?  When I
>talk to the folks at lfp (yes, I know these people), what part is
>misconfigured?  (first error message) does the ip address actually belong to
>flyntdigital.com or flyntdigital.net?

The problem is that the flyntdigital.net zone isn't installed on the
nsf1.flyntdigital.com server at all.

The IP address in the error message is the address of the lame nameserver;
208.145.170.6 is nsf1.flyntdigital.com, and 204.70.25.234 is ns3.cw.net.

-- 
Barry Margolin, barmar at genuity.net
Genuity, Burlington, MA
*** DON'T SEND TECHNICAL QUESTIONS DIRECTLY TO ME, post them to newsgroups.
Please DON'T copy followups to me -- I'll assume it wasn't posted to the group.