On Sat, 13 Mar 2004 12:15:48 +0100 Robert Epprecht <epprecht@xxxxxxxxx> wrote: > Anahata <anahata@xxxxxxxxxxxxxx> writes: >> >> FYI - the way to find out what's going on when a domain doesn't work >> is: first >> whois ardour.org > > This does not work from here: > whois ardour.org > No match for "ARDOUR.ORG". > >>> Last update of whois database: Fri, 12 Mar 2004 19:13:19 EST <<< > >> That will tell you the nameservers for the domain. >> (in this case ns1.deramhost.com, ns2..., ns3...) >> You should be able to get the IP addres from them: >> host ardour.org ns1.dreamhost.com > > this works: > host ardour.org ns1.dreamhost.com > ardour.org A 66.33.221.124 So that means it can't resolve the name when using your default nameserver, but can when using others. >> If either of those steps doesn't work the domain is broken (fsvo >> "broken"). This can happen temporarily if the domain gets moved from >> one registrar or primary nameserver to another. > > 'temporarily' yes, but for days and weeks? And it should work after > some time, shouldn't it? Or should I contact people from my DNS or > ardour.org. And then I do not think that my emails reach ardour.org, > anyway... If some nameservers work, then the problem isn't with ardour.org, but with the nameservers that *don't* work. If you've had this problem for a long time, then you should tell your ISP that the nameservice they're providing you isn't functioning properly. -c -- Chris Metzler cmetzler@xxxxxxxxxxxxxxxxxxxxx (remove "snip-me." to email) "As a child I understood how to give; I have forgotten this grace since I have become civilized." - Chief Luther Standing Bear -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available Url : http://music.columbia.edu/pipermail/linux-audio-user/attachments/20040314/10322f2b/attachment.bin
