Hi there,

Two days ago I knew nothing about nameservers then I got a box from TP and had to learn, and learn quick but I'm still a bit of a noob so apologies in advance.

A couple of days ago I setup ns1.adomain and ns2.adomain but then we decided against this as we have registra problems on that domain and setup ns1.notherdomain and ns2.anotherdomain using WHM. These new nameservers are all sorted at godaddy (who we think are great!) and I've modified a test domain and after propagation found to my amazement that it all worked!

Now I can't remove the ns1 and ns2.adomain from WHN - I have tried and it just will not let me. It says that the IP is now ready for re-use as a diffrent nameserver - argh WHM is lying to me......

I've manually edited these files and no refernce is contained in them to ns1 and ns2.adomain

/etc/nameserverips
/etc/wwwacct.conf
/etc/resolv.conf
/etc/named.conf
/etc/rndc.conf

After editing those I ran these commands:

cd /scripts
./updatenow
./fixndc
(reports "named.conf has already been fixed!")
rndc reload
service named restart
service httpd restart

Yet the old nameservers are still listed in WHM.

Our hostname should be server.anotherdomain yet when I check dnsreports.com it comes up with server.theplaent

How do I totally remove references to the nameservers I don't want and how do I remove references of server.theplanet.com

If anyone can offer a solution to this I'd be very grateful.

Thanks

Assuming you have registered your new DNS at your domain registrar already you may do this.

cd /var/named/
replace ns1.olddomain.tld ns1.newdomain.tld -- *.db

...and just repeat the process for ns2, 3, 4, etc.

Afterwards you should do:
ndc reload or rndc reload

If you have multiple servers DNS servers in a cluster you may want to repeat the process for each, or on the first one, just increase/update the serial numbers for each zone then run these commands.

ndc reload or rndc reload
/scripts/dnscluster syncall

Thanks very much!!!

I did what you recommended and checked WHM. At first the old ns were there but when I went to delete them they finally went so WHM is now looking how I wanted it to look when I go into 'Manage Nameserver IPs'

Now when I check at dnsreport.com it only warms me about:

The nameservers being on the same box
Only 1 MX record
Not accepting mail in the domain literal

Otherwise dnsreport.com gives a clean bill of health.

The namesevers being on the one box and the single MX record I can live with for now but how do I make it accept mail in the domain literal?

I've just been to Orbit and put in a DNS change request so we can have reverse DNS on our domain.

Root, thanks again for your help there. It's really appreciated!

Add this to the first box in Exim Configuration Editor (Advanced Mode):

allow_domain_literals = true

From http://www.exim.org/exim-html-4.40/doc/html/spec.html (emphasis added):

allow_domain_literals
Type: boolean
Default: false

If this option is set, the RFC 2822 domain literal format is permitted in email addresses. The option is not set by default, because the domain literal format is not normally required these days, and few people know about it. It has, however, been exploited by mail abusers.

Unfortunately, it seems that some DNS black list maintainers are using this format to report black listing to postmasters. If you want to accept messages addressed to your hosts by IP address, you need to set allow_domain_literals true, and also to add @[] to the list of local domains (defined in the named domain list local_domains in the default configuration). This “magic string” matches the domain literal form of all the local host's IP addresses.[/b]

Thanks folks, I've managed to get everything working and have decided that the literals issue isn't really an issue. If something ain't broke, why fix it!

If it's okay as it is and domain literals have been abused by spammers there's good enough reason for me not to change it.

Thanks again, especially to root, without your help I'd still be stuck in a nameserver nightmare!