CloudFest Hackathon

On March 23rd through March 25th Domain Connect participated in the CloudFest Hackathon.

Our team implemented a library that implements the Domain Connect protocol for DNS Providers. Using this, we protoptyped implementations on top of PowerDNS, cPanel, and Bind.

This library fills a huge gap in gaining adoption. We’ve had great sample code for Service Providers for a couple of years, but no sample code to help the DNS Providers.

This library solves the harder problems of Domain Connect. This includes verification of signatures, processing variables into templates, and applying the template to an existing zone and dealing with conflict resolution.

The DNS Provider still needs to implement elements of the protocol the flow, including gaining consent, verification of domain ownership, and handling of redirects and UX flow. The DNS Provide also needs to read and write the actual zone contents. But the library handles some of the more difficult challenges DNS Providers face.

The results of our work can be found at

Domain Connect at CloudFest

Meet Domain Connect during the CloudFest – Hackathon and Panel Discussion.

This will be the third year Domain Connect has participated in the Hackathon. This year again it would show its presence with a new project “Domain Connect DNS Provider”. The goal is to build a DNS-Provider on top of standard open source DNS projects (PowerDNS or BIND). Results will be presented on Tuesday at 10am NameStudio™ API Main Forum Ballsaal Berlin.

Also, don’t miss the opportunity to hear about current developments, experiences and opinions in the Panel Discussion on Wednesday, with Arnold Blinn (GoDaddy), Pawel Kowalik ( 1&1 IONOS), Jan Löffler ( Plesk) and Kellie Peterson ( Automattic) on Wednesday at 3:35pm in NameStudio™ API Main Forum Ballsaal Berlin. See you there!

Spec Updates: Dectecting TXT Record Conflicts

We tempted fate at ICANN. A few of us were chatting about how we haven’t had a spec update in months.

Naturally we all came home and something came up.

We’ve always known that detecting conflicts in TXT records was a bit optimistic. The specification had indicated that adding a TXT record should not detect conflicts with existing TXT records. But we got some feedback that this behavior wasn’t always desired.

As such, we’ve added some simple rules around how conflicts in TXT records should be seen. There are three possible settings for a new value called “txtConflictMatchingMode” as an attribute of a TXT record in a template.

None: This is the default value, and is the existing behavior. With this setting, a template would behave as it always has.

All: This value indicates that existing values should be detected as conflicts.

Prefix: This value indicates that existing values with the same prefix (specified in another attribute txtConfictMatchingPrefix).

For detail section 6.2 of the specification.

Domain Connect @ ICANN Barcelona

Domain Connect has been around for a couple of years, but we had a coming out part at ICANN in Barcelona during the week of October 21st 2018.

Several DNS Providers (1&1 and GoDaddy) along with Service Providers (Google, Microsoft, and WPEngine) were present. We were also had help from Hubspot and from the Domain Name Association (DNA).

Our goal was to make sure people knew what Domain Connect was and how it helps the industry. To that end the event was highly successful. The most common reaction was “this makes a ton of sense”. We shared several case studies (links will be shared from here in the next couple of weeks) outlining the benefits to Service Providers, DNS Providers, and of course Consumers.


We’ve finally launched a blog as part of the Domain Connect website.

Domain Connect is over 4 years old. Those of us in the weeds have been working with different DNS Providers and Service Providers to define templates and onboard. This has resulted in some great new integrations, some great additions to the specification, and new capabilities for end users and the providers.

We now have multiple highly active companies contributing to the growth and evolution of the specification and service. Yet we have no easy way for to make make annoucements or celebrate victories.

We’ll see how it goes. We can always remove the blog…