Andre Carregal wrote:
On Mon, Feb 8, 2010 at 5:12 PM, Stuart P. Bentley <[email protected]> wrote:
It appears to just be a DNS issue, as
http://downforeveryoneorjustme.com/keplerproject.org says it's up, but
http://www.opendns.com/support/cache/ is getting DID NOT RESOLVE from all
sources.
Not sure what happened by then, but both links are reporting OK now.
Is the Kepler site up for you too?
Thanks
André
This DNS diagnostic reports that the domain is not configured properly:
http://www.intodns.com/keplerproject.org
----------
Nameserver records returned by the parent servers are:
ns1.luaforge.net. ['147.65.1.201'] (NO GLUE) [TTL=86400]
luaforge1.luaforge.net. ['147.65.1.201'] (NO GLUE) [TTL=86400]
luaforge3.luaforge.net. ['147.65.1.201'] (NO GLUE) [TTL=86400]
a0.org.afilias-nst.info was kind enough to give us that information.
----------
NS records got from your nameservers listed at the parent NS are:
ns1.luaforge.net ['147.65.1.201'] [TTL=3600]
----------
ERROR: One or more of the nameservers listed at the parent servers are
not listed as NS records at your nameservers. The problem NS records are:
luaforge1.luaforge.net
luaforge3.luaforge.net
This is listed as an ERROR because there are some cases where nasty
problems can occur (if the TTLs vary from the NS records at the root
servers and the NS records point to your own domain, for example).
----------
Also the SOA record is not reporting the correct primary nameserver:
Primary nameserver: luaforge.net
Hostmaster E-mail address: hostmaster.luaforge.net
Serial #: 2008052201
Refresh: 10800
Retry: 120
Expire: 604800 1 weeks
Default TTL: 3600
This can cause all sorts of strange DNS problems when it does not match
the NS records returned by the parent servers.
_______________________________________________
Kepler-Project mailing list
[email protected]
http://lists.luaforge.net/cgi-bin/mailman/listinfo/kepler-project
http://www.keplerproject.org/
