bind-9.3.2-33.fc5

[broadcast]

Bill Larson wrote:
> Look, Mark gave ***A*** possibility for an answer to your problem,
> but you provided very little useful information about the problem
> itself.
Yes, I believe this is true, but that was becuase of the way this
discussion went, no further information were asked.
> Can you provide us with a specific example of a domain that you are
> having problems with?  Providing this information will allow someone
> to confirm or deny that there is a DNS problem with the specific
> example(s) that you give.  If
Ok, here are some examples of domains that were failing to resolve
www.3ouon.com.ps
www.twseyatscript.com
www.moashrat.com
www.stooop.com
These domains were failing frequently and to get them to resolve i had
to restart the named daemon whenever they fail.


> Since the issue is only with resolving information, this test setup
> doesn't even have to be authoritative for any zones - simply
> configure a caching DNS server.

I already did so, and I have a Cobalt machine with bind-8.2.3-C1
configured outside my firewall as caching only server.
after forwarding our public servers to the new caching server
everything was fine .
then the problem happened with some new domains not as frequently as it
was before but it is still happens, so then I enabled the query logging
on the caching server and I can see the following messages as an
example.
Sep 25 21:38:51 bns named[3722]: ns_resp: query(mail.yahoo.bz) All
possible A RR's lame
Sep 25 21:38:51 bns named[3722]: bad referral (. !<
freevirtualstrippers.com) from [64.255.172.57].53
Sep 25 21:38:51 bns named[3722]: bad referral (. !<
freevirtualstrippers.com) from [64.255.172.57].53
Sep 25 21:38:51 bns named[3722]: bad referral (. !< alsafidanone.com)
from [64.20.49.218].53
Sep 25 21:38:52 bns named[3722]: bad referral (181.24.in-addr.arpa !<
115.181.24.in-addr.arpa) from [66.168.240.37].53
Sep 25 21:38:52 bns last message repeated 2 times
Sep 25 21:38:56 bns named[3722]: bad referral (. !< www-mailserver.com)
from [64.20.39.26].53
Sep 25 21:39:04 bns named[3722]: bad referral (231.61.in-addr.arpa !<
44.231.61.in-addr.arpa) from [168.95.1.14].53
Sep 25 21:39:04 bns named[3722]: bad referral (231.61.in-addr.arpa !<
44.231.61.in-addr.arpa) from [168.95.1.14].53
Sep 25 21:39:07 bns named[3722]: bad referral (. !< nokiacastle.NET)
from [64.20.41.162].53

one of the domains that failed on the caching server was www.6rb1.net
and again it started working fine after restarting the named daemon.

> BIND-9.3 is IPv6 aware, again as Mark identified.  If there is a
> problem with how your setup, either servers or network, deal with
> IPv6 then there could obviously be a problem.  If the problem lies
> with your handling of IPv6, have you considered using the "-4" option
> to "named" to force IPv4 only handling of DNS?
I currently don't have IPv6 implemented, but how can I use the "-4"
option?

Thank you