Problems with DNS server tests

Avatar
  • Answered
Hi!
When I test DNS servers with my two domain names I receive the following messages. Would you please tell me how I can fix these problems.
Thank you.

aheavenlyhawaiianwedding.com
2012-11-17 00:19:28
Nameserver
ns.inmotionhosting.com.
Name server ns.inmotionhosting.com (74.124.210.242) is recursive.
The name server answers recursive queries for 3rd parties (such as DNSCheck). By making a recursive query to a name server that provides recursion, an attacker can cause a name server to look up and cache information contained in zones under their control. Thus the victim name server is made to query the attackers malicious name servers, resulting in the victim caching and serving bogus data.
ns2.inmotionhosting.com.
Name server ns2.inmotionhosting.com (70.39.150.2) is recursive.
The name server answers recursive queries for 3rd parties (such as DNSCheck). By making a recursive query to a name server that provides recursion, an attacker can cause a name server to look up and cache information contained in zones under their control. Thus the victim name server is made to query the attackers malicious name servers, resulting in the victim caching and serving bogus data.

blisseventplanners.com
2012-11-17 00:05:48
Nameserver
NS1.DOMAIN-IS-4-SALE-AT-DOMAINMARKET.com.
Name server NS1.DOMAIN-IS-4-SALE-AT-DOMAINMARKET.com (174.137.135.164) does not answer queries over TCP.
The name server failed to answer queries sent over TCP. This is probably due to the name server not correctly set up or due to misconfgured filtering in a firewall. It is a rather common misconception that DNS does not need TCP unless they provide zone transfers - perhaps the name server administrator is not aware that TCP usually is a requirement.
NS2.DOMAINMARKET.com.
Name server NS2.DOMAINMARKET.com (77.245.48.84) does not answer queries over TCP.
The name server failed to answer queries sent over TCP. This is probably due to the name server not correctly set up or due to misconfgured filtering in a firewall. It is a rather common misconception that DNS does not need TCP unless they provide zone transfers - perhaps the name server administrator is not aware that TCP usually is a requirement.
Consistency
2 different serials found.
The SOA serial is not the same on all name servers. This is usually due to misconfiguration, but can sometimes be the result of slow zone propagation to secondary name servers.
SOA
Reverse for 174.137.132.100 points to an unknown host name (www1dm.webair.com).
The PTR record for the address points to an unknown host name.
Delivery over IPv4 to [email protected] could not be done.
Failed to deliver email for SOA RNAME of blisseventplanners.com (hostmaster.blisseventplanners.com) using [email protected].
DNSCheck failed to deliver email to the email address listed as the one responsible for the zone.
Avatar
Arn
Hello Wedplan,

Actually, there is nothing wrong with the name servers configured for the hosting here. It's probably being misread by whatever test program you're using because they're expecting UNIQUE name servers specific to your site. This is only available via VPS or Dedicated hosting solutions. Otherwise, the name servers are as they should be and they are configured correctly - all of the hosting servers under Inmotion use these name servers. Only VPS and Dedicated server accounts can have unique name servers.

If you have any further questions, please contact technical support or leave a comment at the bottom of the page.

Regards,

Arnel C.