Full Version: general question: advantages of running your own NS?
any advantages to do this? why not rely on ns1.theplanet.com and ns2.theplanet.com??
It looks better / more professional for your customers to point their domain to something like ns1.yourcompanynamehere.com and ns2.yourcompanynamehere.com
You have considerably more control over DNS and are able to automate DNS-related tasks.
i could understand the first reason, however, wouldn't it be easier to point/redirect ns1.yourcompany.com to ns1.theplaent.com ...etc instead?
i don't see the value in setting up your own ns and having to administer it when you have an entire staff at TP that does that already to keep their NS up. there are a million and one other things we need to do and NS is one thing I am happy not to worry about. my 2 cents...
i don't see the value in setting up your own ns and having to administer it when you have an entire staff at TP that does that already to keep their NS up. there are a million and one other things we need to do and NS is one thing I am happy not to worry about. my 2 cents...
If you want your own ns1.yourcompany.com but don't want the hassle of managing your own name servers, I would recommend www.dnsmadeeasy.com. They allow you to use vanity name servers so you get the best of both worlds - check out http://www.dnsmadeeasy.com/s0306/tuts/vanitydns.html
QUOTE (atm2000)
i don't see the value in setting up your own ns and having to administer it when you have an entire staff at TP that does that already to keep their NS up. there are a million and one other things we need to do and NS is one thing I am happy not to worry about. my 2 cents...
But what happens if there is a power outtage in D2 like there was earlier this year? NS1 & 2 went down, and so did everyone's domains....
I use to have all our NS servers in different datacenters (and our master wasn't even @ TP, it was on our T1 via another provider), but since I moved our T1 over to TP, I'd be in trouble if their D3 went down...
Otherwise, I like having updates happen quickly, and not every hour. There are times when I need an update to happen faster than TP can do it because of their Nameserver reload policies.
QUOTE (Hogie)
QUOTE (atm2000)
i don't see the value in setting up your own ns and having to administer it when you have an entire staff at TP that does that already to keep their NS up. there are a million and one other things we need to do and NS is one thing I am happy not to worry about. my 2 cents...
But what happens if there is a power outtage in D2 like there was earlier this year? NS1 & 2 went down, and so did everyone's domains....
I use to have all our NS servers in different datacenters (and our master wasn't even @ TP, it was on our T1 via another provider), but since I moved our T1 over to TP, I'd be in trouble if their D3 went down...
Otherwise, I like having updates happen quickly, and not every hour. There are times when I need an update to happen faster than TP can do it because of their Nameserver reload policies.
reloads are important, i completely agree. if TP goes down (all their DCs) there are bigger problems.
question, how can i find out TP's NS for each DC? i like the idea of spreading the NS to different geographical locations.
QUOTE (Hogie)
But what happens if there is a power outtage in D2 like there was earlier this year? NS1 & 2 went down, and so did everyone's domains....
This will soon be a non-issue where the name servers are concerned.
QUOTE (jamesn)
This will soon be a non-issue where the name servers are concerned.
"soon"... The problem is that everything is "Soon". RealTime in Orbit... "Soon", fixed uplink graphs "soon" (I think klaude finally fixed them...), other TLD's in orbit to purchase, "soon".
It has been an issue. I didn't go down when everyone else did, because I didnt trust someone else with my dns hosting...
DNS servers are pretty stable. BIND 9 in my limited experience was pretty good. Windows 2k3 is freaking ROCK solid. If your box is running, and your skilled at DNS (Which you should be if you want to host clients) it's not that much extra overhead.
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.