Server Core Wont Register DNS / Other DNS Client Issues
-
Saturday, May 05, 2012 1:24 AM
Installed 2008 R2 Server Core, made the modifications I need and attached it to my domain, however it will not register it's IPs with DNS.
Symtoms/Results of this:
-
Produces the following EventID: 1014 (Source: DNS Client Events) during bootup, "Name resolution for the name <The AD Domain Here> timed out after none of the configured DNS servers responded." Contrary to this, the server can actually ping the domain name.
-
When attempting to use several of these setups in a failover cluster I get many DNS related issues.
Attempts to repair that have no results:
- network driver updates
- no windows updates after install (bare bones)
- only using a single Broadcom NIC instead of multiples
- disabling offloads, etc
- DNS does not register regardless to which domain I attach it to (a 2k3 AD setup as well as a 2k8 setup).
What actually works:
- When I don't use Server Core. Full install has no issues.
Has anybody else run into this? -
All Replies
-
Monday, May 07, 2012 5:01 AMModerator
Hi TKiel,
Thanks for posting here.
So do we have any name resolution issue with current configurations ? what if we perform “nslookup <domain name>”, will this DNS server that it is pointing and using new responds results it has ?
I assume we’ve assigned static network settings for this host, so what about DNS suffix ? and what if we manually registry it by command “ipconfig /registerdns”.Could you also show us the result of command “netsh interface ipv4 show dnsservers” here ?
http://technet.microsoft.com/en-us/library/cc731521(WS.10).aspx#BKMK_showdnsservers
Regards,
Tiger Li
TechNet Subscriber Support in forum
If you have any feedback on our support, please contact tnmff@microsoft.com.
Tiger Li
TechNet Community Support
-
Monday, May 07, 2012 5:33 PMI can ping, nslookup, etc without an issue. I can also ping the active directory domain itself (which it reports in the event during bootup as timing out). If I run 'ipconfig /registerdns' I get no event logs suggesting failure, however the host (A) records are never created in my AD dns. The other symptom was host name lookups when failover clustering.
-
Wednesday, May 09, 2012 2:50 AMModerator
Hi TKiel,
Thanks for update.
Since this is a single-homed host then have we band multiple IP addresses ? could you show us the current network settings?
What if we don’t set it as a node of cluster system but a simple domain joined host and will get DNS record properly updated ?
So far, I’d suggest to recheck our current settings and try to reconfigure the cluster with following the steps in the guide below and see how is going
Configure Failover Clustering on Windows Server 2008 R2 Server Core
Regards,
Tiger Li
TechNet Subscriber Support in forum
If you have any feedback on our support, please contact tnmff@microsoft.com.
Tiger Li
TechNet Community Support
- Marked As Answer by Tiger LiModerator Monday, May 14, 2012 12:47 AM
-
Thursday, May 10, 2012 9:37 AMModerator
Hi TKiel,
If there is any update on this issue, please feel free to let us know.
Regards,
Tiger Li
TechNet Subscriber Support in forum
If you have any feedback on our support, please contact tnmff@microsoft.com.Tiger Li
TechNet Community Support

