asked on Windows Server 2012
Hi,
I have a new 2012 server and 4 new Windows 8 Pro workstations in a new domain. Every day since we went live the network drops out locally and on the internet. I have the the following configuration:
Netgear DGN2200 ADSL router plugged into a Netgear Gigabyte switch.
The server and the 4 PC's plug into the switch.
Router: 192.168.5.1
Internet Port
MAC Address E0:46:9A:63:85:78
IP Address 149.135.2.241
Network Type PPPoA
IP Subnet Mask 255.255.255.255
Gateway IP Address 165.228.7.1
Domain Name Server
203.50.2.71
139.130.4.4
2012 Server:
IP: 192.168.5.10
SUB: 255.255.255.0
GW: 192.168.5.1
DNS1: 192.168.5.1
DNS2: 192.168.5.10
I have given all the PC's static IP addresses with the following config: (with different IP's)
IPv4 Address. . . . . . . . . . . : 192.168.5.32(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.5.1
DNS Servers . . . . . . . . . . . : 192.168.5.10
DNS 192.168.5.1
NetBIOS over Tcpip. . . . . . . . : Enabled
I ran the BPA analyzer on the server and got these results:
CC-SERVER Error DNS: The DNS server 192.168.5.1 on Ethernet 2 must resolve Global Catalog resource records for the domain controller Configuration
CC-SERVER Error This domain controller must register its DNS host A/AAAA records Configuration
CC-SERVER Error This domain controller must advertise as a PDC for the domain Configuration
CC-SERVER Error This domain controller must advertise itself as a generic global catalog server for the forest Configuration
CC-SERVER Error This global catalog server must register its host (A/AAAA) resource records for the forest Configuration
CC-SERVER Error This domain controller must advertise as the global catalog server for the forest Configuration
CC-SERVER Error This domain controller must register its Rfc1510UdpKpwd DNS record to advertise itself as Kerberos Server for the domain Configuration
CC-SERVER Error This domain controller must register its Rfc1510Kpwd DNS record to advertise itself as Kerberos Server for the domain Configuration
CC-SERVER Error This domain controller must register an alias (CNAME) resource record with its DsaGuid for the forest Configuration
CC-SERVER Error This domain controller must register its Rfc1510UdpKdc DNS record to advertise itself as Kerberos Server for the domain Configuration
CC-SERVER Error This domain controller must register its Rfc1510Kdc DNS record to advertise itself as Kerberos Server for the domain Configuration
CC-SERVER Error This server must advertise itself as a domain controller for the domain Configuration
CC-SERVER Error This domain controller must advertise as a KDC for the domain Configuration
CC-SERVER Error The PDC emulator master CC-SERVER.Cleveland.local in this forest should be configured to correctly synchronize time from a valid time source Configuration
CC-SERVER Error This domain controller must register a DNS SRV resource record, which is required for replication to function correctly Configuration
CC-SERVER Error This domain controller must register its DNS host (A or AAAA) resource records for the domain Configuration
CC-SERVER Error This domain controller must advertise as a global catalog server for the forest in its local site Configuration
CC-SERVER Error This domain controller must advertise itself as a generic global catalog server for the forest in its local site Configuration
CC-SERVER Error This domain controller must advertise itself as a Kerberos server for the domain in its local site Configuration
CC-SERVER Error This server must advertise itself as a domain controller for the domain in its local site Configuration
CC-SERVER Error This domain controller must advertise as a KDC for the domain in its local site Configuration
CC-SERVER Error This domain controller must advertise as an LDAP server for the domain in its local site Configuration
CC-SERVER Error DNS: The DNS server 192.168.5.1 on Ethernet 2 must resolve names in the primary DNS domain zone Configuration
CC-SERVER Error DNS: The DNS server 192.168.5.1 on Ethernet 2 must resolve names in the forest root domain name zone Configuration
CC-SERVER Error DNS: The DNS server 192.168.5.1 on the Ethernet 2 must resolve PDC resource records for the domain controller Configuration
CC-SERVER Error DNS: The DNS server 192.168.5.1 on Ethernet 2 must resolve LDAP resource records for the domain controller Configuration
CC-SERVER Error DNS: The DNS server 192.168.5.1 on Ethernet 2 must resolve Kerberos resource records for the domain controller Configuration
CC-SERVER Error This domain controller must advertise as an LDAP server for the domain Configuration
CC-SERVER Error DHCP: The server database should be functional and free of errors. Operation
When I setup the server I just did the default settings.
Do I need to add stuff to DNS
The server keeps changing from Domain to Public
I have also turned DHCP off on the server.
If I restart the router, switch, server and workstations it comes right.
If I haven't set the server correctly up can anyone give me some pointers
Thanks
Andrew
I have a new 2012 server and 4 new Windows 8 Pro workstations in a new domain. Every day since we went live the network drops out locally and on the internet. I have the the following configuration:
Netgear DGN2200 ADSL router plugged into a Netgear Gigabyte switch.
The server and the 4 PC's plug into the switch.
Router: 192.168.5.1
Internet Port
MAC Address E0:46:9A:63:85:78
IP Address 149.135.2.241
Network Type PPPoA
IP Subnet Mask 255.255.255.255
Gateway IP Address 165.228.7.1
Domain Name Server
203.50.2.71
139.130.4.4
2012 Server:
IP: 192.168.5.10
SUB: 255.255.255.0
GW: 192.168.5.1
DNS1: 192.168.5.1
DNS2: 192.168.5.10
I have given all the PC's static IP addresses with the following config: (with different IP's)
IPv4 Address. . . . . . . . . . . : 192.168.5.32(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.5.1
DNS Servers . . . . . . . . . . . : 192.168.5.10
DNS 192.168.5.1
NetBIOS over Tcpip. . . . . . . . : Enabled
I ran the BPA analyzer on the server and got these results:
CC-SERVER Error DNS: The DNS server 192.168.5.1 on Ethernet 2 must resolve Global Catalog resource records for the domain controller Configuration
CC-SERVER Error This domain controller must register its DNS host A/AAAA records Configuration
CC-SERVER Error This domain controller must advertise as a PDC for the domain Configuration
CC-SERVER Error This domain controller must advertise itself as a generic global catalog server for the forest Configuration
CC-SERVER Error This global catalog server must register its host (A/AAAA) resource records for the forest Configuration
CC-SERVER Error This domain controller must advertise as the global catalog server for the forest Configuration
CC-SERVER Error This domain controller must register its Rfc1510UdpKpwd DNS record to advertise itself as Kerberos Server for the domain Configuration
CC-SERVER Error This domain controller must register its Rfc1510Kpwd DNS record to advertise itself as Kerberos Server for the domain Configuration
CC-SERVER Error This domain controller must register an alias (CNAME) resource record with its DsaGuid for the forest Configuration
CC-SERVER Error This domain controller must register its Rfc1510UdpKdc DNS record to advertise itself as Kerberos Server for the domain Configuration
CC-SERVER Error This domain controller must register its Rfc1510Kdc DNS record to advertise itself as Kerberos Server for the domain Configuration
CC-SERVER Error This server must advertise itself as a domain controller for the domain Configuration
CC-SERVER Error This domain controller must advertise as a KDC for the domain Configuration
CC-SERVER Error The PDC emulator master CC-SERVER.Cleveland.local in this forest should be configured to correctly synchronize time from a valid time source Configuration
CC-SERVER Error This domain controller must register a DNS SRV resource record, which is required for replication to function correctly Configuration
CC-SERVER Error This domain controller must register its DNS host (A or AAAA) resource records for the domain Configuration
CC-SERVER Error This domain controller must advertise as a global catalog server for the forest in its local site Configuration
CC-SERVER Error This domain controller must advertise itself as a generic global catalog server for the forest in its local site Configuration
CC-SERVER Error This domain controller must advertise itself as a Kerberos server for the domain in its local site Configuration
CC-SERVER Error This server must advertise itself as a domain controller for the domain in its local site Configuration
CC-SERVER Error This domain controller must advertise as a KDC for the domain in its local site Configuration
CC-SERVER Error This domain controller must advertise as an LDAP server for the domain in its local site Configuration
CC-SERVER Error DNS: The DNS server 192.168.5.1 on Ethernet 2 must resolve names in the primary DNS domain zone Configuration
CC-SERVER Error DNS: The DNS server 192.168.5.1 on Ethernet 2 must resolve names in the forest root domain name zone Configuration
CC-SERVER Error DNS: The DNS server 192.168.5.1 on the Ethernet 2 must resolve PDC resource records for the domain controller Configuration
CC-SERVER Error DNS: The DNS server 192.168.5.1 on Ethernet 2 must resolve LDAP resource records for the domain controller Configuration
CC-SERVER Error DNS: The DNS server 192.168.5.1 on Ethernet 2 must resolve Kerberos resource records for the domain controller Configuration
CC-SERVER Error This domain controller must advertise as an LDAP server for the domain Configuration
CC-SERVER Error DHCP: The server database should be functional and free of errors. Operation
When I setup the server I just did the default settings.
Do I need to add stuff to DNS
The server keeps changing from Domain to Public
I have also turned DHCP off on the server.
If I restart the router, switch, server and workstations it comes right.
If I haven't set the server correctly up can anyone give me some pointers
Thanks
Andrew
Windows Server 2012Active DirectoryDNS
Last Comment
Philip Elder
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
Hi!
Happy New year!
The possible source of problems is that the DNS server for the domain controller (DC) and computers should be the one running on the DC.
The config above appears to be using the DNS supplied by the router.
Set all the machines to use the DC as DNS, including the DC.
The DNS server on the DC should already know all teh info the errors are indicating are not available from the Router DNS.
Once this is working, you set up the DNS server on teh DC to forward DNS requests to the router DNS for addresses external to your network.
Cheers!
TRM
Happy New year!
The possible source of problems is that the DNS server for the domain controller (DC) and computers should be the one running on the DC.
The config above appears to be using the DNS supplied by the router.
Set all the machines to use the DC as DNS, including the DC.
The DNS server on the DC should already know all teh info the errors are indicating are not available from the Router DNS.
Once this is working, you set up the DNS server on teh DC to forward DNS requests to the router DNS for addresses external to your network.
Cheers!
TRM
ASKER
Hi Phillip,
Can you give me some instructions on how to setup the forwarders in DNS
Thanks
Andrew
Can you give me some instructions on how to setup the forwarders in DNS
Thanks
Andrew
As has been said - the ONLY DNS server listed should be that of the Windows Server - any other configuration will cause internal name resolution to fail.
to set up forwarders see http://technet.microsoft.com/en-us/library/cc754941.aspx
to set up forwarders see http://technet.microsoft.com/en-us/library/cc754941.aspx
Start --> DNSMgmt.msc [CTRL + ENTER}
Click on SERVERNAME
Right click and Properties.
Forwarders tab.
Make sure "Use root hints if no forwarders are available" is checked.
Click EDIT button.
Enter the DNS server IP addresses there.
Click OK and OK.
We do this because the Root Hints cache bug has not been fixed since Server 2008.
Note the IPs are for our own ISP up here.
![DNS Forwarder Setting]()
Philip
Click on SERVERNAME
Right click and Properties.
Forwarders tab.
Make sure "Use root hints if no forwarders are available" is checked.
Click EDIT button.
Enter the DNS server IP addresses there.
Click OK and OK.
We do this because the Root Hints cache bug has not been fixed since Server 2008.
Note the IPs are for our own ISP up here.
Philip
If you have only one Domain controller it should be the DNS server for the other machines and for itself.