[Learning to pay attention to my to: lines] This cleared up from here about 5 minutes ago. Both of the previously unreachable worldnic IPs are now reachable for me.
-Rusty On Wed, Mar 17, 2021 at 11:25 AM Rusty Dekema <rdek...@gmail.com> wrote: > > I am having similar problems from AS 7922 near Detroit. I am unable to > reach ns61.worldnic.com/207.204.40.131 as well as > ns75.worldnic.com/207.204.40.138. > > Tracing route to ns75.worldnic.com [207.204.40.138] > over a maximum of 30 hops: > > 7 19 ms 18 ms 19 ms > be-2403-pe03.350ecermak.il.ibone.comcast.net [96.110.37.30] > 8 19 ms 18 ms 23 ms 173.167.56.42 > 9 21 ms 20 ms 19 ms 108.162.217.23 > 10 21 ms 20 ms 19 ms 108.162.217.140 > 11 * * * Request timed out. > > Cheers, > Rusty > > > > On Wed, Mar 17, 2021 at 11:06 AM mike tancsa via Outages > <outages@outages.org> wrote: > > > > I noticed a couple of domains that have netsol as authoritative timing > > out, specifically ns61.worldnic.COM resolving to 207.204.40.131 which I > > pick it up via Cloudflare in Toronto Canada via our Torix peer > > > > % traceroute -I -q1 -n 207.204.40.131 > > traceroute to 207.204.40.131 (207.204.40.131), 64 hops max, 48 byte packets > > 1 199.212.134.10 0.139 ms > > 2 205.211.165.118 4.263 ms > > 3 206.108.34.208 31.456 ms > > 4 108.162.240.24 4.331 ms > > 5 108.162.240.14 4.404 ms > > 6 * > > > > > > e.g > > > > % time host -tns washconnect.com > > washconnect.com name server ns62.worldnic.com. > > washconnect.com name server ns61.worldnic.com. > > > > % time host host1.washconnect.com ns62.worldnic.com. > > Using domain server: > > Name: ns62.worldnic.com. > > Address: 207.204.21.131#53 > > Aliases: > > > > host1.washconnect.com has address 204.186.31.41 > > 0.000u 0.002s 0:00.10 0.0% 0+0k 3+0io 0pf+0w > > > > % time host host1.washconnect.com ns61.worldnic.com. > > ;; connection timed out; no servers could be reached > > 0.000u 0.002s 0:10.05 0.0% 0+0k 3+0io 0pf+0w > > > > I am having problems with their whois server as well > > > > > > % time whois -h whois.networksolutions.com washconnect.com > > whois: connect(): Operation timed out > > 0.000u 0.001s 1:15.18 0.0% 0+0k 1+0io 0pf+0w > > > > route-views.routeviews.org doesnt see their prefix either :( > > > > route-views>sh ip bgp 64.69.216.61 > > BGP routing table entry for 0.0.0.0/0, version 33108733 > > Paths: (1 available, best #1, table default, RIB-failure(17)) > > Not advertised to any peer > > Refresh Epoch 1 > > 53767 3257 > > 162.251.163.2 from 162.251.163.2 (162.251.162.3) > > Origin IGP, localpref 100, valid, external, best > > Community: 53767:5000 > > path 7FE0F6ED4BE8 RPKI State not found > > rx pathid: 0, tx pathid: 0x0 > > route-views> > > > > > > % host whois.networksolutions.com > > whois.networksolutions.com has address 64.69.216.61 > > whois.networksolutions.com has IPv6 address 2607:f408:1010:a:64:69:216:61 > > > > % whois -h 2607:f408:1010:a:64:69:216:61 washconnect.com > > whois: connect(): Operation timed out > > > > > > > > > > > > > > _______________________________________________ > > 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