Experts,\n\nI have almost got this figured out! Old info first followed by the new\ntidbit at the end. Running Windows Server 2003 SP1. Running about 10 small\npublic web sites on it. This is a single-server pointing to itself for DNS\nand running Active Directory. The AD zone is standard primary with "Secure\nand Non-secure" updates set to 'Yes'. All other zones (for the 10 small\npublic web sites) have dynamic updates turned "off". None of those have\nname servers pointing to my ISP. They do however use the Notify feature to\ntransfer to them a secondary zone. In DNS, under Forwarders, are the two IP\naddresses for my ISP's DNS server in question. They were also entered into\nthe properties of the Default Virtual SMTP Server so that Exchange running\non this box could do reverse lookups on the domains of incoming mail but I\nhave removed those. The event ID error below basically indicates my server\ncannot communicate with my ISP server. I can understand that problems\nsometimes happens, as my ISP is hosting my secondary zones for the 10 small\npublic web sites. But why is the server trying to communicate with it using\nDCOM? I would assume it would only try to communicate with it using\nstandard tcp over port 53 (zone transfer). I have been over every square\ninch of this server. DCdiag results also keep telling me I'm using the two\nISP's DNS servers mentioned but I could not see how/where I am doing that\nanywhere within the GUI. The Preferred and Alternate DNS servers for this\nserver points to itself under network properties. The one new thing I have\ndiscovered with the help of Ace/Kevin is that I do have a reverse one for my\nserver delegated to me by my ISP. Given that, what do I need to do with/in\nthis zone to make my server stop trying to register in it??\n\nEvent Type: Error\nEvent Source: DCOM\nEvent Category: None\nEvent ID: 10009\nDate: 12/2/2005\nTime: 8:35:30 AM\nUser: N/A\nComputer: EBIZ-GATE\nDescription:\nDCOM was unable to communicate with the computer <ISP DNS> using any of the\nconfigured protocols.