Ken Lai wrote:
Scott Haneda wrote:
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 retu
Scott Haneda wrote:
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.co
http://www.xname.org
other dns service
On Sun, 19 Jul 2009 11:20:32 -0700, Scott Haneda
wrote:
> 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
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
imple question, please help
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 "x.com" {
type forwar
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 "x.com" {
type forward;
forwarders { x.x.x.x; };
};
bu
6 matches
Mail list logo
