I would add, that while win2k is ok for internal network dns resolution I have found linux and bind to be more reliable and a better choice for a public dns server (cheaper cost of ownership too - after initial configuration).
-Mark -----Original Message----- From: Dave Wilson [mailto:[EMAIL PROTECTED] Sent: Monday, June 23, 2003 9:07 AM To: CF-Talk Subject: RE: To DNS or not to DNS...that is the question. > > I wouldn't. its nice to segregate services...so that if you have to > restart either > of the servers that wont adversely affect the other.... > Not only is it advisable to segregate the services. In the case of DNS it is advisable to run DNS servers (yes multiple servers) dispersed across multiple remote networks (i.e. multiple internet locations) for reliability. Your client only needs win2k/IIS/CF running on their web server. Let the registrar handle the DNS zonefiles. If you want further control over your client's DNS, use a registrar which provides DNS zone management utilities (most provide this as standard nowadays). HTH, Dave ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4 Subscription: http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4 FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Get the mailserver that powers this list at http://www.coolfusion.com Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
