Anybody else having issues with google dns? ..................................... *Luke Rockwell* Systems and Support Analyst Information Technology
My monitoring system is getting responses. Just asking it a simple A record. Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 On Dec 6, 2013 1:31 PM, "Luke Rockwell" <luke.rockwell@alumni.berkeley.edu> wrote:
Anybody else having issues with google dns?
..................................... *Luke Rockwell* Systems and Support Analyst Information Technology
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
On 12/06/13 10:25 -0800, Luke Rockwell wrote:
Anybody else having issues with google dns?
No problems here (south central US): $ time dig +short @8.8.8.8 google.com a 74.125.225.226 74.125.225.230 74.125.225.233 74.125.225.238 74.125.225.232 74.125.225.227 74.125.225.225 74.125.225.229 74.125.225.224 74.125.225.231 74.125.225.228 real 0m0.077s user 0m0.012s sys 0m0.000s $ time dig +short @8.8.4.4 google.com a 74.125.225.231 74.125.225.229 74.125.225.227 74.125.225.238 74.125.225.224 74.125.225.233 74.125.225.230 74.125.225.226 74.125.225.225 74.125.225.228 74.125.225.232 real 0m0.056s user 0m0.012s sys 0m0.000s $ traceroute 8.8.8.8 traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets 4 olp-67-217-150-202.olp.net (67.217.150.202) 1.758 ms 1.756 ms 1.709 ms 5 vlan3823.car1.Dallas1.Level3.net (4.59.113.73) 33.776 ms 33.781 ms 33.773 ms 6 * * * 7 Google-level3-3x10G.Dallas.Level3.net (4.68.70.166) 33.395 ms 36.129 ms 36.112 ms 8 * * * 9 72.14.237.215 (72.14.237.215) 33.802 ms 72.14.237.221 (72.14.237.221) 47.775 ms 72.14.237.215 (72.14.237.215) 34.017 ms 10 209.85.243.178 (209.85.243.178) 41.019 ms 216.239.47.121 (216.239.47.121) 41.025 ms 41.115 ms 11 216.239.46.59 (216.239.46.59) 41.332 ms 216.239.46.39 (216.239.46.39) 41.934 ms 216.239.46.59 (216.239.46.59) 41.939 ms 12 * * * 13 google-public-dns-a.google.com (8.8.8.8) 40.401 ms 40.394 ms 40.115 ms $ traceroute 8.8.4.4 traceroute to 8.8.4.4 (8.8.4.4), 30 hops max, 60 byte packets 4 olp-67-217-150-202.olp.net (67.217.150.202) 2.095 ms 2.089 ms 2.083 ms 5 vlan3823.car1.dallas1.level3.net (4.59.113.73) 33.971 ms 33.972 ms 33.966 ms 6 * * * 7 google-level3-3x10g.dallas.level3.net (4.68.70.166) 33.683 ms 33.691 ms 33.680 ms 8 72.14.233.67 (72.14.233.67) 33.840 ms 33.841 ms 72.14.233.65 (72.14.233.65) 33.963 ms 9 72.14.237.221 (72.14.237.221) 35.000 ms 72.14.237.217 (72.14.237.217) 35.000 ms 72.14.237.219 (72.14.237.219) 35.104 ms 10 209.85.243.178 (209.85.243.178) 41.348 ms 41.352 ms 41.491 ms 11 216.239.46.63 (216.239.46.63) 41.612 ms 41.612 ms 216.239.46.61 (216.239.46.61) 41.110 ms 12 * * * 13 google-public-dns-b.google.com (8.8.4.4) 41.055 ms 40.932 ms 40.722 ms -- Dan White
It is now responding. My routers show it was offline for 5 minutes ..................................... *Luke Rockwell* Systems and Support Analyst Information Technology ..................................... Cal Alumni Association | UC Berkeley 1 Alumni House, Berkeley, CA 94720 *T* 510.900.8196 *F* 510.642.6252 ..................................... *140 Years of Alumni Excellence* *Commitment, Support, Passion* _____________________________________ *alumni.berkeley.edu <http://alumni.berkeley.edu/>* _____________________________________ *Facebook <https://www.facebook.com/CalAlumni> | LinkedIn <http://www.linkedin.com/groups?gid=70245>* On Fri, Dec 6, 2013 at 10:41 AM, Dan White <dwhite@olp.net> wrote:
On 12/06/13 10:25 -0800, Luke Rockwell wrote:
Anybody else having issues with google dns?
No problems here (south central US):
$ time dig +short @8.8.8.8 google.com a 74.125.225.226 74.125.225.230 74.125.225.233 74.125.225.238 74.125.225.232 74.125.225.227 74.125.225.225 74.125.225.229 74.125.225.224 74.125.225.231 74.125.225.228
real 0m0.077s user 0m0.012s sys 0m0.000s
$ time dig +short @8.8.4.4 google.com a 74.125.225.231 74.125.225.229 74.125.225.227 74.125.225.238 74.125.225.224 74.125.225.233 74.125.225.230 74.125.225.226 74.125.225.225 74.125.225.228 74.125.225.232
real 0m0.056s user 0m0.012s sys 0m0.000s
$ traceroute 8.8.8.8 traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets 4 olp-67-217-150-202.olp.net (67.217.150.202) 1.758 ms 1.756 ms 1.709 ms 5 vlan3823.car1.Dallas1.Level3.net (4.59.113.73) 33.776 ms 33.781 ms 33.773 ms 6 * * * 7 Google-level3-3x10G.Dallas.Level3.net (4.68.70.166) 33.395 ms 36.129 ms 36.112 ms 8 * * * 9 72.14.237.215 (72.14.237.215) 33.802 ms 72.14.237.221 (72.14.237.221) 47.775 ms 72.14.237.215 (72.14.237.215) 34.017 ms 10 209.85.243.178 (209.85.243.178) 41.019 ms 216.239.47.121 (216.239.47.121) 41.025 ms 41.115 ms 11 216.239.46.59 (216.239.46.59) 41.332 ms 216.239.46.39 (216.239.46.39) 41.934 ms 216.239.46.59 (216.239.46.59) 41.939 ms 12 * * * 13 google-public-dns-a.google.com (8.8.8.8) 40.401 ms 40.394 ms 40.115 ms
$ traceroute 8.8.4.4 traceroute to 8.8.4.4 (8.8.4.4), 30 hops max, 60 byte packets 4 olp-67-217-150-202.olp.net (67.217.150.202) 2.095 ms 2.089 ms 2.083 ms 5 vlan3823.car1.dallas1.level3.net (4.59.113.73) 33.971 ms 33.972 ms 33.966 ms 6 * * * 7 google-level3-3x10g.dallas.level3.net (4.68.70.166) 33.683 ms 33.691 ms 33.680 ms 8 72.14.233.67 (72.14.233.67) 33.840 ms 33.841 ms 72.14.233.65 (72.14.233.65) 33.963 ms 9 72.14.237.221 (72.14.237.221) 35.000 ms 72.14.237.217 (72.14.237.217) 35.000 ms 72.14.237.219 (72.14.237.219) 35.104 ms 10 209.85.243.178 (209.85.243.178) 41.348 ms 41.352 ms 41.491 ms 11 216.239.46.63 (216.239.46.63) 41.612 ms 41.612 ms 216.239.46.61 (216.239.46.61) 41.110 ms 12 * * * 13 google-public-dns-b.google.com (8.8.4.4) 41.055 ms 40.932 ms 40.722 ms
-- Dan White
On 12/06/13 12:41 -0600, Dan White wrote:
On 12/06/13 10:25 -0800, Luke Rockwell wrote:
Anybody else having issues with google dns?
No problems here (south central US):
$ time dig +short @8.8.8.8 google.com a 74.125.225.226 74.125.225.230 74.125.225.233 74.125.225.238 74.125.225.232 74.125.225.227 74.125.225.225 74.125.225.229 74.125.225.224 74.125.225.231 74.125.225.228
real 0m0.077s user 0m0.012s sys 0m0.000s
One of our DNS servers just had incorrect data cached for google.com and www.google.com: dwhite@quark:~$ dig www.google.com ;; QUESTION SECTION: ;www.google.com. IN A ;; ANSWER SECTION: www.google.com. 24 IN A 201.130.208.23 www.google.com. 24 IN A 201.130.208.44 www.google.com. 24 IN A 201.130.208.34 www.google.com. 24 IN A 201.130.208.45 www.google.com. 24 IN A 201.130.208.29 www.google.com. 24 IN A 201.130.208.30 www.google.com. 24 IN A 201.130.208.53 www.google.com. 24 IN A 201.130.208.38 www.google.com. 24 IN A 201.130.208.19 www.google.com. 24 IN A 201.130.208.49 www.google.com. 24 IN A 201.130.208.59 www.google.com. 24 IN A 201.130.208.57 www.google.com. 24 IN A 201.130.208.27 www.google.com. 24 IN A 201.130.208.42 www.google.com. 24 IN A 201.130.208.15 After the 24 second cache timeout, the correct (google space) IPs populated: ;; ANSWER SECTION: google.com. 138 IN A 74.125.227.104 google.com. 138 IN A 74.125.227.100 google.com. 138 IN A 74.125.227.101 google.com. 138 IN A 74.125.227.102 google.com. 138 IN A 74.125.227.105 google.com. 138 IN A 74.125.227.97 google.com. 138 IN A 74.125.227.98 google.com. 138 IN A 74.125.227.110 google.com. 138 IN A 74.125.227.96 google.com. 138 IN A 74.125.227.103 google.com. 138 IN A 74.125.227.99 I did not notice this on any other DNS servers. -- Dan White
Those are valid Google IPs, so this is likely working as intended and you were just temporarily being load-balanced to a different datacenter. If you're still concerned, please send me more detail off-list. Damian On Fri, Dec 6, 2013 at 1:27 PM, Dan White <dwhite@olp.net> wrote:
On 12/06/13 12:41 -0600, Dan White wrote:
On 12/06/13 10:25 -0800, Luke Rockwell wrote:
Anybody else having issues with google dns?
No problems here (south central US):
$ time dig +short @8.8.8.8 google.com a 74.125.225.226 74.125.225.230 74.125.225.233 74.125.225.238 74.125.225.232 74.125.225.227 74.125.225.225 74.125.225.229 74.125.225.224 74.125.225.231 74.125.225.228
real 0m0.077s user 0m0.012s sys 0m0.000s
One of our DNS servers just had incorrect data cached for google.com and www.google.com:
dwhite@quark:~$ dig www.google.com
;; QUESTION SECTION: ;www.google.com. IN A
;; ANSWER SECTION: www.google.com. 24 IN A 201.130.208.23 www.google.com. 24 IN A 201.130.208.44 www.google.com. 24 IN A 201.130.208.34 www.google.com. 24 IN A 201.130.208.45 www.google.com. 24 IN A 201.130.208.29 www.google.com. 24 IN A 201.130.208.30 www.google.com. 24 IN A 201.130.208.53 www.google.com. 24 IN A 201.130.208.38 www.google.com. 24 IN A 201.130.208.19 www.google.com. 24 IN A 201.130.208.49 www.google.com. 24 IN A 201.130.208.59 www.google.com. 24 IN A 201.130.208.57 www.google.com. 24 IN A 201.130.208.27 www.google.com. 24 IN A 201.130.208.42 www.google.com. 24 IN A 201.130.208.15
After the 24 second cache timeout, the correct (google space) IPs populated:
;; ANSWER SECTION: google.com. 138 IN A 74.125.227.104 google.com. 138 IN A 74.125.227.100 google.com. 138 IN A 74.125.227.101 google.com. 138 IN A 74.125.227.102 google.com. 138 IN A 74.125.227.105 google.com. 138 IN A 74.125.227.97 google.com. 138 IN A 74.125.227.98 google.com. 138 IN A 74.125.227.110 google.com. 138 IN A 74.125.227.96 google.com. 138 IN A 74.125.227.103 google.com. 138 IN A 74.125.227.99
I did not notice this on any other DNS servers.
-- Dan White _______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
If they are valid Google IPs then your rDNS could do with some updating... 23.208.130.201.in-addr.arpa name = 201-130-208-23-cable.cybercable.net.mx. inetnum: 201.130.192/18 status: allocated aut-num: N/A owner: Cablevision Red, S.A de C.V. ownerid: MX-CRSC10-LACNIC responsible: Luis Vielma Ordo<F1>es address: Av. Naciones Unidas, 5526, Col. Vallarta Universidad address: 45110 - Guadalajara - JL country: MX Scott On Fri, Dec 6, 2013 at 2:14 PM, Damian Menscher <damian@google.com> wrote:
Those are valid Google IPs, so this is likely working as intended and you were just temporarily being load-balanced to a different datacenter. If you're still concerned, please send me more detail off-list.
Damian
On Fri, Dec 6, 2013 at 1:27 PM, Dan White <dwhite@olp.net> wrote:
On 12/06/13 12:41 -0600, Dan White wrote:
On 12/06/13 10:25 -0800, Luke Rockwell wrote:
Anybody else having issues with google dns?
No problems here (south central US):
$ time dig +short @8.8.8.8 google.com a 74.125.225.226 74.125.225.230 74.125.225.233 74.125.225.238 74.125.225.232 74.125.225.227 74.125.225.225 74.125.225.229 74.125.225.224 74.125.225.231 74.125.225.228
real 0m0.077s user 0m0.012s sys 0m0.000s
One of our DNS servers just had incorrect data cached for google.com and www.google.com:
dwhite@quark:~$ dig www.google.com
;; QUESTION SECTION: ;www.google.com. IN A
;; ANSWER SECTION: www.google.com. 24 IN A 201.130.208.23 www.google.com. 24 IN A 201.130.208.44 www.google.com. 24 IN A 201.130.208.34 www.google.com. 24 IN A 201.130.208.45 www.google.com. 24 IN A 201.130.208.29 www.google.com. 24 IN A 201.130.208.30 www.google.com. 24 IN A 201.130.208.53 www.google.com. 24 IN A 201.130.208.38 www.google.com. 24 IN A 201.130.208.19 www.google.com. 24 IN A 201.130.208.49 www.google.com. 24 IN A 201.130.208.59 www.google.com. 24 IN A 201.130.208.57 www.google.com. 24 IN A 201.130.208.27 www.google.com. 24 IN A 201.130.208.42 www.google.com. 24 IN A 201.130.208.15
After the 24 second cache timeout, the correct (google space) IPs populated:
;; ANSWER SECTION: google.com. 138 IN A 74.125.227.104 google.com. 138 IN A 74.125.227.100 google.com. 138 IN A 74.125.227.101 google.com. 138 IN A 74.125.227.102 google.com. 138 IN A 74.125.227.105 google.com. 138 IN A 74.125.227.97 google.com. 138 IN A 74.125.227.98 google.com. 138 IN A 74.125.227.110 google.com. 138 IN A 74.125.227.96 google.com. 138 IN A 74.125.227.103 google.com. 138 IN A 74.125.227.99
I did not notice this on any other DNS servers.
-- Dan White _______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
On Dec 6, 2013, at 5:17 PM, Scott Howard <scott@doc.net.au> wrote:
If they are valid Google IPs then your rDNS could do with some updating…
Unfortunately not all valid Google IPs are actually, um, Google IPs. Some are Google Caches: https://peering.google.com/about/ggc.html For various non-technical, contractual type reasons these are not all documented anywhere publicly… W
23.208.130.201.in-addr.arpa name = 201-130-208-23-cable.cybercable.net.mx.
inetnum: 201.130.192/18 status: allocated aut-num: N/A owner: Cablevision Red, S.A de C.V. ownerid: MX-CRSC10-LACNIC responsible: Luis Vielma Ordo<F1>es address: Av. Naciones Unidas, 5526, Col. Vallarta Universidad address: 45110 - Guadalajara - JL country: MX
Scott
On Fri, Dec 6, 2013 at 2:14 PM, Damian Menscher <damian@google.com> wrote: Those are valid Google IPs, so this is likely working as intended and you were just temporarily being load-balanced to a different datacenter. If you're still concerned, please send me more detail off-list.
Damian
On Fri, Dec 6, 2013 at 1:27 PM, Dan White <dwhite@olp.net> wrote: On 12/06/13 12:41 -0600, Dan White wrote: On 12/06/13 10:25 -0800, Luke Rockwell wrote: Anybody else having issues with google dns?
No problems here (south central US):
$ time dig +short @8.8.8.8 google.com a 74.125.225.226 74.125.225.230 74.125.225.233 74.125.225.238 74.125.225.232 74.125.225.227 74.125.225.225 74.125.225.229 74.125.225.224 74.125.225.231 74.125.225.228
real 0m0.077s user 0m0.012s sys 0m0.000s
One of our DNS servers just had incorrect data cached for google.com and www.google.com:
dwhite@quark:~$ dig www.google.com
;; QUESTION SECTION: ;www.google.com. IN A
;; ANSWER SECTION: www.google.com. 24 IN A 201.130.208.23 www.google.com. 24 IN A 201.130.208.44 www.google.com. 24 IN A 201.130.208.34 www.google.com. 24 IN A 201.130.208.45 www.google.com. 24 IN A 201.130.208.29 www.google.com. 24 IN A 201.130.208.30 www.google.com. 24 IN A 201.130.208.53 www.google.com. 24 IN A 201.130.208.38 www.google.com. 24 IN A 201.130.208.19 www.google.com. 24 IN A 201.130.208.49 www.google.com. 24 IN A 201.130.208.59 www.google.com. 24 IN A 201.130.208.57 www.google.com. 24 IN A 201.130.208.27 www.google.com. 24 IN A 201.130.208.42 www.google.com. 24 IN A 201.130.208.15
After the 24 second cache timeout, the correct (google space) IPs populated:
;; ANSWER SECTION: google.com. 138 IN A 74.125.227.104 google.com. 138 IN A 74.125.227.100 google.com. 138 IN A 74.125.227.101 google.com. 138 IN A 74.125.227.102 google.com. 138 IN A 74.125.227.105 google.com. 138 IN A 74.125.227.97 google.com. 138 IN A 74.125.227.98 google.com. 138 IN A 74.125.227.110 google.com. 138 IN A 74.125.227.96 google.com. 138 IN A 74.125.227.103 google.com. 138 IN A 74.125.227.99
I did not notice this on any other DNS servers.
-- Dan White _______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
-- "Let's just say that if complete and utter chaos was lightning, he'd be the sort to stand on a hilltop in a thunderstorm wearing wet copper armour and shouting 'All gods are bastards'." -- Rincewind discussing Twoflower (Terry Pratchett, The Colour of Magic)
I should have noted that during the time that www.google.com was resolving to 201.130.208.x, access to google.com and youtube.com was unavailable (timeouts within a browser). On 12/06/13 14:14 -0800, Damian Menscher wrote:
Those are valid Google IPs, so this is likely working as intended and you were just temporarily being load-balanced to a different datacenter. If you're still concerned, please send me more detail off-list.
Damian
On Fri, Dec 6, 2013 at 1:27 PM, Dan White <dwhite@olp.net> wrote:
On 12/06/13 12:41 -0600, Dan White wrote:
On 12/06/13 10:25 -0800, Luke Rockwell wrote:
Anybody else having issues with google dns?
No problems here (south central US):
$ time dig +short @8.8.8.8 google.com a 74.125.225.226 74.125.225.230 74.125.225.233 74.125.225.238 74.125.225.232 74.125.225.227 74.125.225.225 74.125.225.229 74.125.225.224 74.125.225.231 74.125.225.228
real 0m0.077s user 0m0.012s sys 0m0.000s
One of our DNS servers just had incorrect data cached for google.com and www.google.com:
dwhite@quark:~$ dig www.google.com
;; QUESTION SECTION: ;www.google.com. IN A
;; ANSWER SECTION: www.google.com. 24 IN A 201.130.208.23 www.google.com. 24 IN A 201.130.208.44 www.google.com. 24 IN A 201.130.208.34 www.google.com. 24 IN A 201.130.208.45 www.google.com. 24 IN A 201.130.208.29 www.google.com. 24 IN A 201.130.208.30 www.google.com. 24 IN A 201.130.208.53 www.google.com. 24 IN A 201.130.208.38 www.google.com. 24 IN A 201.130.208.19 www.google.com. 24 IN A 201.130.208.49 www.google.com. 24 IN A 201.130.208.59 www.google.com. 24 IN A 201.130.208.57 www.google.com. 24 IN A 201.130.208.27 www.google.com. 24 IN A 201.130.208.42 www.google.com. 24 IN A 201.130.208.15
After the 24 second cache timeout, the correct (google space) IPs populated:
;; ANSWER SECTION: google.com. 138 IN A 74.125.227.104 google.com. 138 IN A 74.125.227.100 google.com. 138 IN A 74.125.227.101 google.com. 138 IN A 74.125.227.102 google.com. 138 IN A 74.125.227.105 google.com. 138 IN A 74.125.227.97 google.com. 138 IN A 74.125.227.98 google.com. 138 IN A 74.125.227.110 google.com. 138 IN A 74.125.227.96 google.com. 138 IN A 74.125.227.103 google.com. 138 IN A 74.125.227.99
I did not notice this on any other DNS servers.
-- Dan White
Thanks for the additional detail. The responsible team is investigating what happened. Damian On Fri, Dec 6, 2013 at 2:25 PM, Dan White <dwhite@olp.net> wrote:
I should have noted that during the time that www.google.com was resolving to 201.130.208.x, access to google.com and youtube.com was unavailable (timeouts within a browser).
On 12/06/13 14:14 -0800, Damian Menscher wrote:
Those are valid Google IPs, so this is likely working as intended and you were just temporarily being load-balanced to a different datacenter. If you're still concerned, please send me more detail off-list.
Damian
On Fri, Dec 6, 2013 at 1:27 PM, Dan White <dwhite@olp.net> wrote:
On 12/06/13 12:41 -0600, Dan White wrote:
On 12/06/13 10:25 -0800, Luke Rockwell wrote:
Anybody else having issues with google dns?
No problems here (south central US):
$ time dig +short @8.8.8.8 google.com a 74.125.225.226 74.125.225.230 74.125.225.233 74.125.225.238 74.125.225.232 74.125.225.227 74.125.225.225 74.125.225.229 74.125.225.224 74.125.225.231 74.125.225.228
real 0m0.077s user 0m0.012s sys 0m0.000s
One of our DNS servers just had incorrect data cached for google.com and www.google.com:
dwhite@quark:~$ dig www.google.com
;; QUESTION SECTION: ;www.google.com. IN A
;; ANSWER SECTION: www.google.com. 24 IN A 201.130.208.23 www.google.com. 24 IN A 201.130.208.44 www.google.com. 24 IN A 201.130.208.34 www.google.com. 24 IN A 201.130.208.45 www.google.com. 24 IN A 201.130.208.29 www.google.com. 24 IN A 201.130.208.30 www.google.com. 24 IN A 201.130.208.53 www.google.com. 24 IN A 201.130.208.38 www.google.com. 24 IN A 201.130.208.19 www.google.com. 24 IN A 201.130.208.49 www.google.com. 24 IN A 201.130.208.59 www.google.com. 24 IN A 201.130.208.57 www.google.com. 24 IN A 201.130.208.27 www.google.com. 24 IN A 201.130.208.42 www.google.com. 24 IN A 201.130.208.15
After the 24 second cache timeout, the correct (google space) IPs populated:
;; ANSWER SECTION: google.com. 138 IN A 74.125.227.104 google.com. 138 IN A 74.125.227.100 google.com. 138 IN A 74.125.227.101 google.com. 138 IN A 74.125.227.102 google.com. 138 IN A 74.125.227.105 google.com. 138 IN A 74.125.227.97 google.com. 138 IN A 74.125.227.98 google.com. 138 IN A 74.125.227.110 google.com. 138 IN A 74.125.227.96 google.com. 138 IN A 74.125.227.103 google.com. 138 IN A 74.125.227.99
I did not notice this on any other DNS servers.
-- Dan White
In the future, a source IP, destination IP (Google has more than one DNS server), and traceroute would be useful. Damian On Fri, Dec 6, 2013 at 10:25 AM, Luke Rockwell < luke.rockwell@alumni.berkeley.edu> wrote:
Anybody else having issues with google dns?
..................................... *Luke Rockwell* Systems and Support Analyst Information Technology
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
participants (6)
-
Damian Menscher -
Dan White -
Josh Luthman -
Luke Rockwell -
Scott Howard -
Warren Kumari