I'm aware that verizon does this as well which is the root source of the issue as marius pointed out but in my case as the hosts in question get their dns via dhcp from a router provided by the isp which for political reasons I won't go into I have no access to so as to change the resolvers it uses. thus the fix will be telling each host to ignore the resolvers it's given via dhcp and use others instead.... or just simply placing these boxen outside the dhcp range of the router and setting them up on static ip in a range not issued by the router but still within the routers private subnet. Eric On Thu, Jul 31, 2014 at 12:08 PM, jj <ve1jot(a)eastlink.ca> wrote:

Why do they do this ? On Thu, Jul 31, 2014 at 9:40 PM, jj <ve1jot(a)eastlink.ca> wrote:

On Thu, 31 Jul 2014 12:18:28 -0700, Eric Fort <eric.fort(a)gmail.com> wrote: Do this. On most systems, such as Windows XP or Windows 7 you can set the DNS IP's independently of the DHCP, making them higher priority than any they might get from DHCP. Once set, Windows 7 won't even insert the DHCP DNS IP's into its configuration on the interface. Fortunately, Verizon's Actiontec routers always point to themselves as the DNS and the router passes the queries to the DNS servers it has received when it logged in via PPPoE. It's these servers that are screwing with your DNS. I use DHCP to accept the LAN IP and mask but manually set my DNS on all my boxes in-house. Same principles apply to my Linux and OSX boxes. Surprisingly, Google's servers are compliant with the standard and don't return an address for your af6hf.ampr.org which has no entry. Wow, they're not evil. When Verizon stopped using Level3's DNS servers and they started "monetizing" me with their DNS servers, I stopped using their DNS servers. Except for this issue, I'm VERY happy with my FiOS service.