Server 2003 AD DNS error 414

Hello Folks,
I have inherited a single server AD domain network. This server obviously holds all roles including DNS and DHCP. The issue is the server name only shows as "server", there is no dns suffix appended to it. The domain seems to functioning correctly except for the dns error obviously for the domain controller.

I have read through Microsoft KB888048 and in checking the DOMAIN registry value it is indeed blank. I need to add a new 2008 R2 SP 1 DC to this enviroment. That of course entails updating the AD. My question is I could not decern if the fix in the article, which seems simple enough, can be ran on the PDC without causing a critical issue to the enviroment. Also, if I were to update the AD to support the 2008 R2 DC, if this could be a possible fix or because of the issue fail or cause a more serious issue to the enviroment.

I also have the dcdiag. I have changed the guid # to GUID# and the actual domain name to domain.

Domain Controller Diagnosis

Performing initial setup:
Done gathering initial info.

Doing initial required tests

Testing server: Default-First-Site\SERVER
Starting test: Connectivity
The host GUID#._msdcs.Etter.local could not be resolved to an
IP address. Check the DNS server, DHCP, server name, etc
Although the Guid DNS name

Also, do a nslookup command and see what is registered as your name server. You may need to create a reverse lookup zone for your server. If you perform an nslookup from another computer can it resolve the domain name domain.local to an IP address? Also make sure that in the TCP/IP properties it is pointing to itself as the DNS server.

You should check your host file (windows\System32\Drivers\etc) , it should NOT contain a line with "127.0.0.1 localhost", all other lines should also be commented out, since you are also running DNS server on the server.

Mapping Drives using Group policy preferences
Are you still using old scripts to map your network drives if so this article will show you how to get away for old scripts and move toward Group Policy Preference for mapping them.
First things f…

This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008.
Determine the location of the FSMO roles by lo…

This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles to another domain controller.
Log onto the new domain controller with a user account t…