

This behavior brings down all other running virtual machines together with the host computer.

Go to kb/2744129 to find that update, where it states the supersedence in the documentation.

Update: As of October 9, 2012, the update has been superseded by 2744129. Get-NetAdapter | Set-DnsClientServerAddress -ServerAddresses "x.x.x.x","x.x.x.x" Then, there is the one-liner (I discuss finding the proper NetAdapter is other posts). Note how I feed in the multiple addresses, as list of individual comma separated strings. Set-DnsClientServerAddress -InterfaceAlias vEthernet* -ServerAddresses "x.x.x.x","x.x.x.x" Now, to set, just turn this around to the Set.

Not thinking that there would be a DnsClientServerAddress. Well, I have to say it took a while just to find the right cmdlets because I began at IPAddress or IPAdapter. Netsh interface ipv4 add dnsserver "Wired Ethernet Connection" x.x.x.x 2īeing an embracer of PowerShell and all the 2000+ new cmdlets in Windows Server I decided to figure out how to do this the PowerShell way. Netsh interface ipv4 add dnsserver "Wired Ethernet Connection" x.x.x.x 1 Netsh interface ipv4 add dnsserver "local area connection" x.x.x.x 2įor the Windows 8 Preview I simply adapted this: Netsh interface ipv4 add dnsserver "local area connection" x.x.x.x 1 I frequently use custom DNS settings in my lab environments to override the provided DHCP settings and use my own personal domain controllers.įor Server 2008 I used the following commands: Okay, the time has come, I can finally say “Server 2012”
