Posted on 2013-06-19
I'm looking for help straightening out our DNS records. One company that is a customer receives a DNS error when they try to reach our website. The IT rep ran a report that said:
NS list does not match list from parent zone. This should be addressed because queries for this domain may require an extra lookup (and more overhead) because there is no direct relationship between the NS records at the parent and the NS records at the authoritative servers. This can cause delays. The mismatched NS list is:
nameserver | 188.8.131.52 is missing ns.groupoe.com. | 184.108.40.206 nameserver | 220.127.116.11 is missing ns2.groupoe.com. | 18.104.22.168
One or more stealth nameservers discovered. This means that one or more nameservers are not listed at both the parent and authoritative nameservers. This can be confusing and can cause delays or other hard to diagnose inconsistencies. The stealth nameservers discovered are:
22.214.171.124 has nameserver p2742624. | listed where other nameservers do not.
One or more stealth nameservers failed to respond. Having stealth nameservers is not optimal or recommended, and if those stealth nameservers are not responding to queries for your domain, it can lead to some very hard to diagnose problems and inconsistencies. This should be addressed.
The stealth nameservers that failed to respond are:
p2742624. | No Glue
No nameservers provided an SOA record for the zone. You should configure your nameservers to have a master slave relationship. The update of the zone information to the slave nameservers should be handled through the SOA record.
I don't really understand what this is saying or what to change. Can anyone assist me?