gatormoe1
11-20-2012, 01:54 PM
So I got a free copy of Win Server 12 from Dreamspark and I set up my own DNS, it worked fine last night but now it won't work and I have to use my own ISP's DNS and/or Google dns. I think I need to get a certificate for the server for it to keep working but I haven't tried hard enough to figure that out (not yet at least, I don't have the time today). I know I need to use the MMC but to my knowledge, Server2012 got rid of the MMC and I havent googled around enough to figure out what replaced it (or maybe I just haven't installed it yet?) Anyway, here are the errors I'm getting...
Here is the error on the DNS Server
The DNS server could not open socket for address xxx.xxx.xxx.xxx.
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.
Here is the AD DS errors
The DNS server could not open socket for address xxx.xxx.xxx.xxx
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.
Active Directory Web Services could not find a server certificate with the specified certificate name. A certificate is required to use SSL/TLS connections. To use SSL/TLS connections, verify that a valid server authentication certificate from a trusted Certificate Authority (CA) is installed on the machine.
Certificate name: *Domain server*
The DNS server could not bind a User Datagram Protocol (UDP) socket to xxx.xxx.xxx.xxx. The event data is the error code. Restart the DNS server or reboot your computer.
The DNS server could not bind a Transmission Control Protocol (TCP) socket to address xxx.xxx.xxx.xxx. 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.
Here is the error on the DNS Server
The DNS server could not open socket for address xxx.xxx.xxx.xxx.
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.
Here is the AD DS errors
The DNS server could not open socket for address xxx.xxx.xxx.xxx
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.
Active Directory Web Services could not find a server certificate with the specified certificate name. A certificate is required to use SSL/TLS connections. To use SSL/TLS connections, verify that a valid server authentication certificate from a trusted Certificate Authority (CA) is installed on the machine.
Certificate name: *Domain server*
The DNS server could not bind a User Datagram Protocol (UDP) socket to xxx.xxx.xxx.xxx. The event data is the error code. Restart the DNS server or reboot your computer.
The DNS server could not bind a Transmission Control Protocol (TCP) socket to address xxx.xxx.xxx.xxx. 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.