pouët.net

(just emailed to the relevant people, but because I don't particularly trust email at this point I'm trying the scattergun hope-somebody-important-sees-this approach...)

scene.org's DNS setup seems to be a bit broken, and it's causing pouet.net to be intermittently dead. (for me, anyway, and kb's comment on the oneliner makes me suspect I'm not alone here)

As far as I can tell, this is what's going on:

pouet.net's nameservers are ns1.scene.org and ns2.scene.org.
scene.org's nameservers are ns1.hro.nl and ns2.hro.nl.

If you ask scene.org's nameservers about ns1.scene.org and ns2.scene.org, you get two different answers:
ns1.hro.nl says:
ns1.scene.org = 145.24.129.1 (= ns1.hro.nl)
ns2.scene.org = 145.24.129.2 (= ns2.hro.nl)

ns2.hro.nl says:
ns1.scene.org = 145.24.145.100 (= the www.scene.org server)
ns2.scene.org = 193.109.122.62 (= bfib.colo.bit.nl)

I don't know which is the intended result, but ns2.hro.nl's answer seems to be the better one, because 145.24.129.1/145.24.129.2 don't give authoritative answers for www.pouet.net.

So, it looks like somebody ought to either:
a) fix ns1.hro.nl so it gives the same answer as ns2.hro.nl for ns1.scene.org/ns2.scene.org, or
b) add pouet's DNS record to ns1.hro.nl/ns2.hro.nl, then fix ns2.hro.nl so that it gives the same answer as ns1.hro.nl

We (Scene.org) recently did some nameserver/domain renewal magic, but this should be fixed now. :) I'm sure the tech-guys can talk more about what happened.

*.nl

There's your problem...

Weed-smoking wankers fixing (no pun intended) important DNS issues from Coffee shops.

;)

Same problem here. :/

dutch naming scheme FTW

If people are having problems still, please use www.pouet.scene.org (should work despite messed up nameserver entries).

here it works now.