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
In message <8401907190740j6e04pc23316827fe0b...@mail.gmail.com>, Bradle
y Caricofe writes:
> Hello,
>
> Firstly, I know this issue has already been covered in some depth here. I've
> spent hours perusing the archives and researching this online, and am still
> not sure about what I'm seei
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
You don't need the zone entry. In your options configuration add:
...
forwarders { 208.67.222.222; 208.67.220.220; };
forward only;
...
And restart. This will make your named server a forward only name server
Matthew Huff | One Manhattanville Rd
OTA Management LLC | Purchase, NY 10
Hello,
Firstly, I know this issue has already been covered in some depth here. I've
spent hours perusing the archives and researching this online, and am still
not sure about what I'm seeing. This weekend, I migrated two old Solaris 5.7
boxes running BIND 9.2, over to two new CentOS systems runnin
6 matches
Mail list logo
