mi dominio caido, ¿porke?

[pereztroff]

intento entrar en uno de mi dominios alojados en aruba y sale un error "no se puede encontrar el servidor"...
¿HAY alguna aplicacion o web que analice los posibles motivos?
me gustaria saber de porque da ese error antes de reclamar a dicha empresa.....
¿es normal que se caiga un servidor?

[pereztroff]

estuve echando un vistazo a dnsstuff y entre toda la informacion que me daba sobre mi dominio salio lo siguiente:
Looking up at dns2.technorail.com.... Reports 6 A record(s). 174ms.
Looking up at dns.technorail.com.... Reports 6 A record(s). 172ms.


Average of all 2 nameservers: 173ms (plus 184ms overhead).

Score: B-

Took off 2 points since dns2.technorail.com allows recursive lookups (if lots of people are using the server, it can slow down).
Took off 2 points since dns.technorail.com allows recursive lookups (if lots of people are using the server, it can slow down).
Took off 15 points for >160ms average response time.

Note: The 184ms overhead is the time it takes to get your NS records from the parent servers, and indicates a worst-case scenario (normally, the resolving DNS server would have the common parent server entries cached, and would know the parent server(s) that were responding most quickly). The best times since the last time this web server was last restarted are: 21ms average response, plus 111ms overhead. Note that these times are from a server located in the United States; if most of the people using your DNS are outside of the United States, your actual results may be better than what is shown here.

¿¿que significa todo esto?

[pechergu]

dnsstuff te indica el estado de los dns, y si los registros que estos poseen de tu dominio, nada mas. Por lo que pusiste esto todo ok en ese aspecto, es normal.

[pereztroff]

este mensaje , ¿que significa? es grave????

FAIL Reverse DNS entries for MX records ERROR: One or more of your mail server(s) have no reverse DNS (PTR) entries (if you see "Timeout" below, it may mean that your DNS servers did not respond fast enough). RFC1912 2.1 says you should have a reverse DNS for all your mail servers. It is strongly urged that you have them, as many mailservers will not accept mail from mailservers with no reverse DNS entry. This may be a false positive due to the nasty BIND bug (client side) that causes reverse DNS entries to fail the first time (if you ever see long delays in reverse DNS lookups, that's because of this bug). You can double-check using the 'Reverse DNS Lookup' tool at the DNSstuff site. The problem MX records are:
166.128.149.62.in-addr.arpa [No reverse DNS entry (rcode: 3 ancount: 0)]

[andres-rf]

Puede ser que se haya caido el proveedor de acceso a internet de aruba o que el servidor en el que esta tu web haya dejado de funcionar y lo esten intentando arreglar.

[pechergu]

eso no quiere decir que el servidor este caido, sino solo que no posee 'reverse dns'. En la practica no significa nada, es algo muy técnico.