0 pts.
 MsExchangeDSAccess event 2106 2105 — DNS probs?
Hi, I am having a problem with Exchange and would greatly appreciate any help. Outlook clients are getting the sync folders in the system tray and are froze out of Exchange. This occurs sometimes 2 or 3 times a day. A restart seems to clear things up temporarily. I have Server 2003 Standard with Exchange 2003 Enterprise. I am running this server as a domain controller and Exchange for calendar sharing. I know this is not a best practice but I don't know what the best thing to migrate over to another server 2003 I have. I am assuming this is a problem with DNS. I have the NIC card DNS setting pointing to itself. I have forwarders configured to my ISPs DNS servers. I have had this problem for months and I don't know what to do. If you need more info let me know. Thanks Here are the errors I get every 15 mins: Catergory: Topology Event Id: 2106 Process INETINFO.EXE (PID=1752). DSAccess failed to obtain DNS records for forest DC=hun,DC=example,DC=com. DNS Priority and Weight for the Global Catalog servers in this forest will be set to the default values 0 (priority) and 100 (weight). Catergory: Topology Event Id: 2105 Process INETINFO.EXE (PID=1752). DSAccess failed to obtain DNS records for domain hun.bmzlaw.com. DNS Priority and Weight for the Domain Controllers in this domain will be set to the default values 0 (priority) and 100 (weight).

Software/Hardware used:
ASKED: July 12, 2005  1:11 PM
UPDATED: July 15, 2005  11:38 AM

Answer Wiki:
Hi, try the netdiag command to see if your registration of the dc is correct. If there are any kind of failures with DNS Querys repeat the command with the /fix parameter to reregister your DNS - Records
Last Wiki Answer Submitted:  July 12, 2005  4:41 pm  by  Sinclair   0 pts.
All Answer Wiki Contributors:  Sinclair   0 pts.
To see all answers submitted to the Answer Wiki: View Answer History.


Discuss This Question:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _


 

It does not pass the DNS test with netdiag. The /fix command returns a FATAL failed to fix: DC DNS entry xxx.xxx.com on DNS server 10.10.0.28 failed. could not re-register . I don’t know what is setup wrong.. The server is for internal purposes and is not hosting anything on the net so it doesn’t need to be registered on any external DNS servers. I don’t care if I even have a DNS server I just want exchange to not freeze up clients.
I know I should have set up the domain with a .local but is with .com maybe this has something to do with it?
Should I setup DNS on a different server? Or would that make things more complicated? Any help would be great. Thanks
Alex

 0 pts.

 

It seems that you have to build th DNS Records for your Dc by manuell.

Look at this KB and check your environment.

http://support.microsoft.com/default.aspx?scid=kb;en-us;816587

How to verify that SRV DNS records have been created for a domain controller

How DNS Support for Active Directory Works.
http://www.microsoft.com/Resources/Documentation/windowsserv/2003/all/techref/en-us/w2k3tr_addns_how.asp

 0 pts.

 

I also get this warning:

Source: NETLOGON
Event ID: 5782

Dynamic registration or deregistration of one or more DNS records failed with the following error:
No DNS servers configured for local system.

 0 pts.