DNS Error in Event Viewer

Posted on 2005-03-27
Medium Priority
Last Modified: 2011-09-20

Ok I have a client running W2K Server, with an Exchange Server 2003 install.. all the clients seem to be working fine, internal and external mail is able to send and receive just fine. When I check the Event Viewer all seems ok, except for this one thing.. it looks like every 20 seconds or so a message much like this comes up.

"Registration of the DNS record '_ldap._tcp.pdc._msdcs.westonconsulting.com. 600 IN SRV 0 100 389 ibmserv.westonconsulting.com.' failed with the following error:
DNS server unable to interpret format."

The DNS seems to be working correctly as all the machines are resolving correctly. Plus I'm told that Exchange server is pretty picky about DNS working correctly..... these are the only messages that show up in the event viewer..and I'd love to track down the source and stop them if possible.. I realize it's not hurting anything (as far as I can tell) but it is bugging me :-)

Any ideas?


Question by:LimestoneData
  • 3
  • 3

Author Comment

ID: 13641210
OH sorry.. I should mention this is not the only error, I mean there are a number of messages that all sort of follow the same format... all relating to dns entries I have never seen or heard of before.

LVL 40

Expert Comment

ID: 13641226
Try verifying DNS registration of your DC..  you can use Nslookup for this per:


I would also suggest running some tests on your DNS server...  Netdiag and DNSLint are two that I prefer..


Author Comment

ID: 13641589

Thanks for the reply.. to be quite honest with you I"m not sure what the tests listed are
supposed to do... but I do notice something that I"m not sure is correct or not.

The server has it's IP assigned as static. When I check the TCP/IP properties I notice
that in the DNS servers field it's actually pointing to the DSL router's IP address.. so
when I do anything with nslookup it automatically looks to the ISP DNS server..

If this server is supposed to be acting as the Domain's DNS server should it be pointing
to an external DNS server like that? More importantly if not, what should it say there?
I guess even more importantly, would chaning that muck up the email which is working
so well right now? I really hesitate to play around too much as the whole sytem is
working so well other than those entires in the event viewer...

I look forward to your reply.

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

LVL 40

Accepted Solution

Fatal_Exception earned 1000 total points
ID: 13643157
No.  When you are running internal DNS, everything should be pointing to that server for DNS resolution, and the DNS server should be using Forwarders to resolve to external Name Resolution.  Now, I don't see that changing it to the proper setting would hurt you, but I think you need to read through this article and ck your DNS server's settings also..


I assume your clients all have the internal DNS server listed as their primary DNS server, and that the proper records for your Exchange SErver are in your DNS server's configuration (MX, A)...


Author Comment

ID: 13643352
Hi Fatal_exception,

Thanks for all the great info... I re-pointed the exchange server and local machine TCP settings to
the internal DNS server and poof all the errors have stopped in the event viewer. So clearly the
issue was in some way related to how those machines were trying to poll an outside DNS

Yes all the clients were and are pointing to the Internal DNS server.

The proper records A and MX are configured for the exchange server with the ISP DNS server
so that outside people can send mail to us... are you saying that the A and MX records for
the Exchange server need to be configured in the internal domain DNS server as well?

I have gone to the article you posted and it has a ton of info and good links I will be reading
through it for the next couple of days :-)

I am going to just give you points now as your answer of re-pointing to the interna DNS
box was the one that took at the error messages that I originally wrote about.

Thanks very much.

LVL 40

Expert Comment

ID: 13644086
Very good.  Since your errors have disappeared, then I would suggest we take the "if it is not broke, don't fix it" attitude.  

Have a great week!  and thank you!


Featured Post

Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Nslookup is a command line driven utility supplied as part of most Windows operating systems that can reveal information related to domain names and the Internet Protocol (IP) addresses associated with them. In simple terms, it is a tool that can …
Many of us in IT utilize a combination of roaming profiles and folder redirection to ensure user information carries over from one workstation to another; in my environment, it was to enable virtualization without needing a separate desktop for each…
Michael from AdRem Software explains how to view the most utilized and worst performing nodes in your network, by accessing the Top Charts view in NetCrunch network monitor (https://www.adremsoft.com/). Top Charts is a view in which you can set seve…
Is your OST file inaccessible, Need to transfer OST file from one computer to another? Want to convert OST file to PST? If the answer to any of the above question is yes, then look no further. With the help of Stellar OST to PST Converter, you can e…

569 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question