Foros del Web » Administración de webs » Dominios »

Problemas con DNS

Estas en el tema de Problemas con DNS en el foro de Dominios en Foros del Web. Hola Amigos Tengo comprado en godaddy el dominio: www.skill4reservations.com y el hosting del mismo lo estoy haciendo en un servidor propio Windows 2003 Server con ...
  #1 (permalink)  
Antiguo 19/04/2010, 16:34
 
Fecha de Ingreso: abril-2010
Mensajes: 1
Antigüedad: 4 años, 7 meses
Puntos: 0
Busqueda Problemas con DNS

Hola Amigos

Tengo comprado en godaddy el dominio: www.skill4reservations.com y el hosting del mismo lo estoy haciendo en un servidor propio Windows 2003 Server con IIS en la IP:190.241.34.116.
Ya realize toda la configuracion necesaria en el panel de control de goddady para que resuelva correctamente el nombre:
www.skill4reservations.com

El problema que me sucede es que algunas personas si les resuelve bien el nombre y pueden entrar sin ningún problema al web, pero otras personas no pueden acceder en nada, incluso ni logran hacer ping, que lo tengo habilitado en estos momentos. Hice el test de DNS en el web:
http://www.intodns.com
y me devuelve algunos errores, se los pongo al final del mensaje, yo no soy experto en este tema de DNS por lo que les pido ayuda a los que sepan.
Aqui va le test:

Category Status Test name Information send feedback
Parent Domain NS records Nameserver records returned by the parent servers are:

online.skill4reservations.com. ['190.241.34.116'] [TTL=172800]
reservas.skill4reservations.com. ['190.241.34.116'] [TTL=172800]
www.skill4reservations.com. ['190.241.34.116'] [TTL=172800]

k.gtld-servers.net was kind enough to give us that information.
TLD Parent Check Good. k.gtld-servers.net, the parent server I interogated, has information for your TLD. This is a good thing as there are some other domain extensions like "co.us" for example that are missing a direct check.
Your nameservers are listed Good. The parent server k.gtld-servers.net has your nameservers listed. This is a must if you want to be found as anyone that does not know your DNS servers will first ask the parent nameservers.
DNS Parent sent Glue Good. The parent nameserver sent GLUE, meaning he sent your nameservers as well as the IPs of your nameservers. Glue records are A records that are associated with NS records to provide "bootstrapping" information to the nameserver.(see RFC 1912 section 2.3)
Nameservers A records Good. Every nameserver listed has A records. This is a must if you want to be found.
NS NS records from your nameservers NS records got from your nameservers listed at the parent NS are:
Oups! I could not get any nameservers from your nameservers (the ones listed at the parent server). Please verify that they are not lame nameservers and are configured properly.


Recursive Queries Good. Your nameservers (the ones reported by the parent server) do not report that they allow recursive queries for anyone.
Same Glue Hmm,I do not consider this to be an error yet, since I did not detect any nameservers at your nameservers.
Glue for NS records OK. Your nameservers (the ones reported by the parent server) have no ideea who your nameservers are so this will be a pass since you already have a lot of errors!
Mismatched NS records WARNING: One or more of your nameservers did not return any of your NS records.
DNS servers responded ERROR: One or more of your nameservers did not respond:
The ones that did not responded are:
190.241.34.116
Name of nameservers are valid OK. The nameservers reported by the parent send out nothing as shown above. I can't check nothing so it's a green!
Multiple Nameservers ERROR: Looks like you have less than 2 nameservers. According to RFC2182 section 5 you must have at least 3 nameservers, and no more than 7. Having 2 nameservers is also ok by me.
Nameservers are lame OK. All the nameservers listed at the parent servers answer authoritatively for your domain.
Missing nameservers reported by parent OK. All NS records are the same at the parent and at your nameservers.
Missing nameservers reported by your nameservers You should already know that your NS records at your nameservers are missing, so here it is again:

online.skill4reservations.com.
reservas.skill4reservations.com.
www.skill4reservations.com.


Domain CNAMEs OK. RFC1912 2.4 and RFC2181 10.3 state that there should be no CNAMEs if an NS (or any other) record is present.
NSs CNAME check OK. RFC1912 2.4 and RFC2181 10.3 state that there should be no CNAMEs if an NS (or any other) record is present.
Different subnets OK. Looks like you have nameservers on different subnets!
IPs of nameservers are public Ok. Looks like the IP addresses of your nameservers are public. This is a good thing because it will prevent DNS delays and other problems like
DNS servers allow TCP connection OK. Seems all your DNS servers allow TCP connections. This is a good thing and usefull even if UDP connections are used by default.
Different autonomous systems OK. It seems you are safe from a single point of failure. You must be carefull about this and try to have nameservers on different locations as it can prevent a lot of problems if one nameserver goes down.
Stealth NS records sent Ok. No stealth ns records are sent
SOA SOA record No valid SOA record came back!

MX MX Records Oh well, I did not detect any MX records so you probably don't have any and if you know you should have then they may be missing at your nameservers!

WWW WWW A Record ERROR: I could not get any A records for www.skill4reservations.com!


Category Status Test name Information send feedback
Parent Domain NS records Nameserver records returned by the parent servers are:

online.skill4reservations.com. ['190.241.34.116'] [TTL=172800]
reservas.skill4reservations.com. ['190.241.34.116'] [TTL=172800]
www.skill4reservations.com. ['190.241.34.116'] [TTL=172800]

k.gtld-servers.net was kind enough to give us that information.
TLD Parent Check Good. k.gtld-servers.net, the parent server I interogated, has information for your TLD. This is a good thing as there are some other domain extensions like "co.us" for example that are missing a direct check.
Your nameservers are listed Good. The parent server k.gtld-servers.net has your nameservers listed. This is a must if you want to be found as anyone that does not know your DNS servers will first ask the parent nameservers.
DNS Parent sent Glue Good. The parent nameserver sent GLUE, meaning he sent your nameservers as well as the IPs of your nameservers. Glue records are A records that are associated with NS records to provide "bootstrapping" information to the nameserver.(see RFC 1912 section 2.3)
Nameservers A records Good. Every nameserver listed has A records. This is a must if you want to be found.
NS NS records from your nameservers NS records got from your nameservers listed at the parent NS are:
Oups! I could not get any nameservers from your nameservers (the ones listed at the parent server). Please verify that they are not lame nameservers and are configured properly.


Recursive Queries Good. Your nameservers (the ones reported by the parent server) do not report that they allow recursive queries for anyone.
Same Glue Hmm,I do not consider this to be an error yet, since I did not detect any nameservers at your nameservers.
Glue for NS records OK. Your nameservers (the ones reported by the parent server) have no ideea who your nameservers are so this will be a pass since you already have a lot of errors!
Mismatched NS records WARNING: One or more of your nameservers did not return any of your NS records.
DNS servers responded ERROR: One or more of your nameservers did not respond:
The ones that did not responded are:
190.241.34.116
Name of nameservers are valid OK. The nameservers reported by the parent send out nothing as shown above. I can't check nothing so it's a green!
Multiple Nameservers ERROR: Looks like you have less than 2 nameservers. According to RFC2182 section 5 you must have at least 3 nameservers, and no more than 7. Having 2 nameservers is also ok by me.
Nameservers are lame OK. All the nameservers listed at the parent servers answer authoritatively for your domain.
Missing nameservers reported by parent OK. All NS records are the same at the parent and at your nameservers.
Missing nameservers reported by your nameservers You should already know that your NS records at your nameservers are missing, so here it is again:

online.skill4reservations.com.
reservas.skill4reservations.com.
www.skill4reservations.com.


Domain CNAMEs OK. RFC1912 2.4 and RFC2181 10.3 state that there should be no CNAMEs if an NS (or any other) record is present.
NSs CNAME check OK. RFC1912 2.4 and RFC2181 10.3 state that there should be no CNAMEs if an NS (or any other) record is present.
Different subnets OK. Looks like you have nameservers on different subnets!
IPs of nameservers are public Ok. Looks like the IP addresses of your nameservers are public. This is a good thing because it will prevent DNS delays and other problems like
DNS servers allow TCP connection OK. Seems all your DNS servers allow TCP connections. This is a good thing and usefull even if UDP connections are used by default.
Different autonomous systems OK. It seems you are safe from a single point of failure. You must be carefull about this and try to have nameservers on different locations as it can prevent a lot of problems if one nameserver goes down.
Stealth NS records sent Ok. No stealth ns records are sent
SOA SOA record No valid SOA record came back!

MX MX Records Oh well, I did not detect any MX records so you probably don't have any and if you know you should have then they may be missing at your nameservers!

WWW WWW A Record ERROR: I could not get any A records for www.skill4reservations.com!

Saludos
Orlando
  #2 (permalink)  
Antiguo 04/05/2010, 02:46
 
Fecha de Ingreso: abril-2008
Mensajes: 2
Antigüedad: 6 años, 7 meses
Puntos: 0
Respuesta: Problemas con DNS

Yo tengo un problema similar con mi dominio elmierdero.mx, bueno, mas bien con todos mis dominios :S desde que migré a este nuevo servidor dedicado e hice sus respectivos cambios de name server hace mas de 1 semana no he podido resolver este problema. Yo tuve que cambiar los dns de mi módem por los de OpenDNS para poder acceder a mi sitio ya que no hay otra forma.

Aqui estan algunos errores que me arroja este reporte de configuración de DNS de mi sitio. http://www.intodns.com/elmierdero.mx

Espero alguien tenga una solución a este problema.
Saludos!
  #3 (permalink)  
Antiguo 04/05/2010, 17:48
Avatar de j_aroche
Server Ninja
 
Fecha de Ingreso: agosto-2006
Ubicación: iPhone: 14.624481,-90.487457
Mensajes: 2.070
Antigüedad: 8 años, 3 meses
Puntos: 223
Respuesta: Problemas con DNS

eduarbo, según IntoDNS te hace falta crear registros A para tus Nameservers:

Cita:
ERROR: Some of your DNS servers do not have A records at all. I could not find any A records for the following DNS servers:
ns1.meborre.com
ns2.meborre.com
Tienes que crear un registro A para ns1.meborre.com, y otro para ns2.meborre.com, asignando una IP diferente a cada registro.
__________________
Blog: JavierAroche.com - Twitter: @j_aroche
  #4 (permalink)  
Antiguo 05/05/2010, 04:40
 
Fecha de Ingreso: abril-2008
Mensajes: 2
Antigüedad: 6 años, 7 meses
Puntos: 0
Respuesta: Problemas con DNS

Cita:
Iniciado por j_aroche Ver Mensaje
eduarbo, según IntoDNS te hace falta crear registros A para tus Nameservers:



Tienes que crear un registro A para ns1.meborre.com, y otro para ns2.meborre.com, asignando una IP diferente a cada registro.
Gracias por el dato, los NS ya estaban bien configurados con su respectiva ip, al parecer el problema fue que los .mx tardan algo en propagarse, igual q los .us, porque eran los dominios q me causaban problemas. Solo me extraña que durara mucho, mas de 1 semana D:

Pero bueno, ya quedó arreglado :P

Etiquetas: dns
Atención: Estás leyendo un tema que no tiene actividad desde hace más de 6 MESES, te recomendamos abrir un Nuevo tema en lugar de responder al actual.
Respuesta




La zona horaria es GMT -6. Ahora son las 02:35.
SEO by vBSEO 3.3.2