Default DNS server IP addresses
ubrgeek
Contributor - Level 1

I was having problems tracking down the default IP addresses for the FIOS DNS servers and saw others were having the same problem. Finally got them (at least, the ones for Maryland FIOS) and figured I'd post them in case they were of use to others:

4.2.2.1
4.2.2.2
4.2.2.3
4.2.2.4
4.2.2.5

Hope this can help someone.

0 Likes
Reply
1 Solution
eljefe2
Master - Level 1

Hey.....some wine would go well with a Big Mac, wouldn't it?  Smiley Tongue

Good luck.

View solution in original post

0 Likes
Reply
17 Replies
eljefe2
Master - Level 1

Those are all Level 3 DNS servers.  How did you determine those are the FiOS default servers?

I don't use the default servers but if I did my Actiontec shows them to be 68.227.161.12 and 71.250.0.12.

0 Likes
Reply
ubrgeek
Contributor - Level 1

I waited for around 20 minutes for a support rep to finally show up on the live chat support Smiley Wink My question to them was, "What are the IP addresses of the default DNS servers that I should use for Prince George's County, MD?" Those were the ones they provided. 

0 Likes
Reply
eljefe2
Master - Level 1

Well....Level 3 DNS servers should be ok to use but I still don't buy they're a FiOS default.

If you login to your Actiontec's interface and look at the System Monitoring page, what does it say the DNS servers are?

0 Likes
Reply
ubrgeek
Contributor - Level 1

71.252.0.12
68.237.161.12

0 Likes
Reply
eljefe2
Master - Level 1

Those are Verizon DNS servers and I'd say they are the Verizon defaults in your area.

0 Likes
Reply
Hubrisnxs
Legend

Those are old BBN/Genuity/Level 3 DNS's which IMO ROCK.

I like those dns's better than any others personally.

The default Verizon DNS's are default by region, so a list of dns's would be pretty large.     

0 Likes
Reply
ubrgeek
Contributor - Level 1

Hubrisnxs - 71.252.0.12 & 68.237.161.12 are the ones you prefer?

0 Likes
Reply
Hubrisnxs
Legend

@ubrgeek wrote:

Hubrisnxs - 71.252.0.12 & 68.237.161.12 are the ones you prefer?


I like the 4.2.2.1 - 8

a small list of servers for Verizon DNS's can be found here.   I am not sure how current this is but this is the list people have gathered. 

0 Likes
Reply
ubrgeek
Contributor - Level 1

Interesting. Wonder why that wasn't what they provided. Thanks for the explanation.

0 Likes
Reply
eljefe2
Master - Level 1

If you want to see what DNS servers work best in your location, get GRC's DNS Benchmark utlity (free) here:

http://www.grc.com/dns/benchmark.htm

It will show you what smokes and what pokes.  馃檪

ubrgeek
Contributor - Level 1

Thanks eljefe. I'll grab it and see if I've got Wine installed somewhere (yeah, I'm a **bleep** Mac boy :))

0 Likes
Reply
eljefe2
Master - Level 1

Hey.....some wine would go well with a Big Mac, wouldn't it?  Smiley Tongue

Good luck.

0 Likes
Reply
ubrgeek
Contributor - Level 1

lol - Nicely played 馃檪

Thanks everyone and have a great New Year's!

0 Likes
Reply
spacedebris
Master - Level 2

Yeah, those are not the default Verizon DNS servers. Each area has their own DNS server. Those are just the ones that are easy to remember so its the ones that most of the tech support guys use for troubleshooting and for entering static information.

0 Likes
Reply
bnrosman
Newbie

My action tec had similar DNS servers. When I tried to ping them: 68.227.161.12  - it timed out. No responses

71.250.0.12 - 15ms response time. My I pad was dropping wifi, I could not access my verizon account, page not found, I could not access the system with Google Chrome: Method not supported.

I then said I have a DNS problem and tried OPEN DNS. The response time was under 10ms, Google Chrome worked and my IPAD is once again stable.

I believe the verizon DNS's are flakey at best.

0 Likes
Reply
AAdamAnTium
Enthusiast - Level 1

Fast forward to August 2, 2017 and.... 
Thank you! Those are still the top ranked DNS ISP IP Addy's for Verizon FiOS (at least In Gaithersburg, MD) and I have two different sets of pictures and .INIs to prove it (See attached)!  OR go to https://www.GRC.com/DNS/BenchMark.htm download

the utility, run it imageimageand you can spend the next 2 hours costumizing your own DNS configuration.

I ran the Gibson DNS Benchmarking Utility from soup to nuts twice on two distinct compatible  HiSpeed ISPs (~75Mbps Up/Down) Verizon FiOs and RCN

(Formerly Starpower & Erols) 

Thank you all for your contributions!   

The play by play:

@UberGEEK opens up and gets scolded by @ElJefe.  Only to be assisted by @HubrisNXS which in turn keeps The Boss @ElJefe in check. (Officiating early this morning is ME @AAdamAnTium Arbitrations).

THE STANDINGS:

  1. 8.8.4.4  Google DNS
  2. 8.8.8.8  Google DNS
  3. 4.2.2.1   Level3 - Level 3 Communications
  4. 4.2.2.2  Level3 - Level 3 Communications
  5. 4.2.2.3  Level3 - Level 3 Communications
  6. 4.2.2.4  Level3 - Level 3 Communications
  7. 4.2.2.5  Level3 - Level 3 Communications
  8. 4.2.2.6  Level3 - Level 3 Communications 

......9, 10, 11, etc... MegaPath, Cogent , LVLT-3549 (L3 Comm.)

   16. 068.237.161.014:  UUNET - MCI Communications

   17. 071.252.000.012: UUNET - MCI Communications

Here in the future we also have something called OpenDNS and you can Google it from your Android O Smart Device!

PeaceOut!

RCN.ini (VZW.ini to follow)

  1. 8.8.4.4 google-public-dns-b.google.com
    8.8.8.8 google-public-dns-a.google.com
    192.168.85.1 Non-routable local internet address
    4.2.2.1 a.resolvers.level3.net
    4.2.2.2 b.resolvers.Level3.net
    4.2.2.3 c.resolvers.level3.net
    4.2.2.4 d.resolvers.level3.net
    4.2.2.5 e.resolvers.level3.net
    4.2.2.6 f.resolvers.level3.net
    64.136.44.73 vgs-dns.dca.untd.com
    64.212.106.84 dns1.jfk.gblx.net
    64.215.98.148 dns1.lon.gblx.net
    68.105.28.11 cdns1.cox.net
    68.105.28.12 cdns2.cox.net
    74.82.42.42 ordns.he.net
    129.250.35.250 x.ns.gin.ntt.net
    129.250.35.251 y.ns.gin.ntt.net
    141.1.1.1 cns1.cw.net
    141.1.27.249 euro-cns1.cw.net
    151.196.0.37 world2.bellatlantic.net
    151.196.0.38 nsbalt.bellatlantic.net
    151.197.0.39 home4.bellatlantic.net
    151.199.0.39 home3.bellatlantic.net
    151.201.0.38 nspitt.bellatlantic.net
    156.154.70.1 rdns1.ultradns.net
    156.154.70.22 路路路 no official Internet DNS name 路路路
    195.27.1.1 cns2.cw.net
    198.6.1.4 cache03.ns.uu.net
    199.2.252.10 ns2.sprintlink.net
    199.45.32.37 world1.bellatlantic.net
    199.45.32.38 nsdc.bellatlantic.net
    199.45.32.40 legacy-ns1.bellatlantic.net
    206.124.65.253 boingo.gte.net
    206.165.6.12 dns2.phx.gblx.net
    207.172.3.9 ns2.dns.rcn.net
    207.172.11.72 watchmen.dns.rcn.net
    207.172.11.73 neomen.dns.rcn.net
    208.59.247.45 ns2.dns.rcn.net
    208.67.220.220 resolver2.opendns.com
    208.67.222.123 resolver1-fs.opendns.com
    208.67.222.220 resolver3.opendns.com
    208.78.24.238 dns1.nyc.dns-roots.net
    209.87.64.70 ns1.dsl.net
    209.87.79.232 ns2.dsl.net
    209.130.139.2 dns2.roc.gblx.net
    209.244.0.3 resolver1.level3.net
    209.244.0.4 resolver2.level3.net
    216.27.175.2 dns.atl1.speakeasy.net
    216.52.126.1 ns1.wdc002.pnap.net
    216.146.35.35 resolver1.dyndnsinternetguide.com
    216.146.36.36 resolver2.dyndnsinternetguide.com
    216.170.153.146 ns8.dns.tds.net
    216.254.95.2 dns.nyc1.speakeasy.net

VZW.ini

  1. 8.8.4.4 google-public-dns-b.google.com
    8.8.8.8 google-public-dns-a.google.com
    192.168.1.1 FIOS_Quantum_Gateway.fios-router.home
    4.2.2.1 a.resolvers.level3.net
    4.2.2.2 b.resolvers.Level3.net
    4.2.2.3 c.resolvers.level3.net
    4.2.2.4 d.resolvers.level3.net
    4.2.2.5 e.resolvers.level3.net
    4.2.2.6 f.resolvers.level3.net
    64.105.199.74 h-64-105-199-74.mcln.va.globalcapacity.com
    64.212.106.84 dns1.jfk.gblx.net
    64.215.98.148 dns1.lon.gblx.net
    66.28.0.45 res1.dns.cogentco.com
    66.92.159.2 dns.wdc1.speakeasy.net
    67.17.215.132 dns1.snv.gblx.net
    68.105.28.11 cdns1.cox.net
    68.237.161.14 nsnyny02.verizon.net
    71.252.0.12 nsrest01.verizon.net
    74.82.42.42 ordns.he.net
    129.250.35.250 x.ns.gin.ntt.net
    141.1.1.1 cns1.cw.net
    141.1.27.249 euro-cns1.cw.net
    151.196.0.37 world2.bellatlantic.net
    151.196.0.38 nsbalt.bellatlantic.net
    151.199.0.39 home3.bellatlantic.net
    151.201.0.38 nspitt.bellatlantic.net
    156.154.70.22 ... determining domain name ...
    166.102.165.13 nsvip02.windstream.net
    198.6.1.3 cache02.ns.uu.net
    199.2.252.10 ns2.sprintlink.net
    199.45.32.37 world1.bellatlantic.net
    199.45.32.38 nsdc.bellatlantic.net
    199.45.32.40 legacy-ns1.bellatlantic.net
    199.45.32.43 home1.bellatlantic.net
    204.97.212.10 ns3.sprintlink.net
    205.171.2.65 resolver.qwest.net
    205.171.3.25 redirect1.qwest.net
    205.171.3.65 resolver1.qwest.net
    206.124.65.253 boingo.gte.net
    206.165.6.11 dns1.phx.gblx.net
    206.165.6.12 dns2.phx.gblx.net
    208.67.220.123 resolver2-fs.opendns.com
    208.67.220.220 resolver2.opendns.com
    208.67.222.123 resolver1-fs.opendns.com
    208.67.222.220 resolver3.opendns.com
    208.67.222.222 resolver1.opendns.com
    209.130.139.2 dns2.roc.gblx.net
    209.244.0.3 resolver1.level3.net
    209.244.0.4 resolver2.level3.net
    216.27.175.2 dns.atl1.speakeasy.net
    216.52.126.1 ns1.wdc002.pnap.net
    216.146.35.35 resolver1.dyndnsinternetguide.com
    216.146.36.36 resolver2.dyndnsinternetguide.com
LawrenceC
Moderator Emeritus

As this thread is now over two years old, it will be locked in order to keep discussions current. If you have the same or a similar question/issue we invite you to start a new thread on the topic.

0 Likes
Reply