DNS and B*ND?
Aug. 25th, 2009 07:06 amWork has asked me to look at setting up a new server (Or pair of servers) to run as dual role DNS servers, looking up forwarded DNS requests from our network and being authoritive for external requests from third parties.
Now I haven't touched the stuff since 2001, so I'm rather rusty. Back then I wasn't working on the coalface of it either, but I do remember using bind (Did I mention these are destined for Linux boxes?) when I did do this stuff.
The question, however, has been asked:
"Is bind still current, or has the industry moved on to something easier to manage?"
To which I don't have an easy answer. So I turn to you, my network of readers. This is for a production environment so security, scalability and reliability are paramount. If this means "Use bind, even if it is a pig cos it's damned robust" then so be it.
Now I haven't touched the stuff since 2001, so I'm rather rusty. Back then I wasn't working on the coalface of it either, but I do remember using bind (Did I mention these are destined for Linux boxes?) when I did do this stuff.
The question, however, has been asked:
"Is bind still current, or has the industry moved on to something easier to manage?"
To which I don't have an easy answer. So I turn to you, my network of readers. This is for a production environment so security, scalability and reliability are paramount. If this means "Use bind, even if it is a pig cos it's damned robust" then so be it.