Hello Tim, T> Do I deal with our ISP's badly-run BIND servers, or do I roll the dice T> and hope NSI does not obliterate all nameserver entries for our domain T> when I try to promote my djbdns-run primary nameserver to the helm?
If you've got djbdns running on a permanent connection, AND you can get someone else to be a secondary for you (preferably off-network), I'd say become your own DNS. We have three... one on each of three networks we occupy, and have been since we got our first IDSL. Once you establish them, things get a lot smoother in the internet world! With GODADDY.COM, for example, we need only specify our three servers by name during domain setup. The only problem we've had is when NSI had one of them locked to a particular IP address, which changed; It only affected the one master domain, because all the others went back through a look-up process, so they picked up the change. Had to fix that by removing that named server (actually substituted another name with the same IP), let that propagate, then put it back to the original name. NSI wasn't directly involved, but they had the original name of the server locked in their control for some reason, so changes kind of hit a wall. For the record, though, BIND isn't so bad, if you're used to the syntax that DJB dislikes so much. I can throw together a new zone file, and configure BIND to use it on all 4 of our DNS servers, in 10 minutes. The only thing I dislike, really, is having to restart named to get the master to read a zone file change... Fortunately, that's only a couple of times per month. -- Jeff Brenton President, Engineered Software Products, Inc http://espi.com Questionable web page: http://dididahdahdidit.com Liberalism grants you the freedom to advocate any idea*. * Please see http://www.dididahdahdidit.com/except.php for a current list of exceptions
