phranque
msg:4161109 | 6:08 am on Jun 29, 2010 (gmt 0) |
one of the major advantages to how DNS works is that you can specify multiple servers and you should do so in such a way that maximizes redundancy and autonomy.
in other words you want to avoid a single point of failure.
ideally the servers you specify would be on different class C networks, geographically diverse, and owned & operated by different organizations.
so i'm not sure exactly what you're describing but it sounds likely that there is too much sharing of resources among your name servers and between your name servers and your web server.
|
hamids54
msg:4161854 | 4:55 am on Jun 30, 2010 (gmt 0) |
I have one dedicated server.there are two websites on there.
I am registrar of my domains.I created child nameservers for one of my domains and now I have my own nameservers.
now I have new manager server.I want to know why previous server manager offered me to use the nameservers that I mentioned on my first post.is there any difference? hope to make be underestanded. sorry for my poor english.
|
lammert
msg:4162689 | 11:35 am on Jul 1, 2010 (gmt 0) |
Having the DNS records on a separate DNS server can be good in times when your server crashes. With a webserver crash, you can change the DNS records to a new IP address where you have uploaded a recent backup of the site, and then start to recover the old server. Users will be redirected to the new IP address. If both the sites and the DNS records reside on the same server when a crash occurs, recovery can be much more difficult.
|
adephue
msg:4185155 | 2:40 am on Aug 11, 2010 (gmt 0) |
You have to pay close attention to name servers offered by hosting companies. In some cases it is one name server that has two IP addresses.
I like to utilize either third party DNS services or host my own on separate physical servers. I wrote a primer/proof-of-concept that outlines failover name servers for reliability and uptime [blog.dephuedatadesign.com].
|
|
