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.

Thank you in advance
jplatt1Asked:
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

x
 
mooodiecrConnect With a Mentor Commented:
you also might want to try and look at DNS itself.  Does DNS look correct?  Many times I have had to perform the following:

ipconfig /flushdns
ipconfig /registerdns
net stop netlogon
net start netlogon

I have also gone as far as deleting the Primary zone in DNS as the zone itself became corrupted.  

Something else you can try is to run an nslookup and verify that it reads the name/domain correctly.  If not you can blow out the reverse zone and recreate.
0
 
Darius GhassemConnect With a Mentor Commented:
Would not be a possible fix or cause issues when you run adprep.

Can you explain a little more in server not showing dns suffix? Post ipconfig /all
0
 
NavdeepConnect With a Mentor Commented:
Hi,

It seems like you are taking about single label name space. In fact the article mentions about 888048.
You can take system state backup prior to making any changes.

You need to follow those steps on the single label host i.e. the DC which doesn't have a primary suffix.

Also can you post netdiag and dcdiag ouput.

Upgrading AD to Windows 2008 R2 will  not fix the issue that Your 2003 DC is facing. In Server 2008 Single label name space is supported though it's not recommended not it's not a best practice do so.
0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

 
jplatt1Author Commented:
Ok Folks,
                 Thank you for the responses. I will collect the data you have asked for and get post ASAP.
0
 
jplatt1Author Commented:
Ok,
      Tried DNS flush and rereg, that did not work. got the ipconfig all, i stared out the actual mac.
Windows IP Configuration



   Host Name . . . . . . . . . . . . : SERVER

   Primary Dns Suffix  . . . . . . . :

   Node Type . . . . . . . . . . . . : Unknown

   IP Routing Enabled. . . . . . . . : No

   WINS Proxy Enabled. . . . . . . . : Yes



Ethernet adapter Local Area Connection:



   Connection-specific DNS Suffix  . :

   Description . . . . . . . . . . . : Intel(R) PRO/1000 CT Network Connection

   Physical Address. . . . . . . . . : **-**-**-**-**-**

   DHCP Enabled. . . . . . . . . . . : No

   IP Address. . . . . . . . . . . . : 192.168.0.11

   Subnet Mask . . . . . . . . . . . : 255.255.255.0

   Default Gateway . . . . . . . . . : 192.168.0.1

   DNS Servers . . . . . . . . . . . : 192.168.0.11

   Primary WINS Server . . . . . . . : 192.168.0.11

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

         (GUID#._msdcs.domain.local) couldn't be

         resolved, the server name (SERVER) resolved to the IP address

         (192.168.0.11) and was pingable.  Check that the IP address is

         registered correctly with the DNS server.
         ......................... SERVER failed test Connectivity

Doing primary tests
   
   Testing server: Default-First-Site\SERVER
      Skipping all tests, because server SERVER is
      not responding to directory service requests
   
   Running partition tests on : TAPI3Directory
      Starting test: CrossRefValidation
         ......................... TAPI3Directory passed test CrossRefValidation
      Starting test: CheckSDRefDom
         ......................... TAPI3Directory passed test CheckSDRefDom
   
   Running partition tests on : ForestDnsZones
      Starting test: CrossRefValidation
         ......................... ForestDnsZones passed test CrossRefValidation
      Starting test: CheckSDRefDom
         ......................... ForestDnsZones passed test CheckSDRefDom
   
   Running partition tests on : DomainDnsZones
      Starting test: CrossRefValidation
         ......................... DomainDnsZones passed test CrossRefValidation
      Starting test: CheckSDRefDom
         ......................... DomainDnsZones passed test CheckSDRefDom
   
   Running partition tests on : Schema
      Starting test: CrossRefValidation
         ......................... Schema passed test CrossRefValidation
      Starting test: CheckSDRefDom
         ......................... Schema passed test CheckSDRefDom
   
   Running partition tests on : Configuration
      Starting test: CrossRefValidation
         ......................... Configuration passed test CrossRefValidation
      Starting test: CheckSDRefDom
         ......................... Configuration passed test CheckSDRefDom
   
   Running partition tests on : domain
      Starting test: CrossRefValidation
         ......................... domain passed test CrossRefValidation
      Starting test: CheckSDRefDom
         ......................... domain passed test CheckSDRefDom
   
   Running enterprise tests on : domain.local
      Starting test: Intersite
         ......................... domain.local passed test Intersite
      Starting test: FsmoCheck
         ......................... domain.local passed test FsmoCheck
---------------------------------------------------------------------------------------------------------------------------------------------------

Thanks
0
 
NavdeepConnect With a Mentor Commented:
Hi,

Follow the KB article that KB888048
0
 
jplatt1Author Commented:
Alright,

If no one else has anything tho add, I will give the article a go as is. Thanks everyone for your input and I will let you know how it turns out.
0
 
Darius GhassemConnect With a Mentor Commented:
Well you have an issue with DNS.

You don't have a DNS suffix listed.

What is your domain name? Is the domain name like domain.com?
0
 
jplatt1Author Commented:
No, it is domain.local
0
 
Darius GhassemConnect With a Mentor Commented:
Well then you don't have a single label domain then.

Do you have a msdcs.domain.local zone? Is your msdcs folder grayed out under your domain.local zone?
0
 
mooodiecrConnect With a Mentor Commented:
Make sure that you have no firewalls or anything blocking port 53.  

reinstall an active Directory Integrated zone.  These articles further explain the process I previously mentioned.
http://www.howtonetworking.com/dns.htm
http://www.howtonetworking.com/dns.htm
http://exchangemaster.wordpress.com/2009/12/12/how-to-reinstall-a-dynamic-dns-active-directory-integrated-zone/

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.
0
 
xcomiiiConnect With a Mentor Commented:
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.
0
All Courses

From novice to tech pro — start learning today.