Guest Enrique Posted October 1, 2007 Posted October 1, 2007 Running Win 2K3, and Verizon currently host my DNS records but I want to look at hosting my own DNS. What do I need to do in order to host my own public DNS? Thanks, Enrique
Guest Lanwench [MVP - Exchange] Posted October 1, 2007 Posted October 1, 2007 Re: Hosting DNS Enrique <enrique@avertinc.com> wrote: > Running Win 2K3, and Verizon currently host my DNS records but I want > to look at hosting my own DNS. What do I need to do in order to host > my own public DNS? > > Thanks, > Enrique Hate to say it, but "if you have to ask...." perhaps this is a bad idea. The short answer is, you need two DNS servers on an isolated network. In fact, I don't see why you'd want to use Windows for it anyway. If I were you, I'd leave this role on servers in a datacenter with redundant everything. I wouldn't stay with Verizon, though - I'd find someone else. I personally like DynDNS (their CustomDNS service is nice).
Guest Enrique Posted October 1, 2007 Posted October 1, 2007 Re: Hosting DNS You are absolutely right in that it's probably a bad idea, because I know a little about my internal DNS, but for the most part, since I got it up I haven't had to alter my settings much. Unfortunately, my boss wants to make this change because of cost savings and speed of our internet connection and move from Verizon (1.5Mbps) which host our DNS to AT&T (3 Mbps) which will not. I have 2 internal DNS servers which also handles my AD enviroment. Why isolated and is there anything I can reference on how they should be setup? "Lanwench [MVP - Exchange]" <lanwench@heybuddy.donotsendme.unsolicitedmailatyahoo.com> wrote in message news:u2NuaYDBIHA.4612@TK2MSFTNGP03.phx.gbl... > Enrique <enrique@avertinc.com> wrote: >> Running Win 2K3, and Verizon currently host my DNS records but I want >> to look at hosting my own DNS. What do I need to do in order to host >> my own public DNS? >> >> Thanks, >> Enrique > > Hate to say it, but "if you have to ask...." perhaps this is a bad idea. > The short answer is, you need two DNS servers on an isolated network. In > fact, I don't see why you'd want to use Windows for it anyway. > > If I were you, I'd leave this role on servers in a datacenter with > redundant everything. I wouldn't stay with Verizon, though - I'd find > someone else. I personally like DynDNS (their CustomDNS service is nice). >
Guest msnews.microsoft.com Posted October 1, 2007 Posted October 1, 2007 Re: Hosting DNS "Enrique" <enrique@avertinc.com> wrote in message news:%231SAheEBIHA.5652@TK2MSFTNGP05.phx.gbl... > You are absolutely right in that it's probably a bad idea, because I know > a little about my internal DNS, but for the most part, since I got it up I > haven't had to alter my settings much. Unfortunately, my boss wants to > make this change because of cost savings and speed of our internet > connection and move from Verizon (1.5Mbps) which host our DNS to AT&T (3 > Mbps) which will not. Who is your registrar? I currently use GoDaddy, and they provide quite acceptable DNS hosting (at no extra charge), including full control of my DNS records. It is a web interface; I don't know if they support zone transfers. However, since less than a dozen host names are visible outside of my local network, managing them manually is not great burden.
Guest Lanwench [MVP - Exchange] Posted October 1, 2007 Posted October 1, 2007 Re: Hosting DNS Enrique <enrique@avertinc.com> wrote: > You are absolutely right in that it's probably a bad idea, because I > know a little about my internal DNS, but for the most part, since I > got it up I haven't had to alter my settings much. That's good, but isn't really relevant here.... > Unfortunately, my > boss wants to make this change because of cost savings Tell him in nice language that this is a really dumb idea. He doesn't know what it entails (and by your own admission, neither do you). If something goes wrong, is he prepared to deal with the consequences (clients not being able to get to your website, mail server, whatnot)? Don't host your webserver on your LAN, and don't host your own DNS unless you've got the infrastructure to support it. You probably won't. > and speed of > our internet connection and move from Verizon (1.5Mbps) which host > our DNS to AT&T (3 Mbps) which will not. Your ISP should rarely host your DNS. Whom you're using for your connection isn't relevant to your DNS, your webhosting, your mail servers, or your domain registrar, even. > > I have 2 internal DNS servers which also handles my AD enviroment. But that isn't going to help you. You would need two entirely separate/isolated DNS servers, as I mentioned. You mustn't let your internal/external DNS touch. > Why isolated You will break your AD and expose your network to a big security risk. > and is there anything I can reference on how they > should be setup? > > > "Lanwench [MVP - Exchange]" > <lanwench@heybuddy.donotsendme.unsolicitedmailatyahoo.com> wrote in > message news:u2NuaYDBIHA.4612@TK2MSFTNGP03.phx.gbl... >> Enrique <enrique@avertinc.com> wrote: >>> Running Win 2K3, and Verizon currently host my DNS records but I >>> want to look at hosting my own DNS. What do I need to do in order >>> to host my own public DNS? >>> >>> Thanks, >>> Enrique >> >> Hate to say it, but "if you have to ask...." perhaps this is a bad >> idea. The short answer is, you need two DNS servers on an isolated >> network. In fact, I don't see why you'd want to use Windows for it >> anyway. If I were you, I'd leave this role on servers in a datacenter >> with >> redundant everything. I wouldn't stay with Verizon, though - I'd find >> someone else. I personally like DynDNS (their CustomDNS service is >> nice).
Recommended Posts