Salut,
Starting from this morning at 05:20, all name resolutions over the ORSN appear to fail. dnstracer output:
Tracing to (whatever) via 127.0.0.1, timeout 15 seconds 127.0.0.1 (127.0.0.1) |___ E.ORSN-SERVERS.NET [.] (213.161.0.90) * * * |___ J.ORSN-SERVERS.NET [.] (193.93.167.222) |___ H.ORSN-SERVERS.NET [.] (213.144.148.130) |___ B.ORSN-SERVERS.NET [.] (2a02:0060:ffff:0001:0000:0000:0000:0002) |___ B.ORSN-SERVERS.NET [.] (193.238.157.110) |___ K.ORSN-SERVERS.NET [.] (2001:4b88:9000:0000:0000:0000:0000:0000) |___ K.ORSN-SERVERS.NET [.] (217.173.157.225) |___ F.ORSN-SERVERS.NET [.] (91.143.115.242) |___ I.ORSN-SERVERS.NET [.] (194.242.225.162) |___ D.ORSN-SERVERS.NET [.] (2001:08a8:0021:0002:0000:0000:0000:0066) * * * |___ D.ORSN-SERVERS.NET [.] (195.226.7.66) |___ M.ORSN-SERVERS.NET [.] (213.145.82.34) |___ G.ORSN-SERVERS.NET [.] (82.102.0.9) * * * |___ C.ORSN-SERVERS.NET [.] (212.7.160.13) |___ A.ORSN-SERVERS.NET [.] (217.146.128.77) * * * |___ A.ORSN-SERVERS.NET [.] (2001:08d0:0000:0003:0000:0000:0000:0100) * * * ___ L.ORSN-SERVERS.NET [.] (192.83.249.100)
Everything broken? How can this be with such a redundant network? I also thought maybe I should just download a new root hints file, but evidently orsn.net is also down, even when using the root-servers.net hints.
Tonnerre
Hi,
Everything broken? How can this be with such a redundant network? I also thought maybe I should just download a new root hints file, but evidently orsn.net is also down, even when using the root-servers.net hints.
I can confirm that name resolutions via orsn-servers.net fails.
Long TTLs should prevent from users noticing outages. Thankfully our BINDs have a few top-level- orsn-servers in their cache.
However in a few days or in case of a bind restart, I guess we will run unto troubles too...
Regards
Jean-Pierre
On Fri, 20 Jun 2008 09:24:27 +0200 Tonnerre Lombard tonnerre@bsdprojects.net wrote:
Hi,
Starting from this morning at 05:20, all name resolutions over the ORSN appear to fail. dnstracer output:
the master dns-server seems to be down, so all other name servers are unable to refresh the zone-files.
I could touche (refresh) the zone files on the D.ORSN-SERVER but this is not the solution.
to be honest, the ORSN project is slowly dying - except there is a person who'll take care about.
Ueli
Tracing to (whatever) via 127.0.0.1, timeout 15 seconds 127.0.0.1 (127.0.0.1) |___ E.ORSN-SERVERS.NET [.] (213.161.0.90) * * * |___ J.ORSN-SERVERS.NET [.] (193.93.167.222) |___ H.ORSN-SERVERS.NET [.] (213.144.148.130) |___ B.ORSN-SERVERS.NET [.] (2a02:0060:ffff:0001:0000:0000:0000:0002) |___ B.ORSN-SERVERS.NET [.] (193.238.157.110) |___ K.ORSN-SERVERS.NET [.] (2001:4b88:9000:0000:0000:0000:0000:0000) |___ K.ORSN-SERVERS.NET [.] (217.173.157.225) |___ F.ORSN-SERVERS.NET [.] (91.143.115.242) |___ I.ORSN-SERVERS.NET [.] (194.242.225.162) |___ D.ORSN-SERVERS.NET [.] (2001:08a8:0021:0002:0000:0000:0000:0066) * * * |___ D.ORSN-SERVERS.NET [.] (195.226.7.66) |___ M.ORSN-SERVERS.NET [.] (213.145.82.34) |___ G.ORSN-SERVERS.NET [.] (82.102.0.9) * * * |___ C.ORSN-SERVERS.NET [.] (212.7.160.13) |___ A.ORSN-SERVERS.NET [.] (217.146.128.77) * * * |___ A.ORSN-SERVERS.NET [.] (2001:08d0:0000:0003:0000:0000:0000:0100) * * * ___ L.ORSN-SERVERS.NET [.] (192.83.249.100)
Everything broken? How can this be with such a redundant network? I also thought maybe I should just download a new root hints file, but evidently orsn.net is also down, even when using the root-servers.net hints.
Tonnerre
Salut, ueli,
On Fri, 20 Jun 2008 13:31:39 +0200, ueli heuer wrote:
to be honest, the ORSN project is slowly dying - except there is a person who'll take care about.
The question is what is involved with that. I am under the impression that there is enough interest in the project itself, but someone - or optimally a team of people - would need to be worked in.
Tonnerre
-
Jean-Pierre Schwickerath -
Tonnerre Lombard -
ueli heuer