What should you do?

Your company has a server named Server1 that runs Windows Server 2008 R2. Server1 runs the DHCP Server server role and the DNS Server server role. You also have a server named ServerCore that runs a Server Core installation of Windows Server 2008 R2. All computers are configured to use only Server1 for DNS resolution. The IP address of Server1 is 192.168.0.1. The network interface on all the computers is named LAN. Server1 is temporarily offline. A new DNS server named Server2 has been configured to use the IP address 192.168.0.254.
You need to configure ServerCore to use Server2 as the preferred DNS server and Server1 as the alternate DNS server.
What should you do?

Your company has a server named Server1 that runs Windows Server 2008 R2. Server1 runs the DHCP Server server role and the DNS Server server role. You also have a server named ServerCore that runs a Server Core installation of Windows Server 2008 R2. All computers are configured to use only Server1 for DNS resolution. The IP address of Server1 is 192.168.0.1. The network interface on all the computers is named LAN. Server1 is temporarily offline. A new DNS server named Server2 has been configured to use the IP address 192.168.0.254.
You need to configure ServerCore to use Server2 as the preferred DNS server and Server1 as the alternate DNS server.
What should you do?

A.
Run the netsh interface ipv4 add dnsserver “LAN” static 192.168.0.254 index=1 command.

B.
Run the netsh interface ipv4 set dnsserver “LAN” static 192.168.0.254 192.168.0.1 both command.

C.
Run the netsh interface ipv4 set dnsserver “LAN” static 192.168.0.254 primary command and the netsh interface ipv4 set dnsserver “LAN” static 192.168.0.1 both command.

D.
Run the netsh interface ipv4 set dnsserver “LAN” static 192.168.0.254 primary command and the netsh interface ipv4 add dnsserver “LAN” static 192.168.0.1 index=1 command.

Explanation:
So you�ve installed Windows Server 2008 Core, you don�t use DHCP and you want to get the thing on the network. I keep forgetting how to do this so I thought I�d create this post to help me remember!
I�m assuming that you�ve got as far as changing the administrator password and logging in. The next step is as easy as typing a few commands into the plain black window you see in front of you. For this example, let�s assume that we want the server to have the following network configuration:
HOSTNAME: win2008core
IP ADDRESS: 10.1.5.16
SUBNET MASK: 255.255.255.128
DEFAULT GATEWAY: 10.1.5.126
DNS SERVER: 10.10.20.6
DNS SERVER: 10.20.4.3
We first have to extract two pieces of information from the server. The current hostname and the index of the NIC that we want to configure.
The hostname can be acquired simply by entering the command:
hostname
This will return something like �WIN-87abac8chasa87? or something random like that. Make a note of the name returned as we�ll need it later.
Next enter the following command:
netsh interface ipv4 show interfaces
This will return an output a bit like the one below. The important thing though is getting the index (Idx) value for the interface that you�re interested in (3 in this case). By default this will probably be called �Local Area Connection�.
To setup the IP details for the interface just enter the following command:
netsh interface ipv4 set address name=”3″ source=static address=10.1.5.16 mask=255.255.255.128 gateway=10.1.5.126
To add the DNS servers to this interface, use the following commands:
netsh interface ipv4 add dnsserver name=”3″ address=10.10.20.6 index=1
netsh interface ipv4 add dnsserver name=”3″ address=10.20.4.3 index=2
Note that we incremented the index value in the second command.
That was quite easy really. All that remains is to rename the server. This is done with another simple command using the value that we obtained earlier:
netdom renamecomputer WIN-87abac8chasa87 /NewName:win2008core
All that you then need to do is reboot the server:
shutdown /r /t 0



Leave a Reply 0

Your email address will not be published. Required fields are marked *