Verizon blocking Google DNS?

[Jake]

Verizon seems to be blocking google DNS. I can't get results from
8.8.8.8 or 8.8.4.4

nslookup google.com 8.8.4.4
Server: google-public-dns-b.google.com
Address: 8.8.4.4

DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
*** Request to google-public-dns-b.google.com timed-out

C:\Users\Jake Miller>nslookup google.com 8.8.8.8
Server: google-public-dns-a.google.com
Address: 8.8.8.8

DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
*** Request to google-public-dns-a.google.com timed-out

[Paul S. R. Chisholm]

Sorry to hear that, Jake. It's working okay for me from home, both
with Verizon FIOS and Verizon Wireless.

Roughly where are you? Which Verizon service are you using?

The nslookup commands were helpful, but it would help further if you
would let us know what the following return:

tracert -d 8.8.4.4

tracert -d 8.8.8.8

Thanks. --PSRC

[Jake]

Strange, It was broken all day (My kids complained). I have FIOS and
I'm located in Maryland. I could ping and tracert to them, just not
query DNS. Once I switched back to Verizon DNS servers I could surf
again, but still couldn't connect to port 53 on the google DNS
servers. I just tried again, and it's working now. I hate the
verizon DNS service, so I hope this isn't a recurring issue. I wonder
what would cause me to not be able to query the google DNS servers....

Here's the tracert:

Tracing route to FWDR-8.FWDR-8.FWDR-8.FWDR-8 [8.8.8.8]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms Wireless_Broadband_Router.home
[192.168.1.1]
2 19 ms 9 ms 8 ms L100.BLTMMD-VFTTP-45.verizon-gni.net
[98.117.58.
1]
3 14 ms 8 ms 9 ms G10-0-5-445.BLTMMD-LCR-04.verizon-
gni.net [130.8
1.110.168]
4 13 ms 67 ms 13 ms so-2-0-0-0.PHIL-BB-RTR2.verizon-
gni.net [130.81.
28.82]
5 20 ms 23 ms 24 ms so-7-1-0-0.RES-BB-RTR2.verizon-gni.net
[130.81.1
9.106]
6 26 ms 20 ms 76 ms 0.xe-10-0-0.BR2.IAD8.ALTER.NET
[152.63.34.9]
7 22 ms 20 ms 25 ms te-11-0-0.edge1.Washington4.level3.net
[4.68.111
.253]
8 19 ms 41 ms 38 ms vlan79.csw2.Washington1.Level3.net
[4.68.17.126]

9 38 ms 33 ms 33 ms ae-74-74.ebr4.Washington1.Level3.net
[4.69.134.1
81]
10 23 ms 25 ms 21 ms ae-3-3.ebr1.NewYork1.Level3.net
[4.69.132.94]
11 22 ms 39 ms 31 ms ae-91-91.csw4.NewYork1.Level3.net
[4.69.134.78]

12 22 ms 24 ms 25 ms ae-4-99.edge1.NewYork1.Level3.net
[4.68.16.206]

13 23 ms 24 ms 34 ms GOOGLE-INC.edge1.NewYork1.Level3.net
[4.71.172.8
6]
14 132 ms 29 ms 25 ms 72.14.238.232
15 29 ms 28 ms 29 ms 209.85.248.216
16 33 ms 29 ms 29 ms 64.233.175.219
17 41 ms 34 ms 36 ms 72.14.232.25
18 33 ms 32 ms 29 ms FWDR-8.FWDR-8.FWDR-8.FWDR-8 [8.8.8.8]

Trace complete.

On Mar 4, 9:26 pm, "Paul S. R. Chisholm" <psrchish...@gmail.com>
wrote:

[Dan]

I'm on FiOS in Cherry Hill, NJ. Been playin around using Google DNS,
OpenDNS, etc. Never had a problem with blockages. Mostly, I've
found that Verizon's DNS is usually much faster than Google's or even
OpenDNS.

To change the DNS for our whole LAN, I've been doing it in the
Actiontec router.

My Network > Network Connections > Broadband Connection (Ethernet) > Settings.

Take a look at the DNS assignments in the Actiontec router. Verizon
offers two sets. The ones that end in .12 redirect typo queries to
Yahoo. To opt-out of that "feature", change the DNS entries to end
in .14. Those servers do not redirect, and seem faster.

FWIW,
- Dan.