I am having a few issues with my DNS setup for some reason. I did the rndc fix but after that I get the following warning:
Attempting to restart bind
Waiting for bind to restart.... . . . . . . . . . . finished.
rndc: connection to remote host closed This may indicate that the remote server is using an older version of the command protocol, this host is not authorized to connect, or the key is invalid.
Edit: FIXED by doing the following steps
CODE
First, edit these files
/etc/rndc.conf
/etc/named.conf
and remove any hyphens from "rndc-key" (so that it reads "rndckey"
Then execute these commands.
/scripts/fixnamed
/scripts/fixndc
/scripts/fixndc
service named restart
service named restart
/etc/rndc.conf
/etc/named.conf
and remove any hyphens from "rndc-key" (so that it reads "rndckey"
Then execute these commands.
/scripts/fixnamed
/scripts/fixndc
/scripts/fixndc
service named restart
service named restart
[b]Open Issues:
DNSReport.com reports:
QUOTE
FAIL All MX IPs public
Error: At least one of your MX records points to an IP address that is not a public IP. The problem IP(s) are:
67.18.2.xxx is not a public IP
Note that these IPs are not reachable, which can cause extra resource usage, slight mail delays, and possibly bounced mail.
Error: At least one of your MX records points to an IP address that is not a public IP. The problem IP(s) are:
67.18.2.xxx is not a public IP
Note that these IPs are not reachable, which can cause extra resource usage, slight mail delays, and possibly bounced mail.
also:
QUOTE
Error: At least one of your NS records points to an IP address that is not a public IP. The problem IP(s) are:
67.18.2.xxx is not a public IP67.18.2.xxx is not a public IP
These IPs are not reachable on the Internet, causing DNS delays, extra resource usage, and possibly no DNS response.
67.18.2.xxx is not a public IP67.18.2.xxx is not a public IP
These IPs are not reachable on the Internet, causing DNS delays, extra resource usage, and possibly no DNS response.
and:
WARN NS TTL discrepancy
Warning: Your NS records at your authoritative DNS servers have TTLs that do not match what the parent servers report:
QUOTE
NS1.mydomain.us. [TTL 7200 at parent; 14400 at 67.18.2.xxx]NS2.mydomain.us. [TTL 7200 at parent; 14400 at 67.18.2.xxx]
In some cases, this can cause some serious problems. For example, if the parent servers have a 172800 second TTL (48 hours), and your authoritative DNS servers report a TTL of 3600 seconds (1 hour), you are saying that the parent DNS servers do not have the correct information. But, after 1 hour your DNS records may time out. At that point a DNS resolver will need to get fresh NS records. This can cause a serious problem in some cases.
In some cases, this can cause some serious problems. For example, if the parent servers have a 172800 second TTL (48 hours), and your authoritative DNS servers report a TTL of 3600 seconds (1 hour), you are saying that the parent DNS servers do not have the correct information. But, after 1 hour your DNS records may time out. At that point a DNS resolver will need to get fresh NS records. This can cause a serious problem in some cases.
Any idea how to get rid of some or all of these warnings / fail troubles ?
Thanks a lot