custom/alias nameservers
I believe this is called aliasing nameservers, and it is possible because whatever "proper" name a DNS server may have, it will respond to queries about any "zone" that it contains regardless of the name you use to refer to that DNS server. I hope that language makes sense.
Hunky dory, until I do a dnsreport.com query for a hosted domain name that has ns1 and ns2.mydomain.net specified in the registrar records. There are leaks of stealth nameservers galore, etc etc; the long and the short of it is that it probably works in most cases, but certain standards aren't met, and that may cause problems.
I have found that editing the individual zonefile for that domain in whm I can stop those errors and leaked or stealth dns server names. It involved editing the SOA record to read that the master DNS server is ns1.mydomain.net and NS records to read ns1 and ns2.mydomain.net.
I don't trust the DNS server IPs that I have been given, they are both on the same machine. I will therefore use an external DNS management service like zoneedit.
1. Can I set up the DNS zones on the zoneedit servers, then set the IPs for ns1 and ns2.mydomain.com to point at the zoneedit IPs? I'm thinking yes, but I'm not sure if it's a particular configuration that allows bind (for example) to respond to any name it's given, or whether it's a feature universal to all DNS servers.
2. if 1==true { To stop the errors and leaked details about the true names of the DNS servers, I need full access to the SOA primary nameserver/DNS contact email records and NS records. Zoneedit doesn't let you delete NS records in your zones referring to their nameservers, so that's not ideal. Is there another DNS management service that allows the required control?
3. Is it a Bad Thing to change any of the mentioned records in this way?
Many thanks,
Olly.
Disclaimer: It is very very late here in the UK, and my head is slowly turning to mush, so please forgive any rubbish that I post.
