did a dns report, here are results... help!!

Missing nameservers 2 -
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:
ns1.hostofthefuture.com.
ns2.hostofthefuture.com.

these are my nameservers! does this mean one of the does not work?!?!?!?!

SOA MNAME Check

WARNING: Your SOA (Start of Authority) record states that your master (primary) name server is: ns3.hostofthefuture.com.. However, that server is not listed at the parent servers as one of your NS records! This is probably legal, but you should be sure that you know what you are doing.

I only use ns1 + ns2. I wasnt even aware there was an ns3. how do i change this?

SOA REFRESH value
WARNING: Your SOA REFRESH interval is : 14400 seconds. This seems a bit high. You should consider decreasing this value to about 3600-7200 seconds. RFC1912 2.2 recommends a value between 1200 to 43200 seconds (20 minutes to 12 hours, with the longer time periods used for very slow Internet connections; 12 hours seems very high to us), although some registrars may limit you to 10000 seconds or higher, and if you are using DNS NOTIFY the refresh value is not as important (RIPE recommends 86400 seconds if using DNS NOTIFY). This value determines how often secondary/slave nameservers check with the master for updates. A value that is too high will cause DNS changes to be in limbo for a long time.

where do i change this?

SOA EXPIRE value
WARNING: Your SOA EXPIRE time is : 3600000 seconds. This seems a bit high. You should consider decreasing this value to about 1209600 to 2419200 seconds (2 to 4 weeks). RFC1912 recommends 2-4 weeks. This is how long a secondary/slave nameserver will wait before considering its DNS data stale if it can't reach the primary nameserver.

this aswell?

Multiple MX records
WARNING: You only have 1 MX record. If your primary mail server is down or unreachable, there is a chance that mail may have troubles reaching you.

how do i add another one? Also, what should i add as it?

Acceptance of domain literals

WARN: One or more of your mailservers does not accept mail in the domain literal format (user@[0.0.0.0]). Mailservers are technically required RFC1123 5.2.17 to accept mail to domain literals for any of its IP addresses. Not accepting domain literals can make it more difficult to test your mailserver, and can prevent you from receiving E-mail from people reporting problems with your mailserver. However, it is unlikely that any problems will occur if the domain literals are not accepted.

hostofthefuture.com's postmaster@[67.19.60.2] response:
>>> RCPT TO:<postmaster@[67.19.60.2]>
<<< 501 : domain literals not allowed

seems like a quick fix?



thanks to anyone who helps!!

J

 

 

 

 

Top