Re: Strange DNS problem

From: Herb Martin (news_at_LearnQuick.com)
Date: 04/20/05 

Date: Tue, 19 Apr 2005 18:02:15 -0500

"C Hall" <someone@microsoft.com> wrote in message
news:#mv9kyRRFHA.3496@TK2MSFTNGP12.phx.gbl...
> Thanks for the lesson, Herb.

Sure but it still didn't solve you real issue. <grin>

> "Herb Martin" <news@LearnQuick.com> wrote in message
> news:enUGOrRRFHA.248@TK2MSFTNGP15.phx.gbl...
> > "C Hall" <someone@microsoft.com> wrote in message
> > news:OS$oyyORFHA.688@TK2MSFTNGP10.phx.gbl...
> >
> > > That was my first thought--DNS cache poisoning. The one reason I
thought
> > > that it just may be an internal configuration problem is that the zone
> I'm
> > > using is already in use as an Internet domain space--a mistake on my
> part.
> >
> > First, your internal zone using an internal name the
> > same as a public name doesn't really interact with
> > cache poisoning.
> >
> > Holding your zones, it distinct from the resolution
> > you do for clients (beyond those zones) and poisoning
> > is worked through that resolution.
> >
> >
> >
> >
>
>