Superfluous name server listed at parent

Posted on 2012-08-28
Medium Priority
Last Modified: 2012-08-29
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?
Question by:MDauphinais1
LVL 22

Accepted Solution

Matt V earned 2000 total points
ID: 38345544
The zone records for NS should match the registrar records.  If they do not you will get these types of errors.

Whatever the end user enters with their registrar (ns1.mydomain.com) should have corresponding NS and A records in the zone file are your end.

Author Closing Comment

ID: 38347712
Ahh, that did the trick. Adding the NS entry for the domain on the DNS server pointing back to my custom NS fixed the error. I thought that would cause a loop or something but I guess not,


Featured Post

 The Evil-ution of Network Security Threats

What are the hacks that forever changed the security industry? To answer that question, we created an exciting new eBook that takes you on a trip through hacking history. It explores the top hacks from the 80s to 2010s, why they mattered, and how the security industry responded.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Transparency shows that a company is the kind of business that it wants people to think it is.
Creating an OSPF network that automatically (dynamically) reroutes network traffic over other connections to prevent network downtime.
After creating this article (http://www.experts-exchange.com/articles/23699/Setup-Mikrotik-routers-with-OSPF.html), I decided to make a video (no audio) to show you how to configure the routers and run some trace routes and pings between the 7 sites…
Get a first impression of how PRTG looks and learn how it works.   This video is a short introduction to PRTG, as an initial overview or as a quick start for new PRTG users.
Suggested Courses
Course of the Month14 days, 16 hours left to enroll

840 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question