Re: [outages] NetSol issues via Cloudflare in Toronto (ns61.worldnic.com) ?
[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 <rdekema@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
SRSPlus.com(also owned by web.com) was down at the same time. I saw it back up at 15:30 GMT. I am in the Chicago area and checked from my virtual server at IONOS and saw the same DNS outage. Lyle Giese On 3/17/21 10:42 AM, Rusty Dekema via Outages wrote:
[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 <rdekema@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
It seems I spoke too soon. Reachability to those IP addresses is now intermittent here as well as from Comcast's NY route server. However, Comcast seems to still be seeing a route to the /24 even when the IPs aren't pingable: RP/0/RSP0/CPU0:route-server.newyork.ny.ibone#show ip bgp 64.69.216.61 Wed Mar 17 15:57:59.012 utc BGP routing table entry for 64.69.216.0/24 Versions: Process bRIB/RIB SendTblVer Speaker 0 0 Last Modified: Mar 17 15:32:26.630 for 00:25:32 Paths: (1 available, no best path) Not advertised to any peer Path #1: Received by speaker 0 Not advertised to any peer 1299 19871, (received & used) 96.109.22.227 (inaccessible) from 68.86.80.3 (96.109.22.227) Origin IGP, metric 0, localpref 250, valid, internal Received Path ID 0, Local Path ID 0, version 0 Community: 7922:403 7922:3000 Originator: 96.109.22.227, Cluster list: 68.86.1.3, 96.109.22.30 -Rusty On Wed, Mar 17, 2021 at 11:42 AM Rusty Dekema <rdekema@gmail.com> wrote:
[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 <rdekema@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
participants (2)
-
Lyle Giese -
Rusty Dekema