View Full Version: What's The Point?

Domain Name Services > Nameservers > What's The Point?


Title: What's The Point?
Description: Nameservers run on same machine as site.


samspin - July 26, 2005 03:29 PM (GMT)
What is the point in making the rule 'you must have 2 nameservers on different Cblocks so they on different machines'? I have loads of domains, and they all have nameservers here:
ns1.samspin.com 209.59.177.6
ns2.samspin.com 209.59.177.52
ns3.samspin.com 209.59.177.37
ns4.samspin.com 209.59.177.38
My WEBSITE runs on the same machine as the nameservers- so you can't get any more reliable than that! If the machine goes offline, both site and DNS don't work anyway! What's the point in getting secondary DNS just to abide by these rules, when if my site goes offline, the DNS will be useless anyway? It will point to a 'dead' site. I think the rules should be adjusted to allow this kind of nameserver setup. If not, if I set up some free .com.ru domains and point to the nameservers above (but replace ns4.samspin.com with t4l1.samspin.com which is mapped to ns1.twisted4life.com, a secondary DNS provider on a different IP block)? These nameserver rules are really annoying, and in my case, pointless...

dnsau - July 28, 2005 05:16 AM (GMT)
It is obvious that you are not familiar with dns protocols. RFC 2182 3.1 states "that nameserver IPs must be in geographical and topographical dispersed locations". This means that the secondary nameserver IP must be in a different subnet range to the primary IP subnet or in a different geographical location i.e. different country or different state as in the US.

Data Centers in the US and Europe mass produce servers online with disregard to the above RFC, mainly because the TLD domain providers do not insist on this rule, but most country tld registries still require its adherence as does the .ru registry. Another point is that most people who order servers nowadays are trying to break into the hosting field whether for the free or for profit aspect. These people are mostly ignorant about dns protocols.

You can get servers with these requirements relating to the RFC, but it is difficult in the US where your server is housed. If you had of stipulated this requirement when you purchased the server the Data Center may have obliged, but many won't do it because they state that it is not part of their infrastructure. Which is a stupid excuse because it is an easy process with several ways of doing it. Also it is restrictive to what domains you can host.

We have several servers and they are all setup this way with nameserver IPs in different subnets, both in the US and Europe. You just have to search around for the right data center.

To learn more about DNS and the its workings go to DNSRD there you will find lots of information about DNS and RFC's.


samspin - November 27, 2005 09:18 PM (GMT)
I think I have learnt it out now... All my domain names now have secondary DNS on different networks. Let's just say I feel a total fool now, after reading all the DNS info on dnsstuff.com... took ages... I apologize for the above post...
No wonder I couldn't register a .de domain properly before! The .de domain has these requirements as well...
I have resubmitted my free domain applications now that I meet the requirements. Thanks for the help dnsau!
P.S. I already know .com.ru is suspended by RIPN due to abuse... shame, I wanted one.




Hosted for free by InvisionFree