3

UPDATE 2/23/2016 I think my original question was confusing, so I am going to rephrase it: I have my own dedicated nameservers running cPanel DNS Only! I want to know how to give other people vanity nameservers!

Our company has its own dedicated nameservers running cPanel/WHM DNS Only, which are using the hostname ns1.ourcompany.com ns2.ourcompany.com and so forth.

One of our clients is a reseller and wants to use our nameservers but would like to white label them so that it says ns1.theircompany.com, ns2.theircompany.com and so forth.

Is there a hostname alias option that the nameserver will respond to? How would we achieve this?

I've read many time that using CNAME for nameservers is a really bad idea, so I am guessing that is not an option.

UPDATE Feb 2016

I've created A records to point to the nameserver IP addresses and it works! I don't know why it works and how I could prevent someone from pointing to them with a different domain. So if I pointed them to CloudFlare I could use cloudflare as the nameservers? How would CloudFlare prevent that? Also why would creating a CNAME record instead of an A record not work? It has been working for me on Amazon Route 53.

Neo
  • 256
  • 1
  • 3
  • 16

2 Answers2

0

Your question needs to be much improved with details for you to get good answers.

Without such details, all I can say as a superficial answer, is that setting the CNAME record is not enough, or anyone on the Internet could hijack any and all domain-names.

In the end, some authoritative nameserver must accept your nameservers as authoritative for cloudflare.com, and this is surely not going to happen. So anyone performing a DNS report on a domain that uses your 'white label' nameservers will see that those are not the real nameservers and will ignore the result.

Cloudflare will need to assist you in creating the appropriate records, for this to work the way you want it to, since they are the only ones having the needed authority for their domain. CloudFlare is within reason when limiting this option to paid accounts, since this involves work on their part. If they are too costly, you might shop for another supplier.


For your question about using A records or CNAME, the latter have some limitations :

  1. Usage of CNAME records may cause an additional request to the DNS servers, causing a further delay of a few milliseconds. Some DNS servers may send the A records with the answer to a CNAME request to avoid that delay.

  2. You cannot create a CNAME record for the main domain name (mydomain.com) itself, this must be an A record. For example, you cannot map mydomain.com to google.com, however, you can map google.mydomain.com to google.com.

  3. MX or NS (nameserver) records may never point to a CNAME record, only A records.

  4. Problems may occur if one of the A or CNAME records is found in the local DNS cache, but not the other one, in case of a change to the IP address or name.

harrymc
  • 498,455
0

Upon further research for what you are wanting to do, I found a few sites that you might want to look at and read the information on these sites. It appears to answer your questions in detail.


(Snippet From Source Below)

Of particular interest to hosting providers or resellers, having branded or vanity nameservers provides a more professional look to clients. It eliminates the need of asking your clients to point their domains to another company's nameservers. This tutorial will outline two approaches to creating custom nameservers: (i) Vanity and (ii) Branded.

Types => Vanity nameservers allow you to use your own domain name, without having to setup complicated zone files; you can do this using DigitalOcean's nameservers and DNS Manager. This is accomplished by mapping your custom nameservers to DigitalOcean's IPs.

Branded => Nameservers require a little more configuration, but allow you to exert complete control over DNS for your domain. The added control, however, carries with it the burden of having to self-manage your DNS. You'll need to deploy at least two VPS, with specialized software such as BIND, PowerDNS or NSD (for "name server daemon"). Wikipedia publishes a nice comparison of DNS server software.

| Create Vanity or Branded NAMESERVERS |


(Snippet From Source Below)

Can I create the following CNAMEs with "mydomain.com" to effectively whitelabel "mydnsprovider.com"'s nameservers?

ns1.mydomain.com CNAME --> ns1.mydnsprovider.com

ns2.mydomain.com CNAME --> ns2.mydnsprovider.com

| Use CNAME to White Label DNS |


Hope you find what you're looking for mate.