3 ms·

Here is one glitch that seems to be related that still is not fixed: https://www.indilib.org/forum/general/14691-indilib-org-site-outage.html?start=0 https://w

Here is one glitch that seems to be related that still is not fixed: https://www.indilib.org/forum/general/14691-indilib-org-site-outage.html?start=0 https://www.indilib.org/forum/general/14691-indilib-org-site... The glitch began on the 18th and is now in the situation where some users can and others cannot access the site. I, myself, cannot access the site six days later, when connected via my network wifi router (ISP is Cox Communications), but can, if instead I connect to the Hotspot on my IPhone(AT&T). Traceroutes fail in either case, continually, at the server 198.207.200.70 (which does not appear to be owned by cogent). What, if anything, can an end-user such as myself do in such a situation. Where can such an end-user send a report that might lead to a fix? I assume the owners of the indilib.org site are trying whatever they can, but I have no idea what their reporting chain might be.

bewaretheirs 2y ago
What's your evidence that this is related to c.root-servers.net serving a stale version of the root zone? If you can get the correct IP address for a site out of the DNS but can't reach the site, it's not a DNS problem, and not a problem with the root DNS servers. This is likely correlated only in time with the c.root-servers.net issue. That said, your difficulty reaching indilib.org may be related to the Cogent-TATA peering dispute or one of Cogent's other peering disputes - from where I sit, a traceroute to indilib.org goes through cogent's network. But that's not what this submission is about.