Superfluous name server listed at parent
Posted on 2012-08-28
I am looking to resell web hosting and I want to create custom name servers as a central point for all customers to point their domains to regardless of what server their website ends up being hosted on. To try and do this in the most efficient manor, I have 3 components: My domain registrar, a separate DNS server (third-party hosted), and my resell web servers (could be spread across multiple vendors).
This is the setup I have currently:
Domain Registrar - Registered custom name servers:
- ns.mydomain.com points to the IP of the primary NS at my DNS server
- ns2.mydomain.com points to the IP of the secondary NS at my DNS server
Third-Party DNS Server:
- Here I create a zone for each domain that will host a website on one of my resell servers. Say I create an account for abc.com on web server #1 that has the name servers ns1.webserver.com and ns2.webserver.com. I go into the zone for abc.com on the DNS server and set the NS records to ns1.webserver.com and ns2.webserver.com.
Using this setup, if the owner of abc.com sets their NS records at their registrar to ns.mydomain.com and ns2.mydomain.com, my goal is to have it flow to ultimately point them at their web server (and never requiring them to set their NS to the actual NS of the web server).
Currently with this setup, if I do a DNS check at pingdom.com I am getting this error:
Superfluous name server listed at parent: ns.mydomain.com
Superfluous name server listed at parent: ns2.mydomain.com
Total parent/child glue mismatch.
Can you please tell me where I went wrong and how I can set this up in the most robust and efficient manor?