Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am doing a school project. There are 3 sites wich are connected trough vpn, i have my server infrastructure at the head office. Which would be the best option; have a seperate dhcp server at each location or is it possible to use dhcp relay via vpn so that i do not have to place any servers at the other locations? thanks

share|improve this question
also, i wish to use a diffirent scope with diffirent ip range at each site eg. site one will be 192.168.1.x , Site 2 will be 192.168.2.x and site 3 will be 192.168.3.X – Distracted Mar 14 '12 at 22:16

It would depend, to me, on whether there are any servers or other shared resources on-site in each remote office.

If there aren't servers or shared resources in each remote office that could be used independently of a VPN failure then there isn't much point in putting a DHCP server in the remote office. If the VPN has failed then not getting DHCP leases is probably the least of your problems.

If there is some capability for each office to function independently because of on-site servers or other shared resources then I'd strongly consider putting a DHCP server in each remote office. That gives the remote office some ability to function in the face of VPN failure.

Having a single DHCP server also implies a single point of failure but, also, a single point of administration. You'll have to weigh the pros-and-cons of that yourself. For ISC DHCPd or Windows DHCP servers I don't particularly care whether I'm administering one or several. Your feelings may vary.

As long as your VPN hardware (or some other device on each remote office network) supports DHCP relaying you'll have no trouble using a single central DHCP server from a technical feasibility perspective. The address assigned to the network interface of the device receiving / relaying the DHCP requests gets placed into the relayed DHCP request and will allow the DHCP server to serve the request out of the proper scope / subnet.

share|improve this answer
thanks, i will be using a second dhcp server at the main office incase the main one go's down. – Distracted Mar 14 '12 at 22:27

It isn't uncommon to find the device in each location that is making the VPN connection is also capable of acting as a DHCP server - e.g. Cisco ASA, Linux server, pfsense, m0n0wall.

Depending on the capacity of the device and number of clients at the site, this might be worth taking advantage of.

This is particularly useful where there may be site specific configuration you want to push out via DHCP. For example, you might want to include a public DNS server in the list of DNS servers assigned, so in case the VPN fails, but the Internet is up, people at the remote site can access public resources even if your central DNS is unreachable.

It is also a lot easier to visualise/explain this way.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.