Can I use multi-purpose servers for authoritative bind dns servers?

[Warren Kumari]

On Sat, Jan 5, 2019 at 7:06 AM Tom Browder <tom.browder at gmail.com> wrote:

> I have two remote servers: (1) one with one IP (used mainly for backups)
> which is planned to be an OpenStreetmap tile server and (2) one with five
> IP addresses used for serving my personal websites with Apache and planned
> to be a mail server.
>
> Note I am currently running mostly static sites but am in the process of
> setting up more dynamic sites running behind a proxy on the apache server.
> Public usage is very light at the moment and probably will remain that way.
>
> Question: Can I use one or both servers as authoritative bind dns servers,
> or should I get one or two dedicated servers for that purpose?
>

Yup, you sure can — in general the resources required to run Bind / DNS for
“normal” usage is fairly small.

YMMV if you are doing this for a large / popular name, or if your existing
boxes are *horriably* overloaded, but generally it’s fine...

>
> If they are usable, is it preferable to have a unique IP instead of
> sharing with other services?
>

Sharing is fine. Having a dedicated IP address *might* be useful under DOS
conditions (easier to ask your isp to null route an up than filter port
53), but not really important...

W


> Thanks, and Happy New Year!
>
> -Tom
> _______________________________________________
> Please visit https://lists.isc.org/mailman/listinfo/bind-users to
> unsubscribe from this list
>
> bind-users mailing list
> bind-users at lists.isc.org
> https://lists.isc.org/mailman/listinfo/bind-users
>
-- 
I don't think the execution is relevant when it was obviously a bad idea in
the first place.
This is like putting rabid weasels in your pants, and later expressing
regret at having chosen those particular rabid weasels and that pair of
pants.
   ---maf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/bind-users/attachments/20190105/7c28ac91/attachment.html>