This is my setup...
Windows 2012 R2 Core servers with 4 NICS to be used for hyperv
NIC1 - Management network
NIC2 - HyperV live-migration network
NIC3 - NAS network/iSCSI
NIC4 - trunked VLANs for virtualmachines and stuff (including regular network)
I'd like to use DHCP to assign these as I will have quite a few of them, and it's easier for the rest of the staff than to fiddle around with the Core servers.
My DHCP server scopes:
Regular scope - 192.168.0.0/24, options router, dns/ad and domain name (co.net)
Scope for NIC1 - 192.168.1.0/24, options router, dns/ad and domain name (co.net)
Scope for NIC2 - 192.168.2.0/24, options only domain name (hyperv.co.local)
Scope for NIC3 - 192.168.3.0/24, options only domain name (nas.co.local)
My AD/DNS has the following forward zones:
co.net
hyperv.co.local
nas.co.local
My AD/DNS has the following reverse lookup zones:
0.168.192.in-addr.arpa (regular network)
1.168.192.in-addr.arpa (management)
2.168.192.in-addr.arpa (hyperv)
3.168.192.in-addr.arpa (nas)
The problem:
When the servers boot and request a DHCP address for each NIC they register those addresses with AD/DNS (even for the scopes that doesn't offer DNS)... this would be just fine if it wasn't for the fact that they register all addresses under the NIC1 scope, so that when I look at it I see 3 different IP addresses for the same host name...
i.e. > nslookup srv-01
Server: ad.co.net
Address: 192.168.0.10
Name: srv-01.co.net
Addresses: 192.168.1.10
192.168.2.10
192.168.3.10
Preferably I would only have it return the 1... as the other two really shouldn't be registered :( I have 2 other servers (2008R2 non-core) where I've configured the advanced IP settings to not register in DNS, but the core servers seem to do this by default... so for those servers I get one registration for each domain (co.net, hyperv.co.local and nas.co.local).
I've been looking at options in DHCP but those don't seem to help. How do I get the core servers to automatically register with the right DNS suffixes so that I would end up with
srv-01.co.net = 192.168.1.10
srv-01.hyperv.co.local = 192.168.2.10
srv-01.nas.co.local = 192.168.3.10
Is this understandable? Any suggestions without manually doing a lot of point and click which won't work on the core server anyways? :D
If this is the wrong forum feel free to move or point me around, but I seemed to find several related questions here - but no real comparable solutions...