The Planet Forums > Nameserver problems.

AlphaSRV

Nov 22 2006, 02:30 AM

Using the following tool, http://www.dnsreport.com/tools/dnsreport.ch

I am getting the following errors on my dns servers. My server is dedicated, centos, whm/cpanel. I went through the dns setup guide on the top of this forum and its pretty much the exact samething that I did.

Any ideas on how to fix?

QUOTE

Your NS records at your nameservers are:

ns2.mydomain.net.mydomain.net. [no glue provided] [TTL=86400]
ns1.mydomain.net.mydomain.net. [no glue provided] [TTL=86400]

Shouldn't this be saying, ns1.mydomain.net instead of ns1.mydomain.net.mydomain.net?

QUOTE

WARNING: Your nameservers do not include any corresponding A records when asked for your NS records. They probably are not returning the A records when asked, which can prevent some other DNS servers from contacting your DNS servers. They should do this if they are authoritative for those A records (in BIND, you should not use 'minimal-responses yes;'). The problem record(s) are:

Nameserver xx.xx.xx.xx did not provide any IPs
Nameserver xx.xx.xx.xx did not provide any IPs

I used the add A record option in whm. Both ns's have seperate ips.

Stefaans

Nov 22 2006, 04:14 PM

QUOTE (AlphaSRV)

QUOTE

Your NS records at your nameservers are:

ns2.mydomain.net.mydomain.net. [no glue provided] [TTL=86400]
ns1.mydomain.net.mydomain.net. [no glue provided] [TTL=86400]

Shouldn't this be saying, ns1.mydomain.net instead of ns1.mydomain.net.mydomain.net?

Edit the relevant DNS zone and check that the two NS entries have periods at the ends, i.e. "ns1.mydomain.net." (note the trailing period). Without the trailing period, those entries are understood to be a subdomains of the zone, i.e. your domain name is added to the end of the values to get ns1.mydomain.net.mydomain.net instead of the intended ns1.mydomain.net.

QUOTE

Nameserver xx.xx.xx.xx did not provide any IPs
Nameserver xx.xx.xx.xx did not provide any IPs

This is likely because the NS records have the above errors (no trailing periods).

AlphaSRV

Nov 22 2006, 05:40 PM

Awesome thank you, that did the trick.

Any thoughts on this error?

QUOTE

WARNING: One or more of your mailservers is claiming to be a host other than what it really is (the SMTP greeting should be a 3-digit code, followed by a space or a dash, then the host name). If your mailserver sends out E-mail using this domain in its EHLO or HELO, your E-mail might get blocked by anti-spam software. This is also a technical violation of RFC821 4.3 (and RFC2821 4.3.1). Note that the hostname given in the SMTP greeting should have an A record pointing back to the same server. Note that this one test may use a cached DNS record.

mydomain.net claims to be non-existent host www1.mydomain.net:
220-www1.mydomain.net ESMTP Exim 4.52 #1 Wed, 22 Nov 2006 18:37:53 -0500 220-We do not authorize the use of this system to transport unsolicited, 220 and/or bulk e-mail.

Stefaans

Nov 22 2006, 06:59 PM

You are welcome. I am glad I could help

QUOTE

WARNING: One or more of your mailservers is claiming to be a host other than what it really is (the SMTP greeting should be a 3-digit code, followed by a space or a dash, then the host name). If your mailserver sends out E-mail using this domain in its EHLO or HELO, your E-mail might get blocked by anti-spam software. This is also a technical violation of RFC821 4.3 (and RFC2821 4.3.1). Note that the hostname given in the SMTP greeting should have an A record pointing back to the same server. Note that this one test may use a cached DNS record.

mydomain.net claims to be non-existent host www1.mydomain.net:
220-www1.mydomain.net ESMTP Exim 4.52 #1 Wed, 22 Nov 2006 18:37:53 -0500 220-We do not authorize the use of this system to transport unsolicited, 220 and/or bulk e-mail.

That is a typical error due to the way WHM sets up DNS zones by default.

Using your example: When you create and account, park a domain or create a DNS zone, the MX record will be set to mydomain.net. However, during an SMTP session the server will always announce itself as its hostname, www1.mydomain.net, irrespective of which domain's email it is actually handling.

This is an obvious conflict, but I am yet to seen a case where email is actually denied because of this. Of much more importance is that the main server IP has reverse DNS set up (PTR record that points the main server IP back to the server hostname).

The correct way of doing things (I have not yet bothered) would be to edit your DNS zone templates in WHM, and then set the MX to the server hostname. With the MX set to the server hostname, and SMTP session answering by the same name, there should be no issues.

And oh yes, remember the trailing dot for the host in your MX entry