re: DNS issues (Page 2/3)
theogre DEC 12, 12:04 PM
Even at https://www.cogentco.com/en/looking-glass shows similar or same depending on Route Location...
IPv4 Trace for US-Philly to 217.148.167.147
code:
traceroute to 217.148.167.147 (217.148.167.147), 30 hops max, 60 byte packets
 1  gi0-5-0-10.3.rcr21.phl01.atlas.cogentco.com (66.250.250.105)  0.622 ms  0.664 ms
 2  be2364.ccr41.jfk02.atlas.cogentco.com (154.54.3.141)  2.813 ms  2.820 ms
 3  be2317.ccr41.lon13.atlas.cogentco.com (154.54.30.186)  70.917 ms  70.862 ms
 4  be12194.ccr41.ams03.atlas.cogentco.com (154.54.56.94)  76.039 ms  77.701 ms
 5  be3457.ccr21.ams04.atlas.cogentco.com (130.117.1.10)  78.328 ms  76.255 ms
 6  be2514.rcr01.b015515-0.ams04.atlas.cogentco.com (130.117.0.130)  78.286 ms  76.728 ms
 7  149.11.39.250 (149.11.39.250)  77.493 ms  77.500 ms
 8  cr01nh-as01cpl.wd6.net (92.48.253.42)  78.935 ms  77.614 ms
 9  as01cpl-as03cpl.wd6.net (84.244.189.118)  80.085 ms  80.094 ms
10  www.fiero.nl (217.148.167.147)  79.055 ms  78.976 ms

Note that This trace skips all hops from you and your local ISP to their fist hop listed.

[This message has been edited by theogre (edited 12-12-2021).]

williegoat DEC 12, 12:07 PM
For me, it either fails to resolve, or goes through in eleven hops. Actually 9-10 hops with a timeout or two as it tries to cross the Atlantic.

[This message has been edited by williegoat (edited 12-12-2021).]

Raydar DEC 12, 12:11 PM
I've had the occasional problem, posting messages/responses, but nothing spectacular about loading pages.

Edit - And this message posted with no issues.

[This message has been edited by Raydar (edited 12-12-2021).]

Jake_Dragon DEC 12, 12:12 PM
Its not just Fiero.nl I noticed that several sites are having DNS issue over the last couple of days.
Its worse depending on where the host is.

I was blaming Spectrum but perhaps its something else.
rinselberg DEC 12, 01:26 PM
theogre DEC 12, 01:38 PM

quote
Originally posted by Jake_Dragon:
Its not just Fiero.nl I noticed that several sites are having DNS issue over the last couple of days.
Its worse depending on where the host is.

I was blaming Spectrum but perhaps its something else.

Doesn't matter what local ISP is if all use Cogent Undersea Cables to reach Fiero.nl

Can see DNS fail or Connect Timeout depending on ISP and local OS.
Change DNS to any others like Cloudflare 1.1.1.1 may stop DNS fail and still timeout connecting to Europe sites.
Note that a Browser "Error" can say DNS fail but mean just can't connect to X.

Also All Local OS have DNS Caches that should resolve Recent Names First. Depending on settings, often will not bother DNS servers unless Cache Time to Live has ended.
Unless you have DNS over HTTPS like FF and some others browsers use to hide DNS from ISP etc. Then the cache if any is in the browser.

Cogent router names that shows about where a problem is... 3rd section of name is "City"/location
above traces first problem is at or in between JFK (as is JFK Airport area in NY) and London...
Example:
code:
My Trace
 13    21 ms    18 ms    17 ms  be2807.ccr42.jfk02.atlas.cogentco.com [154.54.40.109]
 14    86 ms    88 ms    88 ms  be2490.ccr42.lon13.atlas.cogentco.com [154.54.42.86]

Looking Glass Trace
 2  be2364.ccr41.jfk02.atlas.cogentco.com (154.54.3.141)  2.813 ms  2.820 ms
 3  be2317.ccr41.lon13.atlas.cogentco.com (154.54.30.186)  70.917 ms  70.862 ms

Amsterdam routers doesn't look happy either. 1st of 2 "ams" names maybe really in Cambridge for Undersea cable link.
(See https://www.cogentco.com/fi..._networkmap_page.jpg but that likely doesn't show all links for various reasons.)
williegoat DEC 12, 02:08 PM
I'm pretty sure mine crosses the Atlantic on CenturyLink (Lumen) cables. Cogent isn't involved, as far as I can tell.
Cliff Pennock DEC 12, 04:12 PM
It's a DNS issue which is unfortunately out of my control. Hopefully they will solve it soon.
CoolBlue87GT DEC 13, 09:55 AM
Is there any company or group that should be contacted to notify them of the problem ? Or do they know already ?

This is the only site that I'm unable to connect to every try, it took over 10 minutes of trying to connect today.
theogre DEC 13, 10:40 AM

quote
Originally posted by Cliff Pennock:
It's a DNS issue which is unfortunately out of my control. Hopefully they will solve it soon.

Even "going direct" w/ IP # is slow or no connect to your server(s).

IOW For browser, I get "can't find" or "can't connect" errors at random times trying to get PFF Page. Or PFF page may load but not pip/button pics.
And use several DNS servers and IP # direct or in Host all w/ same results.

Cogent and maybe more have issues on US to EU cable(s) still today.

Any w/ slow connecting should run tracert to see if pings are high at some hops like examples above.
High > 90 ms pushes many things to see connecting w/ many lost packets and slows down even more to resend, often several times, the lost data.
Example Default setting of Ping and Tracert programs will often timeout a attempt a little above 100ms. To add time to them have to add command switches. (ping -v & -w, tracert -w, all w/ values before name/IP#.)

If one browser has problems dealing w/ slow connecting, try another or add a new profile w/ default setting and no plugins.