Imago
25/11/2006, 14h41
Still, the secondary nameserver which is ns.ovh.net is reported now 7th day lame:
The primary ns reports, - Port unreachable
As a result, nothing works.
The fail-over IPs do precisely what they promiss - help the primary IP to fail when assigned for nameservers.
I am using cPanel @ FreeBSD @ Superplan 2007 L+ - a rocket-fast combination even at the background of my present Dual Xeon 2.8 server with RHEL.
Lame nameservers ERROR: You have one or more lame nameservers. These are nameservers that do NOT answer authoritatively for your domain. This is bad; for example, these nameservers may never get updated. The following nameservers are lame:
212.27.32.132 (ns.ovh.ne)
As a result, nothing works.
The fail-over IPs do precisely what they promiss - help the primary IP to fail when assigned for nameservers.
I am using cPanel @ FreeBSD @ Superplan 2007 L+ - a rocket-fast combination even at the background of my present Dual Xeon 2.8 server with RHEL.