domain-connect / domainconnectddns-windows Goto Github PK

So I have a domain that has traditionally used Domain Connect to update it's external IP. And now I have a domain controller on that internal network, which uses that domain as it's domain. (This is a traditional way the Internet was expected to work: example.com on the Internet points to my location, host1.example.com is a machine at that network, etc.)

However, the problem I've hit is that the Domain Connect DDNS app won't let me set up Domain Connect again (saying "Domain does not support Domain Connect"), presumably because it's trying to talk to my local DNS provider instead of GoDaddy's. I added the _domainconnect CNAME on my internal DNS, but that didn't help.

So how do I get the public DNS updated when on a network with split brain DNS?

Hello,
I come back to you, because I still encounter a problem, it seems that my service is cut alone, when I consult the services I do not see this one as you mention it in the "documentation"

`Installing and Running the Service

To run as a Windows service, you need to run a cmd prompt as the System Administrator. Visit the directory where you unpacked the files, and run the command:

c:\windows\Microsoft.Net\Framework\v4.0.30319\InstallUtil.exe DomainConnectDDNSUpdate.exe

This will install the service instance.

Next set the service to start automatically. This can be done by typing Windows+R and typing in services.msc to run the Service Manager.

From the Service Manager find "Domain Connect DDDNS Update", right click, and select "Properties".

Click Start (to begin the service), and select "Automatic" as the Startup Type to have it start on boot.`

Hi, could you please confirm if the DomainConnectDDNSUpdate service is capable of running undates to the same domain provider with multiple sub-domains pointing to the same IP address?

My case use, 2x sub-domains have been created with IONOS, both configured with this utility to point to the same IP address, using the same install procedures.

The 1st sub-domain (A record) is now listed as using 'External Service - Dynamic DNS' - IP address is correct
The 2nd sub-domain (A record) is still listsed as using an IPv4 address - nothing else?

I'm trying to troubleshoot and determine if this multiple sub-domain to the same IP address functionality has been previously tested?