 | View Full Version : One Central dns server - how to do it? kaz 08-04-2002, 06:13 AM I see some webhosts use only ns.theirdomain.com and ns1.theirdomain.com for all their customers. Though their domains is all hosted in different servers. How do i setup a centralise dns server where i can tell customer to use one set of dns? What is the advantage and disadvantage? MotleyFool 08-05-2002, 06:18 AM You dont have to do anything special.. you can use one server [or two preferably] as your dns servers(s) and set ns & ns1 on these 2 servers. You just point your A records or MX records to the relevant IP addresses Advantage is that you can move sites as you like all over the Internet in a very short time and with 0 down time.. another advantage is that you are unlikely to lose any email to any site if the DNS is up Disadvantage is that if the DNS server(s) are down ALL sites will be down irrespective of whether the web server is up or not If you are going to centralise DNS better get 3 different servers at 3 topologically diff NOC's and sync the zone records.. If all this is confusing you may either not to do it or you may use a service like zoneedit or everydns.net Cheers Balaji free2learn 08-11-2002, 02:30 PM What type of server/software will you recommend for a DNS Server? Any Windows solutions? Shyne 08-11-2002, 04:25 PM BIND is good for this type of setup. I'm not sure if it supports window$ achost_ca 08-12-2002, 02:05 AM There is a windows port of BIND 9, havent used it, usually if its a windows server, most people stick with M$'s DNS server MotleyFool 08-12-2002, 06:04 AM I recommend djbdns on Unix. It can automatically sync zone records across different nameservers through rsync If you are going to use DNS on a Windows server I have no recommendations except that you may reconsider your decision! You can host your site on Windows and keep the DNS off the server if you can afford it If you want help on this please feel free to email me Cheers Balaji jolly 08-13-2002, 04:26 PM I have server with my own domain name and the same name server. And now if I want to shift my serve to another host how can i do it with 0 downtime. All the domains are pointed to the servers nameserver. justageek 08-13-2002, 04:32 PM Originally posted by MotleyFool If you are going to use DNS on a Windows server I have no recommendations except that you may reconsider your decision! Is there something in particular that you don't like about Windows DNS server? I have used it before and it's pretty straight-forward. NetRemedy 08-31-2002, 08:00 PM Am running Bind 9 on an NT server (master) and on another NT server (secondary 800 miles away from master) for 48 domains and it works flawlessly !! I would recommend understanding BIND before implementing it however, but there is nothing wrong with it. NOW it would be nice to us djbdns but it does not support Windows (yet) wlandman 08-31-2002, 10:53 PM I also vouch for djbdns. It's not so easy to setup since the instructions have to be followed very clearly. But once it is setup, the operation is flawless. It also inter-operates with Bind pretty well. You can use the program that comes with djbdns to pull data directly from your bind dns server (if your thinking of converting). Also when we had BIND and there was a change to data, we had to change the serial and restart the server. Now the server never stops running. All we do is run 'make' and the server rebuilds the data itself.. Plus it hasn't crashed on us yet. -- Walter L Programmer DavidU 09-01-2002, 11:39 AM Originally posted by wlandman I also vouch for djbdns. It's not so easy to setup since the instructions have to be followed very clearly. But once it is setup, the operation is flawless. I think that's the funniest thing I've read all day. You're right Walter, the directions need to be followed for it to work. I love djbdns and I love reading how hard it is to install when you and I know the real secret, the install docs. :D -davidu wlandman 09-01-2002, 11:49 AM Specifically I ran into one small piece of difficulty that was clearly because I mis-read something. I thought tinydns has to run on 127.0.0.1, and dnscache on a public IP address, then the root sever's would query the dnscache and not tinydns directly. It took me a while to realize the my mistake. But finally I did figure it out. :stickout -- Walter Landman Programmer Simplicato - Exceptionally simple web hosting http://www.simplicato.com DavidU 09-01-2002, 11:51 AM Originally posted by wlandman Specifically I ran into one small piece of difficulty that was clearly because I mis-read something. I thought tinydns has to run on 127.0.0.1, and dnscache on a public IP address, then the root sever's would query the dnscache and not tinydns directly. That would be the BIND way of doing things. Then again, BIND stands for "Broken Internet Name Daemon" for a reason. :-) -davidu StevenG 09-03-2002, 06:31 AM I have server with my own domain name and the same name server. And now if I want to shift my serve to another host how can i do it with 0 downtime. All the domains are pointed to the servers nameserver. Just transfer the accounts to a new server - Update your IP's for your name servers at your registrar and you are set. You don't have to update all of your clients domains with the new nameserver IP's - Just yours at your registrar will do just fine :D |