Not every server can resolve same name / cache issue?

[Lawrence Mackley]

That is my concern with the NT servers. However, I
thought the Solaris DNS servers were new enough to
avoid this and was planning to use them to replace the
NT ones. 

Our Solaris servers are running BIND 8.2.2-P5. Is
there a way to configure them so this does not happen
(short of adding offending servers as bogus after the
fact)?

Larry
-----------------------------------------

In article <9k72kr$8n4 at pub3.rc.vix.com>,
Lawrence Mackley  <larryslists at yahoo.com> wrote:
>
>Recently (past two weeks) we have experienced strange
>behavior with NT 4.0 SP5 and Solaris 8 DNS servers.
>One example is the internal DNS server used by users
>can resolve all names but one, such as www.isc.org.
If
>I try to resolve that name from another DNS server it
>is resolved just fine. When I compare the caches of
>the two servers both have the domain but only one has
>the A record. This is also occurring with MX records.

Most likely, something is poisoning the NS record
caches.  Check the cache
to see what they have for the NS records for isc.org
and org.

A few weeks ago I was helping a customer and they had
bad NS records for
COM cached, because of some web hosting site that had
configured their
nameserver as authoritative for COM, ORG, and NET. 
Recent versions of BIND
won't cache these bogus NS records, but he's running
an old version without
the checks (I had him reconfigure his server to use
ours via "forwarders").

-- 
Barry Margolin, barmar at genuity.net
Genuity, Woburn, 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.



__________________________________________________
Do You Yahoo!?
Make international calls for as low as $.04/minute with Yahoo! Messenger
http://phonecard.yahoo.com/