mu.nu - We're sorry we accidentally destroyed your panties.
April 21, 2006
DNS Setup
ns.liquidweb.com I don't know why - I set it up over 2 years ago and haven't touched it since. In any case, I changed it to ns.mu.nu
ns2.mu.nu and it's now been 24 hours and it's still not working. Is this right? Is there something that I have to do at the mu.nu end? Anyone know what's going on/how I can fix it?
My domain (rishon-rishon.com) suddenly stopped working. I checked the DNS in its registration, and for some reason it was
mica.mu.nuns.liquidweb.com I don't know why - I set it up over 2 years ago and haven't touched it since. In any case, I changed it to ns.mu.nu
ns2.mu.nu and it's now been 24 hours and it's still not working. Is this right? Is there something that I have to do at the mu.nu end? Anyone know what's going on/how I can fix it?
Posted by: David Boxenhorn at 06:21 AM | Comments (16) | Add Comment | Trackbacks (Suck)
1
That's exactly right, and I just tried it and it's working for me.
A very useful utility is the Squishywishywoo DNS checker at squish.net. It reports that rishon-rishon.com is set up just fine. It should certainly be working after 24 hours, and it's working for me, and it's set up correctly, so I'm a bit confuzzled.
A very useful utility is the Squishywishywoo DNS checker at squish.net. It reports that rishon-rishon.com is set up just fine. It should certainly be working after 24 hours, and it's working for me, and it's set up correctly, so I'm a bit confuzzled.
Posted by: Pixy Misa @ at April 21, 2006 11:34 PM
2
Thanks, Pixy. It is working fine for me now. Guess it just took some time. But where did those old DNS values come from?
Posted by: David Boxenhorn @ at April 22, 2006 05:06 PM
3
Could this be a problem? Here are the results I got at the Squish link:
Results
16.7% of queries will end in failure at 69.72.215.218 (ns1.mu.nu) - failed to resolve ns.mu.nu due to 69.72.215.218 - query timed out
16.7% of queries will end in failure at 69.72.215.226 (ns2.mu.nu) - failed to resolve ns.mu.nu due to 69.72.215.226 - query timed out
50.0% of queries will end in failure at 69.72.215.226 (ns2.mu.nu) - query timed out
16.7% of queries will be returned by 69.72.215.218 (ns.mu.nu)
rishon-rishon.com. 14400 IN A 69.72.215.227
Results
16.7% of queries will end in failure at 69.72.215.218 (ns1.mu.nu) - failed to resolve ns.mu.nu due to 69.72.215.218 - query timed out
16.7% of queries will end in failure at 69.72.215.226 (ns2.mu.nu) - failed to resolve ns.mu.nu due to 69.72.215.226 - query timed out
50.0% of queries will end in failure at 69.72.215.226 (ns2.mu.nu) - query timed out
16.7% of queries will be returned by 69.72.215.218 (ns.mu.nu)
rishon-rishon.com. 14400 IN A 69.72.215.227
Posted by: David Boxenhorn @ at April 22, 2006 05:11 PM
4
I'd run into this problem a while back. It seems some ISP's Domain Name Servers don't see / recognize / point to the right place for the mu.nu domain.
I ended up using the DNS Server from a secondary ISP at work to access mu.nu sites.
There's an ISP in the northern US that was having problems for a while, but I haven't heard anything about it lately.
I ended up using the DNS Server from a secondary ISP at work to access mu.nu sites.
There's an ISP in the northern US that was having problems for a while, but I haven't heard anything about it lately.
Posted by: phin @ at April 25, 2006 01:01 PM
5
I like the cheap christian heels, I just guess nobody dont!
Posted by: Wholesale blog @ at May 18, 2011 10:16 AM
Processing 0.0, elapsed 0.0112 seconds.
22 queries taking 0.0081 seconds, 27 records returned.
Page size 8 kb.
Powered by Minx 0.8 beta.