I've checked from multiple networks and recursive name servers. It seems all of the authoritative name servers for sun.com are not responding to requests. Is everyone else seeing this as well? Traces look the same to all sun.com name servers I get from glue data via a.gtld-servers.net. Tracing route to 192.18.43.12 over a maximum of 30 hops 1 <1 ms 5 ms <1 ms vlan40.s1-lnsskinj.dellservices.net [155.16.137.129] 2 <1 ms <1 ms <1 ms vlan31.colo3.tdc.nwt.dellservices.net [69.39.183.177] 3 <1 ms <1 ms <1 ms ge1-6.core2.tdc.nwt.dellservices.net [66.97.0.13] 4 4 ms 4 ms 4 ms ge1-9.core1.ccs.phl.dellservices.net [216.182.7.58] 5 4 ms 4 ms 4 ms 12.116.229.17 6 9 ms 8 ms 8 ms cr84.phlpa.ip.att.net [12.123.224.222] 7 17 ms 11 ms 11 ms cr2.phlpa.ip.att.net [12.122.107.117] 8 12 ms 10 ms 12 ms cr1.wswdc.ip.att.net [12.122.4.54] 9 7 ms 7 ms 7 ms gar13.n54ny.ip.att.net [12.122.81.245] 10 9 ms 9 ms 9 ms 192.205.35.106 11 10 ms 10 ms 10 ms te0-1-0-5.mpd22.dca01.atlas.cogentco.com [154.54.26.121] 12 26 ms 26 ms 27 ms te0-2-0-4.mpd22.ord01.atlas.cogentco.com [154.54.40.242] 13 45 ms 45 ms 45 ms te0-1-0-2.mpd22.mci01.atlas.cogentco.com [154.54.3.202] 14 57 ms 57 ms 57 ms te4-4.mpd02.den01.atlas.cogentco.com [154.54.45.49] 15 57 ms 57 ms 57 ms te3-2.ccr01.den03.atlas.cogentco.com [154.54.83.34] 16 80 ms 80 ms 80 ms 38.122.114.46 17 80 ms 80 ms 80 ms mpr2.den.ve3-bbnet2.pnap.net [216.52.40.72] 18 * * * Request timed out. -Vinny
Perhaps by design? http://www.oracle.com/us/sun/index.htm On 11/04/2012, at 2:07 PM, <Vinny_Abello@Dell.com> wrote: I’ve checked from multiple networks and recursive name servers. It seems all of the authoritative name servers for sun.com<http://sun.com> are not responding to requests. Is everyone else seeing this as well? Traces look the same to all sun.com<http://sun.com> name servers I get from glue data via a.gtld-servers.net<http://a.gtld-servers.net>. Tracing route to 192.18.43.12 over a maximum of 30 hops 1 <1 ms 5 ms <1 ms vlan40.s1-lnsskinj.dellservices.net<http://vlan40.s1-lnsskinj.dellservices.net> [155.16.137.129] 2 <1 ms <1 ms <1 ms vlan31.colo3.tdc.nwt.dellservices.net [69.39.183.177] 3 <1 ms <1 ms <1 ms ge1-6.core2.tdc.nwt.dellservices.net [66.97.0.13] 4 4 ms 4 ms 4 ms ge1-9.core1.ccs.phl.dellservices.net [216.182.7.58] 5 4 ms 4 ms 4 ms 12.116.229.17 6 9 ms 8 ms 8 ms cr84.phlpa.ip.att.net [12.123.224.222] 7 17 ms 11 ms 11 ms cr2.phlpa.ip.att.net [12.122.107.117] 8 12 ms 10 ms 12 ms cr1.wswdc.ip.att.net [12.122.4.54] 9 7 ms 7 ms 7 ms gar13.n54ny.ip.att.net [12.122.81.245] 10 9 ms 9 ms 9 ms 192.205.35.106 11 10 ms 10 ms 10 ms te0-1-0-5.mpd22.dca01.atlas.cogentco.com [154.54.26.121] 12 26 ms 26 ms 27 ms te0-2-0-4.mpd22.ord01.atlas.cogentco.com [154.54.40.242] 13 45 ms 45 ms 45 ms te0-1-0-2.mpd22.mci01.atlas.cogentco.com [154.54.3.202] 14 57 ms 57 ms 57 ms te4-4.mpd02.den01.atlas.cogentco.com [154.54.45.49] 15 57 ms 57 ms 57 ms te3-2.ccr01.den03.atlas.cogentco.com [154.54.83.34] 16 80 ms 80 ms 80 ms 38.122.114.46 17 80 ms 80 ms 80 ms mpr2.den.ve3-bbnet2.pnap.net [216.52.40.72] 18 * * * Request timed out. -Vinny _______________________________________________ Outages mailing list Outages@outages.org<mailto:Outages@outages.org> https://puck.nether.net/mailman/listinfo/outages
Old news finally comes to fruition? http://www.theregister.co.uk/2011/03/16/oracle_closes_sun_domain/ On 4/11/12 12:37 AM, Vinny_Abello@Dell.com wrote:
I've checked from multiple networks and recursive name servers. It seems all of the authoritative name servers for sun.com are not responding to requests. Is everyone else seeing this as well?
Traces look the same to all sun.com name servers I get from glue data via a.gtld-servers.net.
Tracing route to 192.18.43.12 over a maximum of 30 hops
1 <1 ms 5 ms <1 ms vlan40.s1-lnsskinj.dellservices.net [155.16.137.129]
2 <1 ms <1 ms <1 ms vlan31.colo3.tdc.nwt.dellservices.net [69.39.183.177]
3 <1 ms <1 ms <1 ms ge1-6.core2.tdc.nwt.dellservices.net [66.97.0.13]
4 4 ms 4 ms 4 ms ge1-9.core1.ccs.phl.dellservices.net [216.182.7.58]
5 4 ms 4 ms 4 ms 12.116.229.17
6 9 ms 8 ms 8 ms cr84.phlpa.ip.att.net [12.123.224.222]
7 17 ms 11 ms 11 ms cr2.phlpa.ip.att.net [12.122.107.117]
8 12 ms 10 ms 12 ms cr1.wswdc.ip.att.net [12.122.4.54]
9 7 ms 7 ms 7 ms gar13.n54ny.ip.att.net [12.122.81.245]
10 9 ms 9 ms 9 ms 192.205.35.106
11 10 ms 10 ms 10 ms te0-1-0-5.mpd22.dca01.atlas.cogentco.com [154.54.26.121]
12 26 ms 26 ms 27 ms te0-2-0-4.mpd22.ord01.atlas.cogentco.com [154.54.40.242]
13 45 ms 45 ms 45 ms te0-1-0-2.mpd22.mci01.atlas.cogentco.com [154.54.3.202]
14 57 ms 57 ms 57 ms te4-4.mpd02.den01.atlas.cogentco.com [154.54.45.49]
15 57 ms 57 ms 57 ms te3-2.ccr01.den03.atlas.cogentco.com [154.54.83.34]
16 80 ms 80 ms 80 ms 38.122.114.46
17 80 ms 80 ms 80 ms mpr2.den.ve3-bbnet2.pnap.net [216.52.40.72]
18 * * * Request timed out.
-Vinny
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
Quite possibly! However, someone running java.com messed up as nobody can download java anymore as a result. J -Vinny From: Jon Radel [mailto:jradel@vantage.com] Sent: Wednesday, April 11, 2012 1:02 AM To: Abello, Vinny Cc: outages@outages.org Subject: Re: [outages] sun.com name servers unreachable? Old news finally comes to fruition? http://www.theregister.co.uk/2011/03/16/oracle_closes_sun_domain/ On 4/11/12 12:37 AM, Vinny_Abello@Dell.com<mailto:Vinny_Abello@Dell.com> wrote: I've checked from multiple networks and recursive name servers. It seems all of the authoritative name servers for sun.com are not responding to requests. Is everyone else seeing this as well? Traces look the same to all sun.com name servers I get from glue data via a.gtld-servers.net. Tracing route to 192.18.43.12 over a maximum of 30 hops 1 <1 ms 5 ms <1 ms vlan40.s1-lnsskinj.dellservices.net [155.16.137.129] 2 <1 ms <1 ms <1 ms vlan31.colo3.tdc.nwt.dellservices.net [69.39.183.177] 3 <1 ms <1 ms <1 ms ge1-6.core2.tdc.nwt.dellservices.net [66.97.0.13] 4 4 ms 4 ms 4 ms ge1-9.core1.ccs.phl.dellservices.net [216.182.7.58] 5 4 ms 4 ms 4 ms 12.116.229.17 6 9 ms 8 ms 8 ms cr84.phlpa.ip.att.net [12.123.224.222] 7 17 ms 11 ms 11 ms cr2.phlpa.ip.att.net [12.122.107.117] 8 12 ms 10 ms 12 ms cr1.wswdc.ip.att.net [12.122.4.54] 9 7 ms 7 ms 7 ms gar13.n54ny.ip.att.net [12.122.81.245] 10 9 ms 9 ms 9 ms 192.205.35.106 11 10 ms 10 ms 10 ms te0-1-0-5.mpd22.dca01.atlas.cogentco.com [154.54.26.121] 12 26 ms 26 ms 27 ms te0-2-0-4.mpd22.ord01.atlas.cogentco.com [154.54.40.242] 13 45 ms 45 ms 45 ms te0-1-0-2.mpd22.mci01.atlas.cogentco.com [154.54.3.202] 14 57 ms 57 ms 57 ms te4-4.mpd02.den01.atlas.cogentco.com [154.54.45.49] 15 57 ms 57 ms 57 ms te3-2.ccr01.den03.atlas.cogentco.com [154.54.83.34] 16 80 ms 80 ms 80 ms 38.122.114.46 17 80 ms 80 ms 80 ms mpr2.den.ve3-bbnet2.pnap.net [216.52.40.72] 18 * * * Request timed out. -Vinny _______________________________________________ Outages mailing list Outages@outages.org<mailto:Outages@outages.org> https://puck.nether.net/mailman/listinfo/outages
Oracle did disable the sun.com domain (although not at the DNS server level) close to a year ago. It lasted a few hours before they discovered a large number of other websites stopped working as a result, including parts of java.com. I doubt they would have made the same mistake twice, which leads me to guess this is probably an outage rather than a deliberate shutdown. Scott. On Tue, Apr 10, 2012 at 10:11 PM, <Vinny_Abello@dell.com> wrote:
Quite possibly! However, someone running java.com messed up as nobody can download java anymore as a result. J****
** **
-Vinny****
** **
*From:* Jon Radel [mailto:jradel@vantage.com] *Sent:* Wednesday, April 11, 2012 1:02 AM *To:* Abello, Vinny *Cc:* outages@outages.org *Subject:* Re: [outages] sun.com name servers unreachable?****
** **
Old news finally comes to fruition?
http://www.theregister.co.uk/2011/03/16/oracle_closes_sun_domain/
On 4/11/12 12:37 AM, Vinny_Abello@Dell.com wrote: ****
I’ve checked from multiple networks and recursive name servers. It seems all of the authoritative name servers for sun.com are not responding to requests. Is everyone else seeing this as well?****
****
Traces look the same to all sun.com name servers I get from glue data via a.gtld-servers.net.****
****
Tracing route to 192.18.43.12 over a maximum of 30 hops****
****
1 <1 ms 5 ms <1 ms vlan40.s1-lnsskinj.dellservices.net [155.16.137.129]****
2 <1 ms <1 ms <1 ms vlan31.colo3.tdc.nwt.dellservices.net[69.39.183.177] ****
3 <1 ms <1 ms <1 ms ge1-6.core2.tdc.nwt.dellservices.net[66.97.0.13] ****
4 4 ms 4 ms 4 ms ge1-9.core1.ccs.phl.dellservices.net[216.182.7.58] ****
5 4 ms 4 ms 4 ms 12.116.229.17****
6 9 ms 8 ms 8 ms cr84.phlpa.ip.att.net [12.123.224.222]****
7 17 ms 11 ms 11 ms cr2.phlpa.ip.att.net [12.122.107.117]****
8 12 ms 10 ms 12 ms cr1.wswdc.ip.att.net [12.122.4.54]****
9 7 ms 7 ms 7 ms gar13.n54ny.ip.att.net [12.122.81.245]****
10 9 ms 9 ms 9 ms 192.205.35.106****
11 10 ms 10 ms 10 ms te0-1-0-5.mpd22.dca01.atlas.cogentco.com[154.54.26.121] ****
12 26 ms 26 ms 27 ms te0-2-0-4.mpd22.ord01.atlas.cogentco.com[154.54.40.242] ****
13 45 ms 45 ms 45 ms te0-1-0-2.mpd22.mci01.atlas.cogentco.com[154.54.3.202] ****
14 57 ms 57 ms 57 ms te4-4.mpd02.den01.atlas.cogentco.com[154.54.45.49] ****
15 57 ms 57 ms 57 ms te3-2.ccr01.den03.atlas.cogentco.com[154.54.83.34] ****
16 80 ms 80 ms 80 ms 38.122.114.46****
17 80 ms 80 ms 80 ms mpr2.den.ve3-bbnet2.pnap.net [216.52.40.72] ****
18 * * * Request timed out.****
****
-Vinny****
****
_______________________________________________****
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
I am seeing this also. No DNS response from any of the 4 DNS server IPs. $ traceroute -n 192.18.43.12 traceroute to 192.18.43.12 (192.18.43.12), 30 hops max, 40 byte packets 1 72.20.181.1 0.454 ms 0.452 ms 0.518 ms 2 72.20.191.132 10.312 ms 10.435 ms 10.452 ms 3 72.5.252.77 10.242 ms 10.224 ms 10.324 ms 4 216.52.191.40 11.328 ms 216.52.191.105 11.599 ms 11.676 ms 5 38.104.204.73 26.291 ms 26.195 ms 26.156 ms 6 154.54.6.97 22.448 ms 22.424 ms 22.867 ms 7 154.54.46.217 22.423 ms 154.54.2.230 23.002 ms 154.54.46.217 22.388 ms 8 154.54.82.213 34.333 ms 34.261 ms 34.374 ms 9 154.54.83.34 34.809 ms 34.651 ms 34.513 ms 10 38.122.114.46 29.532 ms 29.206 ms 29.192 ms 11 216.52.40.7 29.120 ms 29.081 ms 29.136 ms 12 * * * 13 * * * 14 * * * $ traceroute -n 192.18.4.206 traceroute to 192.18.4.206 (192.18.4.206), 30 hops max, 40 byte packets 1 72.20.181.1 0.485 ms 0.470 ms 0.520 ms 2 72.20.191.132 10.405 ms 10.461 ms 10.466 ms 3 72.5.252.77 10.297 ms 10.340 ms 10.314 ms 4 216.52.191.40 29.791 ms 216.52.191.105 30.098 ms 29.843 ms 5 38.104.204.73 123.796 ms 123.795 ms 123.797 ms 6 154.54.82.29 22.665 ms 22.773 ms 22.746 ms 7 154.54.46.209 23.023 ms 154.54.80.106 22.189 ms 22.257 ms 8 154.54.82.213 93.193 ms 154.54.82.209 93.199 ms 93.172 ms 9 154.54.45.186 37.295 ms 34.561 ms 154.54.83.34 34.584 ms 10 38.122.114.46 29.169 ms 28.993 ms 29.105 ms 11 216.52.40.7 29.073 ms 28.926 ms 28.843 ms 12 * * * 13 * * * 14 * * * $ dig +norec -t A sun.com @a.gtld-servers.net ; <<>> DiG 9.6.0-APPLE-P2 <<>> +norec -t A sun.com @a.gtld-servers.net ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 48012 ;; flags: qr; QUERY: 1, ANSWER: 0, AUTHORITY: 4, ADDITIONAL: 4 ;; QUESTION SECTION: ;sun.com. IN A ;; AUTHORITY SECTION: sun.com. 172800 IN NS ns8.sun.com. sun.com. 172800 IN NS ns2.sun.com. sun.com. 172800 IN NS ns1.sun.com. sun.com. 172800 IN NS ns3.sun.com. ;; ADDITIONAL SECTION: ns8.sun.com. 172800 IN A 192.18.43.12 ns2.sun.com. 172800 IN A 192.18.99.5 ns1.sun.com. 172800 IN A 192.18.128.11 ns3.sun.com. 172800 IN A 192.18.4.206 $ dig +norec -t SOA sun.com @192.18.43.12 ; <<>> DiG 9.6.0-APPLE-P2 <<>> +norec -t SOA sun.com @192.18.43.12 ;; global options: +cmd ;; connection timed out; no servers could be reached $ dig +norec -t SOA sun.com @192.18.99.5 ; <<>> DiG 9.6.0-APPLE-P2 <<>> +norec -t SOA sun.com @192.18.99.5 ;; global options: +cmd ;; connection timed out; no servers could be reached $ dig +norec -t SOA sun.com @192.18.128.11 ; <<>> DiG 9.6.0-APPLE-P2 <<>> +norec -t SOA sun.com @192.18.128.11 ;; global options: +cmd ;; connection timed out; no servers could be reached $ dig +norec -t SOA sun.com @192.18.4.206 ; <<>> DiG 9.6.0-APPLE-P2 <<>> +norec -t SOA sun.com @192.18.4.206 ;; global options: +cmd ;; connection timed out; no servers could be reached
Same here. One of their four DNS servers, ns1.sun.com (192.18.128.11), doesn't have Cogent in the path (see http://bgptables.merit.edu/assum.php?z=&as=11479#prefixTables), but it makes no difference. None of the traceroutes I perform hit a 192.18.x.x address. Frank -----Original Message----- From: outages-bounces@outages.org [mailto:outages-bounces@outages.org] On Behalf Of Jimmy Hess Sent: Wednesday, April 11, 2012 1:01 AM To: outages@outages.org Subject: Re: [outages] sun.com name servers unreachable? I am seeing this also. No DNS response from any of the 4 DNS server IPs. $ traceroute -n 192.18.43.12 traceroute to 192.18.43.12 (192.18.43.12), 30 hops max, 40 byte packets 1 72.20.181.1 0.454 ms 0.452 ms 0.518 ms 2 72.20.191.132 10.312 ms 10.435 ms 10.452 ms 3 72.5.252.77 10.242 ms 10.224 ms 10.324 ms 4 216.52.191.40 11.328 ms 216.52.191.105 11.599 ms 11.676 ms 5 38.104.204.73 26.291 ms 26.195 ms 26.156 ms 6 154.54.6.97 22.448 ms 22.424 ms 22.867 ms 7 154.54.46.217 22.423 ms 154.54.2.230 23.002 ms 154.54.46.217 22.388 ms 8 154.54.82.213 34.333 ms 34.261 ms 34.374 ms 9 154.54.83.34 34.809 ms 34.651 ms 34.513 ms 10 38.122.114.46 29.532 ms 29.206 ms 29.192 ms 11 216.52.40.7 29.120 ms 29.081 ms 29.136 ms 12 * * * 13 * * * 14 * * * $ traceroute -n 192.18.4.206 traceroute to 192.18.4.206 (192.18.4.206), 30 hops max, 40 byte packets 1 72.20.181.1 0.485 ms 0.470 ms 0.520 ms 2 72.20.191.132 10.405 ms 10.461 ms 10.466 ms 3 72.5.252.77 10.297 ms 10.340 ms 10.314 ms 4 216.52.191.40 29.791 ms 216.52.191.105 30.098 ms 29.843 ms 5 38.104.204.73 123.796 ms 123.795 ms 123.797 ms 6 154.54.82.29 22.665 ms 22.773 ms 22.746 ms 7 154.54.46.209 23.023 ms 154.54.80.106 22.189 ms 22.257 ms 8 154.54.82.213 93.193 ms 154.54.82.209 93.199 ms 93.172 ms 9 154.54.45.186 37.295 ms 34.561 ms 154.54.83.34 34.584 ms 10 38.122.114.46 29.169 ms 28.993 ms 29.105 ms 11 216.52.40.7 29.073 ms 28.926 ms 28.843 ms 12 * * * 13 * * * 14 * * * $ dig +norec -t A sun.com @a.gtld-servers.net ; <<>> DiG 9.6.0-APPLE-P2 <<>> +norec -t A sun.com @a.gtld-servers.net ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 48012 ;; flags: qr; QUERY: 1, ANSWER: 0, AUTHORITY: 4, ADDITIONAL: 4 ;; QUESTION SECTION: ;sun.com. IN A ;; AUTHORITY SECTION: sun.com. 172800 IN NS ns8.sun.com. sun.com. 172800 IN NS ns2.sun.com. sun.com. 172800 IN NS ns1.sun.com. sun.com. 172800 IN NS ns3.sun.com. ;; ADDITIONAL SECTION: ns8.sun.com. 172800 IN A 192.18.43.12 ns2.sun.com. 172800 IN A 192.18.99.5 ns1.sun.com. 172800 IN A 192.18.128.11 ns3.sun.com. 172800 IN A 192.18.4.206 $ dig +norec -t SOA sun.com @192.18.43.12 ; <<>> DiG 9.6.0-APPLE-P2 <<>> +norec -t SOA sun.com @192.18.43.12 ;; global options: +cmd ;; connection timed out; no servers could be reached $ dig +norec -t SOA sun.com @192.18.99.5 ; <<>> DiG 9.6.0-APPLE-P2 <<>> +norec -t SOA sun.com @192.18.99.5 ;; global options: +cmd ;; connection timed out; no servers could be reached $ dig +norec -t SOA sun.com @192.18.128.11 ; <<>> DiG 9.6.0-APPLE-P2 <<>> +norec -t SOA sun.com @192.18.128.11 ;; global options: +cmd ;; connection timed out; no servers could be reached $ dig +norec -t SOA sun.com @192.18.4.206 ; <<>> DiG 9.6.0-APPLE-P2 <<>> +norec -t SOA sun.com @192.18.4.206 ;; global options: +cmd ;; connection timed out; no servers could be reached _______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
Looks like 192.18.43.12 (ns8.sun.com) is accessible for me now, but the other three aren't. Frank -----Original Message----- From: outages-bounces@outages.org [mailto:outages-bounces@outages.org] On Behalf Of Frank Bulk Sent: Wednesday, April 11, 2012 1:09 AM To: 'Jimmy Hess'; outages@outages.org Subject: Re: [outages] sun.com name servers unreachable? Same here. One of their four DNS servers, ns1.sun.com (192.18.128.11), doesn't have Cogent in the path (see http://bgptables.merit.edu/assum.php?z=&as=11479#prefixTables), but it makes no difference. None of the traceroutes I perform hit a 192.18.x.x address. Frank -----Original Message----- From: outages-bounces@outages.org [mailto:outages-bounces@outages.org] On Behalf Of Jimmy Hess Sent: Wednesday, April 11, 2012 1:01 AM To: outages@outages.org Subject: Re: [outages] sun.com name servers unreachable? I am seeing this also. No DNS response from any of the 4 DNS server IPs. $ traceroute -n 192.18.43.12 traceroute to 192.18.43.12 (192.18.43.12), 30 hops max, 40 byte packets 1 72.20.181.1 0.454 ms 0.452 ms 0.518 ms 2 72.20.191.132 10.312 ms 10.435 ms 10.452 ms 3 72.5.252.77 10.242 ms 10.224 ms 10.324 ms 4 216.52.191.40 11.328 ms 216.52.191.105 11.599 ms 11.676 ms 5 38.104.204.73 26.291 ms 26.195 ms 26.156 ms 6 154.54.6.97 22.448 ms 22.424 ms 22.867 ms 7 154.54.46.217 22.423 ms 154.54.2.230 23.002 ms 154.54.46.217 22.388 ms 8 154.54.82.213 34.333 ms 34.261 ms 34.374 ms 9 154.54.83.34 34.809 ms 34.651 ms 34.513 ms 10 38.122.114.46 29.532 ms 29.206 ms 29.192 ms 11 216.52.40.7 29.120 ms 29.081 ms 29.136 ms 12 * * * 13 * * * 14 * * * $ traceroute -n 192.18.4.206 traceroute to 192.18.4.206 (192.18.4.206), 30 hops max, 40 byte packets 1 72.20.181.1 0.485 ms 0.470 ms 0.520 ms 2 72.20.191.132 10.405 ms 10.461 ms 10.466 ms 3 72.5.252.77 10.297 ms 10.340 ms 10.314 ms 4 216.52.191.40 29.791 ms 216.52.191.105 30.098 ms 29.843 ms 5 38.104.204.73 123.796 ms 123.795 ms 123.797 ms 6 154.54.82.29 22.665 ms 22.773 ms 22.746 ms 7 154.54.46.209 23.023 ms 154.54.80.106 22.189 ms 22.257 ms 8 154.54.82.213 93.193 ms 154.54.82.209 93.199 ms 93.172 ms 9 154.54.45.186 37.295 ms 34.561 ms 154.54.83.34 34.584 ms 10 38.122.114.46 29.169 ms 28.993 ms 29.105 ms 11 216.52.40.7 29.073 ms 28.926 ms 28.843 ms 12 * * * 13 * * * 14 * * * $ dig +norec -t A sun.com @a.gtld-servers.net ; <<>> DiG 9.6.0-APPLE-P2 <<>> +norec -t A sun.com @a.gtld-servers.net ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 48012 ;; flags: qr; QUERY: 1, ANSWER: 0, AUTHORITY: 4, ADDITIONAL: 4 ;; QUESTION SECTION: ;sun.com. IN A ;; AUTHORITY SECTION: sun.com. 172800 IN NS ns8.sun.com. sun.com. 172800 IN NS ns2.sun.com. sun.com. 172800 IN NS ns1.sun.com. sun.com. 172800 IN NS ns3.sun.com. ;; ADDITIONAL SECTION: ns8.sun.com. 172800 IN A 192.18.43.12 ns2.sun.com. 172800 IN A 192.18.99.5 ns1.sun.com. 172800 IN A 192.18.128.11 ns3.sun.com. 172800 IN A 192.18.4.206 $ dig +norec -t SOA sun.com @192.18.43.12 ; <<>> DiG 9.6.0-APPLE-P2 <<>> +norec -t SOA sun.com @192.18.43.12 ;; global options: +cmd ;; connection timed out; no servers could be reached $ dig +norec -t SOA sun.com @192.18.99.5 ; <<>> DiG 9.6.0-APPLE-P2 <<>> +norec -t SOA sun.com @192.18.99.5 ;; global options: +cmd ;; connection timed out; no servers could be reached $ dig +norec -t SOA sun.com @192.18.128.11 ; <<>> DiG 9.6.0-APPLE-P2 <<>> +norec -t SOA sun.com @192.18.128.11 ;; global options: +cmd ;; connection timed out; no servers could be reached $ dig +norec -t SOA sun.com @192.18.4.206 ; <<>> DiG 9.6.0-APPLE-P2 <<>> +norec -t SOA sun.com @192.18.4.206 ;; global options: +cmd ;; connection timed out; no servers could be reached _______________________________________________ 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
participants (6)
-
Frank Bulk -
Jimmy Hess -
Jon Radel -
Peter Childs -
Scott Howard -
Vinny_Abello＠Dell.com