| Event Id | 414 |
| Source | Microsoft-Windows-DNS-Server-Service |
| Description | "The DNS server machine currently has no DNS domain name. Its DNS name is a single label hostname with no domain (example: "host" rather than "host.microsoft.com"). You might have forgotten to configure a primary DNS domain for the server computer. While the DNS server has only a single label name, all zones created will have default records (SOA and NS) created using only this single label name for the server's hostname. This can lead to incorrect and failed referrals when clients and other DNS servers use these records to locate this server by name. To correct this problem: 1) open Control Panel 2) open System applet 3) select Computer Name tab 4) click the "Change" button and join the computer to a domain or workgroup; this name will be used as your DNS domain name 5) reboot to initialize with new domain name After reboot, the DNS server will attempt to fix up default records, substituting new DNS name of this server, for old single label name. However, you should review to make sure zone's SOA and NS records now properly use correct domain name of this server. " |
| Event Information | According to Microsoft : Cause : This event is logged when DNS server machine currently has no DNS domain name. Resolution : Give the DNS server a fully qualified domain name The DNS server must be configured with a fully qualified domain name (FQDN) to function properly. This computer is configured with a single-label name. To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority. To give the DNS server an FQDN: 1.On the DNS server, start Server Manager. To start Server Manager, click Start, click Administrative Tools, and then click Server Manager. 2.Click Change system properties. 3.On the Computer Name tab, click Change. 4.In Computer Name/Domain Changes, click More. 5.In Primary DNS Suffix of this computer, type the primary Domain Name System (DNS) suffix of the computer (the part of the computer's FQDN that follows the host name), and then click OK. 6.Click OK, and then click Close to close all the dialog boxes. 7.Restart the computer to allow the changes to take effect. To restart the computer, click Start, click the arrow next to the Lock button, and then click Restart. After the computer restarts, the DNS server attempts to fix default records, substituting the new DNS name of this server for the single-label name. However, ensure that each zone's start of authority (SOA) and name server (NS) resource records now use the correct domain name of this server. To view the start of authority (SOA) and name server (NS) resource records: 1.On the DNS server, start Server Manager. To start Server Manager, click Start, click Administrative Tools, and then click Server Manager. 2.In the console tree, double-click Roles, double-click DNS Server, and then double-click DNS. 3.For each zone, expand the zone folder that contains the zone, expand the zone, and then click Properties. 4.To view the start of authority (SOA) resource records, click the Start of Authority (SOA) tab. 5.To view the name server (NS) resource records, click the Name Servers tab. Instead of directly specifying the primary DNS suffix, you can join the computer to a Windows domain. The DNS name of the Windows domain is then used as the primary DNS suffix of the server's name. Verify To verify that the Domain Name System (DNS) configuration is correct, verify that all configuration settings are correct, check the event log for events that indicate continuing problems, and then verify that DNS client computers are able to resolve names properly. To verify DNS configuration settings: 1.On the DNS server, start Server Manager. To start Server Manager, click Start, click Administrative Tools, and then click Server Manager. 2.In the console tree, double-click Roles, double-click DNS Server, and then double-click DNS. 3.Right-click the DNS server, and then click Properties. 4.Review the settings on each tab, and verify that they contain the intended values. 5.Expand the DNS server. 6.Expand a zone folder, right-click a zone, and then click Properties. 7.Review the settings on each tab, and verify that they contain the intended values. 8.Repeat steps 6 and 7 for each zone. To verify that DNS client computers can resolve names properly: 1.On a DNS client computer, open a command prompt. To open a command prompt, click Start, click Run, type cmd, and then click OK. 2. At the command prompt, type pinghostname (where hostname is the DNS name of a computer with a known IP address), and then press ENTER. If the client can resolve the name, the ping command responds with the following message: Pinging hostname [ip_address] Note: The name resolution is successful even if the ping command reports that the destination is unreachable. If the client cannot resolve the name, the ping command responds with the following message: Ping request could not find host hostname |
| Reference Links | Event ID 414 from Microsoft-Windows-DNS-Server-Service |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.