sustain
a little downtime.
Good luck,
RW
From: bind-users on behalf of Fred Morris
Sent: Wednesday, January 8, 2025 2:11 PM
To: Bind-users
Subject: Re: Bind and DHCP
This email originated from outside of TESLA
Do not click links or open attachments unless
Good operational network design calls for network segmentation; proper
segmentation implies the functions of DDI to be technically (as opposed to
organizationally) managed by segment. This would include actual recursing
resolvers and DHCP services, not forwarders, at the segment edge.
A lot of
On 1/8/25 10:14 AM, John Thurston wrote:
You may want those services co-hosted today. But if you want to separate
them next year, your life will be easier if they had unique IP addresses
from the start.
I agree that different IPs for each service is more flexible.
Though I've never found it d
+1 for Greg's suggestion.
You may want those services co-hosted today. But if you want to separate
them next year, your life will be easier if they had unique IP addresses
from the start.
--
Do things because you should, not just because you can.
John Thurston907-465-8591
john.thurs...@a
Hi Karol.
You can run them both together, if you like. I think it comes down to a
personal choice between economics, simplicity, cleanliness of design and
performance. If you want your DNS server to handle many 1,000 QPS it might
be better dedicating resource to that and put Kea (I assume Kea?) on
On 08.01.25 15:34, Karol Nowicki via bind-users wrote:
Does a good practice recommend to split running ISC Bind and DHCP into two
different machines or make DNS+DHCP running on same server is allowed ?
you can run both on the same server. If you ran, run them both on multiple
machines to ha
6 matches
Mail list logo
