Domain NS records Nameserver records returned by the parent servers are: ns1.nxservepro.com. ['207.150.183.52'] (NO GLUE) [TTL=86400] ns2.nxservepro.com. ['207.150.183.53'] (NO GLUE) [TTL=86400 a0.info.afilias-nst.info was kind enough to give us that information. Missing nameservers reported by parent FAIL: The following nameservers are listed at your nameservers as nameservers for your domain, but are not listed at the parent nameservers (see RFC2181 5.4.1). You need to make sure that these nameservers are working.If they are not working ok, you may have problems! ns2.nxserve.net ns1.nxserve.net Missing nameservers reported by your nameservers 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: ns2.nxservepro.com ns1.nxservepro.com 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). Different subnets WARNING: Not all of your nameservers are in different subnets Different autonomous systems WARNING: Single point of failure SOA MNAME entry WARNING: SOA MNAME (ns2.nxserve.net) is not listed as a primary nameserver at your parent nameserver! ---------------- CHECK DNS tool DNS server ns1.nxservepro.com[207.150.183.52] is alive and authoritative for domain pinoynurses.info DNS server ns2.nxservepro.com[207.150.183.53] is alive and authoritative for domain pinoynurses.info 2 server(s) are alive Master DNS defined by SOA (ns2.nxserve.net) was not found among NS records. All 2 your servers have the same zone version 2009041501 NS list mismatch: registration authority reports that domain is hosted on the following servers: 'ns1.nxservepro.com; ns2.nxservepro.com', but DNS server ns1.nxservepro.com reports domain to be hosted on 'ns1.nxserve.net; ns2.nxserve.net'. Please make sure that you configure the same DNS servers in registrar database and on your DNS need help! my domain is messed up with my dns.. it is almost about 3 days already since my last update last april 15 for my dns..
Go to the DNS zone editor of your domain and change NS records for your domain in DNS zone: Set DNS zone as follow: pinoynurses.info. NS ns1.nxservepro.com. pinoynurses.info. NS ns2.nxservepro.com. And remove following entries: pinoynurses.info. NS ns1.nxserve.net. pinoynurses.info. NS ns2.nxserve.net. Your both nameservers are in same subnet hence it is giving warning. Because both nameservers IP addresses are in same subnet. Edit SOA record for your domain and replace ns2.nxserve.net with ns1.nxservepro.com Kailash
what if i dont have an access to my domain Dns editor? just a Nameserver field list for adding a nameserver.. my registrar doesnt have a dns control panel.. thanks for the reply anyway.. is there any other solution? is this issue from my registrar not on my host? thanks again..
Do you have root access? only then you could change dns records. If not just ask your host to do it. see this dns guide Your domain should point to nameservers and those nameservers should point to A record its just warning ignore it! This means if your one dns server (same ip subnet) goes down it wont resolve. You should setup primary dns ip with one host and secondary dns ip on different geographic location!
i dont have an access either on my host root folder.. im just hosting to their premium account.. before i used to host on a free server but due to downtime i transfer to paid server, changing my domain nameserver list from free to paid has cause this to conflict my dns records.. is it the problem by my host or by my registrar? thank you, Andrew
You do not need to perform that changes that I have mentioned on registrar end but you will need to make this changes in the DNS zone of hosting server. If you do not own the server and you are on shared server, you will need to update your hosting provider. Kailash
thanks for the reply.. is this a DNS cache poisoning? why my DNS records are mess up? whats the cause? thank you, Andrew
Because you have set different nameservers set in Parent (at registrar end) and your domain has different NS record in the DNS zone at hosting end. Not sure about DNS poisoning. Kailash