I am trying to set up a virtual network with a DNS server.
I perform the following steps.
1. Create a resource group.
2. Create a virtual network.
3. Create a Virtual Machine under the above virtual network.
4. RDP to the virtual machine and configure it to be a DNS server.
5. Within the management portal, assign the internal IP of the virtual machine to be the DNS server of the virtual network.
6. Restart the virtual machine
7. Run 'ipconfig /all' on the virtual machine
At this point, the DNS suffix shows as reddog.microsoft.com, which I assume is the placeholder when the DNS server fails to resolve the domain name. What am I doing incorrectly?
Windows IP Configuration
Host Name . . . . . . . . . . . . : ****
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : reddog.microsoft.com
Ethernet adapter Ethernet:
Connection-specific DNS Suffix . : reddog.microsoft.com
Description . . . . . . . . . . . : Microsoft Hyper-V Network Adapter
Physical Address. . . . . . . . . : 00-0D-3A-90-1E-86
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::794c:76af:b44a:5884%12(Preferred)
IPv4 Address. . . . . . . . . . . : 70.0.0.4(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Wednesday, January 6, 2016 6:10:45 AM
Lease Expires . . . . . . . . . . : Saturday, February 12, 2152 12:44:14 PM
Default Gateway . . . . . . . . . : 70.0.0.1
DHCP Server . . . . . . . . . . . : 168.63.129.16
DHCPv6 IAID . . . . . . . . . . . : 201329978
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1E-1E-63-0A-00-0D-3A-90-1E-86
DNS Servers . . . . . . . . . . . : 70.0.0.4
NetBIOS over Tcpip. . . . . . . . : Enabled
Tunnel adapter 6TO4 Adapter:
Connection-specific DNS Suffix . : reddog.microsoft.com
Description . . . . . . . . . . . : Microsoft 6to4 Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2002:4600:4::4600:4(Preferred)
Default Gateway . . . . . . . . . :
DHCPv6 IAID . . . . . . . . . . . : 385875968
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1E-1E-63-0A-00-0D-3A-90-1E-86
DNS Servers . . . . . . . . . . . : 70.0.0.4
NetBIOS over Tcpip. . . . . . . . : Disabled
Tunnel adapter Teredo Tunneling Pseudo-Interface:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2001:0:9d38:90d7:2801:4fe:b9ff:fffb(Preferred)
Link-local IPv6 Address . . . . . : fe80::2801:4fe:b9ff:fffb%15(Preferred)
Default Gateway . . . . . . . . . :
DHCPv6 IAID . . . . . . . . . . . : 402653184
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1E-1E-63-0A-00-0D-3A-90-1E-86
NetBIOS over Tcpip. . . . . . . . : Disabled
Tunnel adapter isatap.reddog.microsoft.com:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . : reddog.microsoft.com
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
I also see the following errors logged in my server manager.
1. ID 407 The DNS server could not bind a User Datagram Protocol (UDP) socket to 169.254.88.132. The event data is the error code. Restart the DNS server or reboot your computer.
2. ID 404 The DNS server could not bind a Transmission Control Protocol (TCP) socket to address 169.254.88.132. The event data is the error code. An IP address of 0.0.0.0 can indicate a valid "any address" configuration in which all
configured IP addresses on the computer are available for use.
Restart the DNS server or reboot the computer.
3. ID 408 The DNS server could not open socket for address 169.254.88.132.
Verify that this is a valid IP address for the server computer. If it is NOT valid use the Interfaces dialog under Server Properties in the DNS Manager to remove it from the list of IP interfaces. Then stop and restart the DNS server. (If this was
the only IP interface on this machine and the DNS server may not have started as a result of this error. In that case remove the DNS\Parameters\ ListenAddress value in the services section of the registry and restart.)
If this is a valid IP address for this machine, make sure that no other application (e.g. another DNS server) is running that would attempt to use the DNS port.
For more information, see "DNS server log reference" in the online Help.