Oh come on it's impossible ?! Why that domain only ?! Why only on Free's DNS (212.27.40.241). Is anyone else facing this issue ? Anyone using Free facing issues resolving nixos.org or other domain names ?

@Sasha (don't have access to a proper computer, sorry

dig nixos.org

dig +cd nixos.org

And post the results. (+cd = checking disabled, to see if this is a DNSSEC problem)

@bortzmeyer I had done a simple `dig nixos.org` (I don't know what +cd does) but I got the same result with `+cd` :

; <<>> DiG 9.11.2 <<>> nixos.org
;; global options: +cmd
;; connection timed out; no servers could be reached

A result I interpret as the DNS process on their server crashing and thus maybe closing the socket unexpectedly ? Because I can garantee the server can be reached : I can resolve any other domain name without any trouble at all.

@Sasha @bortzmeyer looks like your local nameserver has trouble, what's in /etc/resolv.conf (or whatever equivalent of it you might have).

I have a crappy router that tends to fill up its DNS cache and stop resolving new names, it answers to the old (known) ones only.

@saper @bortzmeyer Yeah it contains my provider's DNS servers (212.27.40.24{0,1}), which can apparently resolve any other domain name like a charm, and conversely I've been able to resolve nixos.org by asking directly other DNS (yeah, I did it with @8.8.8.8 ^^) and also on a VPS I rent. So yeah, I would suppose my provider's servers have gone nut, but I'm very surprised I should be the only one to notice something. Plus I thought that'd be the kind of bug they would fix within minutes.

@Sasha @saper RIPE stat show that at least one Udag prefix is poorly visible (70 % only) https://stat.ripe.net/185.61.8.10#tabId=routing

@bortzmeyer @Sasha does free have a looking glass?

@saper @Sasha But you have me :-) to perform traceroutes (or dozens of RIPE Atlas probes) : routing loop inside Free https://gist.github.com/bortzmeyer/5e23d3f7cffd92d366a7d750fcbacae4