Verizon provides their FiOS customers with 2 regional DNS servers via DHCP that are geographically close to their install location. The default address given out is a ".12" address which utilizes DNS Hijacking to serve you ads from Verizon. Each region has a corresponding ".14 DNS server which does not hijack DNS. Changing to this ".14" address is the method Verizon utilizes for allowing customers to opt-out of their "DNS Assistance".
I couldn't find a complete list of these online, so with a little digging I put this together.
Regional DNS Servers, opt-in/opt-out are listed below. There are many other valid Verizon DNS servers, but these are the ones given out to customers via DHCP. If you are aware of any additional DNS servers given out via DHCP to FiOS customers, please let me know in the comments.
Boston, MA:
nsbost01.verizon.net - 71.243.0.12
nsbost02.verizon.net - 71.243.0.14
New York, NY:
nsnyny01.verizon.net - 68.237.161.12
nsnyny02.verizon.net - 68.237.161.14
Newark, NJ:
nsnwrk01.verizon.net - 71.250.0.12
nsnwrk02.verizon.net - 71.250.0.14
Philadelphia, PA:
nsphil01.verizon.net - 71.242.0.12
nsphil02.verizon.net - 71.242.0.14
Reston, VA:
nsrest01.verizon.net - 71.252.0.12
nsrest02.verizon.net - 71.252.0.14
Atlanta, GA:
nsatla01.verizon.net - 68.238.120.12
nsatla01.verizon.net - 68.238.120.14
Tampa, FL:
nstamp01.verizon.net - 68.238.112.12
nstamp02.verizon.net - 68.238.112.14
Dallas, TX:
nsdall01.verizon.net - 68.238.96.12
nsdall02.verizon.net - 68.238.96.14
Los Angeles, CA:
nslala01.verizon.net - 68.238.64.12
nslala02.verizon.net - 68.238.64.14
Seattle, WA:
nsseat01.verizon.net - 68.238.128.12
nsseat02.verizon.net - 68.238.128.14
(Added 5/5/2016)
Chicago, IL:
nschic01.verizon.net - 68.238.0.12
nschic02.verizon.net - 68.238.0.14
Great, thanks!
ReplyDeleteThanks for this! Was able to add these to DNS Jumper and test their speeds. The Verizon servers closest to me (newark/nyc/pa) were consistently in the top 5 in resolve time.
ReplyDeleteChicago, IL:
ReplyDeleteServer: nschic01.verizon.net
Address: 68.238.0.12
Thanks! Added
DeleteThanks!
ReplyDeleteThanks!
ReplyDeleteThanks... Nice to see documentation
ReplyDeleteWhat is the one to Lawrence, MA.
ReplyDeleteThese are regionally based - so the closest ones would be Boston and then New York.
DeleteI wanted to opt out of Verizon's hijacking "service" so I followed their instructions and changed the DNS servers from xxx.xxx.xxx.12 to xxx.xxx.xxx.14 in my router (actually, their modem/router/wifi device). Now I am seeing
ReplyDeleteThis site can’t be reached
xxx.xx’s server DNS address could not be found.
Search Google for klei mn
ERR_NAME_NOT_RESOLVED
instead of google search. This is ridiculous.
On top of that I am now getting weird error messages when I attempt to enter something into the verizon forums... When I click on "Forums Sign in" I get:
Bad Request
Your browser sent a request that this server could not understand.
Size of a request header field exceeds server limit.
Cookie
/n
This is absolutely intolerable. Unfortunately, I am also unable (at least for now) to see the online chat OR the option to have them call me back. Their service has ALWAYS been abominable but, this is something worse than abominable.
I'd double check your settings and also try manually polling the new .14 DNS server from a command prompt.
DeleteThis comment has been removed by the author.
ReplyDeleteThis comment has been removed by the author.
ReplyDeleteSE Virginia, Hampton Roads area, FIOS gives those DNS:
ReplyDeletePrimary: 71.252.0.12
Secondary: 68.238.112.12
As always, use .14 at the end to opt out from their "Assistance".
Any for northern cali area?
ReplyDeletenot sure what you want me to say, I guess I'm looking for a dns until I can get a domain dns
ReplyDeleteFWIW I'm in Phila area, I'm given 71.242.0.12 and 71.250.0.12 on their lease to my firewall. the .14 versions of these are without the wrong hostname assistance. I use the .14 versions on a channels-dvr server I'm running so the TVE gets the proper local CDN servers, but everything else I'm using cloudflare over TLS forced by my firewall.
ReplyDelete