I can't get http://www.kmeleon.org to resolve from a number of locations but http://kmeleon.org does. It seems that this problem crops up a couple times a year...

kmeleon.org has 2 main name servers NS.RONOGRAPHY.COM (1) and NS.PLANET-D.NET (2)

here are my records pulled from these servers.


----server (1)------

> ]http://www.kmeleon.org
Server: NS.RONOGRAPHY.COM
Address: 216.36.77.61

Non-authoritative answer:
Name: usw-pr-vhost.sourceforge.net
Address: 216.136.171.204
Aliases: ]http://www.kmeleon.org, vhost.sourceforge.net

> kmeleon.org
Server: NS.RONOGRAPHY.COM
Address: 216.36.77.61

Name: kmeleon.org
Address: 216.136.171.204



---and server (2)-----------

> ]http://www.kmeleon.org
Server: NS.PLANET-D.NET
Address: 193.109.142.19

Name: ]http://www.kmeleon.org
Address: 64.236.8.138

> kmeleon.org
Server: NS.PLANET-D.NET
Address: 193.109.142.19

Name: kmeleon.org
Address: 64.236.8.138


I am on windows currently so I don't have dig or anything else to pull better information, but a few things to point out. on the primary server (1) it points to the same IP address but it's a vhost on sourceforge's server and it also has to be configured on the server in order to work. The reason I got a non auth answer for www. is because ot points to sourceforge as the soa, and the ns.ron* (1) server is just holding a cached answer from ns1.valinux.com and serving it.

The next server NS.PLANET-D.NET is just holding the wrong record, the A record for the web site. 64.236.8.138 is not even a live IP. They should fix the record on that server or just remove the authoritave record from the box and let it cache an answer form ns1.valinux.com like the other server.

The whois database entry still has the old IP address for NS.RONOGRAPHY.COM as well, I think the DNS records could use some updating.