Please, see this dnsreport:

http://dnsreport.com/tools/dnsreport.ch?do...in=dnsready.net

Do you know what is causing the errors?

Thanks,

Pablo

I like the irony of your domain being "dnsready" but you are having DNS problems!

The errors are pretty straight forward:
- All nameservers respond
DNS service not running on ns2.dnsready.net. It would be better to get servermatrix to run a slave domain instead of doing your own secondary DNS

- Connect to mail servers
You should add an A record for mail to your domain
Your MX entry should be changed to mail.dnsready.net instead of just "dnsready.net"
This should also fix the "Reverse DNS entries for MX records" error.

Ross

LOL

I want the secondary NS on the same server, it was working ok before the OS reload. I just want to fix the error, not a workaround, but a real fix

Did you change your nameservers aftr the OS reloaded, if so you have to wait 48h before the new namservers propagate through the net...

Having your seconday DNS on the same server as your primary DNS does not offer much redundency - if you lose your primary you automatically lose your seconday.

Perhaps you should register dns-not-quite-ready.net


Not critical as dnsready.net resolves to an IP correctly.

Anyway, I have only one server for all the hosting services, if I loose this server I do nothing with a secondary DNS server alone

Don't worry, a TP tech fixed the server:



Thank you!

Ah, but do you use this server for email? If so, then you stand to lose any incoming email if the server is down. If a mail client can not resolve your MX record to an IP, the email is discarded immediately. If it can resolve the MX but can't connect to the IP, the mail is queued for later delivery

:shock: :!:


Good point

Good use of smilies