Hi there, Just trying to understand the process of setting up private nameservers (is that the same as 'custom' nameservers btw?). I am in the process of setting up a new reseller hosting account where I will be hosting my own sites (1cPanel for each domain). I would like to set up private nameservers for branding purposes, even though I won't be reselling hosting. I understand I'll have to register the main domain to act as private nameservers at my domain registrar. I also understand the bit where the A records have to be edited in the DNS zone files. But I am unsure about the IPs that I would be provided with for that purpose...are they normally dedicated IP's? My account will come with 1 free dedicated IP and free SSL certificate, so I was intending to hold onto them for later. When I check out other hosting provider's FAQ's they seem to just say they provide their clients with 2 IP's for their nameserver set ups. I guess the part I don't understand is how nameservers are set up 'behind the scenes' at my hosting company, i.e. are they running exclusive nameservers with shared IP's for the purpose of giving those out to any client who wants to set up their own private nameservers, or does it always HAVE TO BE a set of dedicated IPs? I am reading conflicting statements in various forums. Is there perhaps a choice normally between using shared IPs for nameservers (where I need to set up my domain as nameservers at my registrar), and using dedicated IP's? I am just not understanding where the Ip's are coming from.... Once my private nameservers would be set up, any WHOIS search on either of my cPanel account domains (and their add-on domains?) would reveal the same private nameserver, correct? Doing then a reverse search on the nameserver domain would then also reveal all my domains under this reseller hosting account (i.e. my main domain, all cPanel domains and all add-on domains in each cPanel account) - correct? That's what I have been seeing by doing some cross-checking on other people's domains, but I am unsure if this is just as a result of using dedicated IP's for their nameserver, or if that would not matter? Or in other words: would it be possible that when someone does a reverse whois on my private nameserver domain, not only my own domains that are all pointing to it would come up in a list, but also other people's domains hosted on the same hosting server? (for instance when the hosting provider gives everyone shared ip's for their private nameservers?) Thanks for plugging this hole in my visual map of how I am trying to understand private nameservers Thanks a lot
This is common thing you can ask from your host support. You need to have at least 2 dedicated IP for this. If you using non dedicated IP,people can easily found by doing RDNS.
Hi mentos, I am not sure if I understand what you are saying...what is it that people can find out if I was NOT using dedicated IP's for my private nameservers? Someone was just telling me that: My provider should provide me with a set of 2/4 name servers (it really depends on the company you choose), I could then move on to creating my own A records using the provided IP addresses. These name server IP addresses can be shared across multiple NS records, once again it depends on the company you choose. I would then have to modify my DNS zone (mydomain.com) and create A entries for each. All I understand is that when I want to set up ONE set of private nameservers and from then point ALL my subsequent domains (cPanel accounts) to this name server, then when ever I do a WHOIS search on either of those domains, once set up, then the resulting WHOIS record will show the same ns1.mydomain.com and ns2.mydomain.com for each of those domains. I have seen this multiple times then, when I WHOIS the name server domain (i.e. mydomain.com), ALL of those domains, and sometimes (but not always) including that nameserver domain come up in a list - but only them, NOT anybody else's domains. My question here is: Does this happen in this way BECAUSE that person was using dedicated IP's, or could this also be "IP addresses [that] can be shared across multiple NS records" as per what I stated above, what someone told me very recently?
Furthermore, what does everyone think of geographically redundant nameservers? Are most hosting providers using multiple DNS's spread across multiple locations/datacenters, in order to avoid a single point of failure? But I have seen many providers giving out only one single IP with instructions to: For ns1.yourdomain.com the ip would be the ip listed in your welcome email. For ns2.yourdomain.com the ip would be the same except change the last number in the ip to be one digit higher. Example: If the ip listed in your welcome email was 69.93.193.74 your ns2.domain.com name servers ip would be 69.93.193.75 ~~~> Does this not constitute using one nameserver location?