Domain Controller with multiple network interfaces

Occasional Contributor

I have two DCs which have network interfaces on two or three different VLANs. I only need a response on the corporate LAN, but the other VLAN is for VOIP and one server has a third network for VLANed traffic that doesn't touch the corporate LAN but still goes out to the internet.


In networking I have selected the tick-box for 'register this connection's address in DNS ' for only the network interface on the corporate LAN. However DNS is getting all the two (or three) addresses and ping is failing because it is resolving the address to an IP address that I don't expect to respond on that VLAN.


Why is this happening and how can I resolve it? This is Windows 2016 Server, by the way.



7 Replies

Multi-homing a domain controller will always cause no end to grief for active directory domain DNS. Better option is to install the viop software on another instance of windows.



Thank you... The other networks are on the DC because it's also doing DHCP. Should I have a separate DHCP server in the VOIP VLAN to provide addressing to the phones?

Better option is to use layer 3 routing hardware for this purpose. If you must do it on windows then use another member server for this role.




Thanks. We have L3 switches so I'm not sure what has been done. Can you refer me to any best practice?

Your router should have a dhcp relay agent option.

Support multiple subnets with one DHCP server by configuring DHCP relay agents | Microsoft Docs

DHCP Subnet Selection Options | Microsoft Docs


(please don't forget to mark helpful replies)



To be clear the phone system is running on a different server.
best response confirmed by TimGowen (Occasional Contributor)

Sounds good, just don't multi-home your domain controllers.


(please don't forget to mark helpful replies)