99% of the time openDNS works by just pointing some agent to their ip
space.
That 1% of the time, openDNS tries to make DNS responses that are
modified in a way to try to help you.
Maybe this is your issue?
Googl.com being common enough they elect to return the google.com's
answer istead.
By default openDNS does not know how to return NXDOMAIN.
This is fine for end users. This is bad for developed and servers.
OpenDNS also does phishing URL blocking, stats, and a lot more.
If you plan on using them as a resolver you want to be accurate, you
must disable these features. Simply create an account with open DNS,
login, add your IP, and disable all respond modification settings.
Make sure someone elses IP has not been inherited by you with settings
you will not want.
I used to reccomend openDNS to everone. I found a problem in their
system many many months back. Despite a small effort to resolve it,
they have seemingly forgot about the problem.
Maybe someone else here has recommendationd to huge robust recursive
resolvers that do not focus on any response modification.
--
Scott
Iphone says hello.
On Jul 18, 2009, at 11:52 PM, Ken Lai <soulhacker...@gmail.com> wrote:
my bind server have a default option
forwarders { 208.67.222.222; 208.67.220.220; };
to send all query to OpenDNS.
but some answer could not access, while a answer can which solved by
another server
i put these in the config:
zone "xxxxx.com" {
type forward;
forwarders { x.x.x.x; };
};
but this not work.
how can i make this happen.
THANKS.
_______________________________________________
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
