Search Again: Re: BIND was :Secondary IP Port Mapping Bug From: Nicholas Orr Date: Monday, August 13, 2001 Time: 9:15:16 pm In a nutshell I don't see any problem with this, as the bind software is well received and well supported in the open source community. However.... Can m&m tell us which version of the bind codebase is used in the current QuickDNS? How soon would you expect bug fixes in bind to be implemented in an update? If I hear about a major security hole in bind (as has happened before) can I assume it's also possibly in quickdns? How significant are the changes that m&m made, and in what parts of the code? I'm happy to be paying for this software, and I appreciate the work that has gone in to the interface, but it seems we have lost one of the benefits of open source if we can no longer rely on the actual open source software. Did m&m ever consider shipping the source code to bind, so that you could simply re-compile the newer version into quickdns, and have the best of both worlds? (It seems I've raised a few thorny issues there. Don't take this as dismissal of your software or the effort you've put into it.) Nick On Tuesday, August 14, 2001, at 01:57 PM, Men & Mice Support wrote: >> To run a name server under OS X, we'll be stuck with BIND? > > Well, so far we've made a few minor changes to the stock Bind codebase, > but essentially, yes.

Messages In This Thread: Re: BIND was :Secondary IP Port Mapping Bug by Nicholas Orr on Aug 13, 2001 at 9:15:16 pm Re: BIND was :Secondary IP Port Mapping Bug by Men & Mice Support on Aug 13, 2001 at 9:48:59 pm