KCrimson
Premium
join:2001-02-25
Brooklyn, NY
 ·Optimum Online
 ·Verizon FIOS
| reply to KA3SGM
Re: [northeast] DNS hijacking in effect (new)
I think the directions that FiOS is giving to change the default DNS server are flawed. I didn't get any change until I edited the Broadband (in my case /MOCA, in others /Ethernet depending on how your router was hooked up) setting, NOT the Home/Office DNS setting, as the directions say. I'm wondering if I should leave BOTH sets of DNS settings to the 4.2.2.2/4.2.2.3 servers, or whether I should leave the Home/Office side back to the automatic position. Anyone care to give insight? |
|
gweeper
join:2002-01-04
Southborough, MA
| You have to change it in multiple spots and boy is that actiontec interface lame. Userid that works for the pointy-clicky goop doesn't seem to be effective way to gain access to the CLI.
Of course once wrestling my way through the interface I changed to a server I run and one of the L3 anycasts. Use whatever you like but MEASURE the path first (traceroute at least). Folks saying "everyone should use FOO" are ignoring that topology matters. The reason service providers deploy DNS resolvers near customers is to be sure lookups -part of any transaction- do not slow down applications. Using any distant DNS servers is introducing other variables, possible outages, etc.
The 'opt-out' garbage in this case [paxfire, it seems; www.paxfire.com to direct additional comments] is related only to web browsers. Glad they have unmolested servers available. DNS is basic plumbing and not a revenue stream.
Your best bet, if you don't use bad software, is to deploy a local resolver yourself.
Coffee, local resolver, get on with my day.
|
|
