This is a continuation of a thread that was 'mistakenly' marked as answered - http://social.technet.microsoft.com/Forums/en-US/winservergen/thread/353d381d-0911-41c3-98fb-2475b65c32f6 Basically, we have 2008 R2 domain controllers that are trying to create a secure connection to servers listed in the 'forwarders' section of the DNS server properties. Of course, this connection attempt fails causing warning messages in event viewer. Hopefully, this will get more attention from the gurus and MVP's than the last thread...

Hi, Could you please describe the issue in more details? What kind of secure connection it is trying to create? What warning messages you get in event viewer? Best Regards Scott Xie

<see below> Note: The 208.67.220.220 address is OpenDNS which I use for my DNS forwarder. Log Name: System Source: Microsoft-Windows-DistributedCOM Date: 7/14/2012 10:46:40 AM Event ID: 10009 Task Category: None Level: Error Keywords: Classic User: N/A Computer: DC.[domain].com Description: DCOM was unable to communicate with the computer 208.67.220.220 using any of the configured protocols. Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Microsoft-Windows-DistributedCOM" Guid="{1B562E86-B7AA-4131-BADC-B6F3A001407E}" EventSourceName="DCOM" /> <EventID Qualifiers="49152">10009</EventID> <Version>0</Version> <Level>2</Level> <Task>0</Task> <Opcode>0</Opcode> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2012-07-14T14:46:40.000000000Z" /> <EventRecordID>24337</EventRecordID> <Correlation /> <Execution ProcessID="0" ThreadID="0" /> <Channel>System</Channel> <Computer>DC.[domain].com</Computer> <Security /> </System> <EventData> <Data Name="param1">208.67.220.220</Data> <Binary>3C5265636F726423313A20436F6D70757465723D286E756C6C293B5069643D3639323B372F31342F323031322031343A34363A34303A3339383B5374617475733D313732323B47656E636F6D703D323B4465746C6F633D313731303B466C6167733D303B506172616D733D313B7B506172616D23303A307D3E3C5265636F726423323A20436F6D70757465723D286E756C6C293B5069643D3639323B372F31342F323031322031343A34363A34303A3339383B5374617475733D313732323B47656E636F6D703D31383B4465746C6F633D313434323B466C6167733D303B506172616D733D313B7B506172616D23303A3230382E36372E3232302E3232307D3E3C5265636F726423333A20436F6D70757465723D286E756C6C293B5069643D3639323B372F31342F323031322031343A34363A34303A3339383B5374617475733D313732323B47656E636F6D703D31383B4465746C6F633D3332333B466C6167733D303B506172616D733D303B3E3C5265636F726423343A20436F6D70757465723D286E756C6C293B5069643D3639323B372F31342F323031322031343A34363A34303A3339383B5374617475733D313233373B47656E636F6D703D31383B4465746C6F633D3331333B466C6167733D303B506172616D733D303B3E3C5265636F726423353A20436F6D70757465723D286E756C6C293B5069643D3639323B372F31342F323031322031343A34363A34303A3339383B5374617475733D31303036303B47656E636F6D703D31383B4465746C6F633D3331313B466C6167733D303B506172616D733D333B7B506172616D23303A3133357D7B506172616D23313A307D7B506172616D23323A3078646364633433643030303030303030307D3E3C5265636F726423363A20436F6D70757465723D286E756C6C293B5069643D3639323B372F31342F323031322031343A34363A34303A3339383B5374617475733D31303036303B47656E636F6D703D31383B4465746C6F633D3331383B466C6167733D303B506172616D733D303B3E</Binary> </EventData> </Event>

Hi, Error with Event ID 10009 is a known issue. Please refer similar kind of thread http://social.technet.microsoft.com/Forums/en-US/winservergen/thread/fff393bb-ff8b-4523-831d-c95bf8f1cb36/ Regards, Ravikumar P

Sorry, maybe I should have been more specific... The question is not "Why am I getting EventID 10009?", or "How do I fix EventID 10009?". The unanswered question posed by several people in the previous thread is WHY is my DNS server trying to create this connection with an EXTERNAL system listed in my DNS forwarder section?

Hi Alceryes, To figure out why your DNS server always tries to create the connection to the server listed in DNS forwarder, I suggest that you can capture network trace on the DNS server when the event occurs. Then check what process is connecting the server 208.67.220.220 at that time point. Best Regards Scott Xie