Configuring a service such as mail or web hosting to work with a domain name is a complex and difficult task for users. This is because most services require changes to the DNS settings associated with a domain, and users don’t understand DNS.
Domain Connect is a protocol that makes this easier for the user, and more consistent across providers.
A typical use case is as follows.
Often a customer will try to configure a service at a Service Provider by entering their domain name. The Service Provider then uses a number of techniques to discover the DNS Provider. This might include trying to figure out the registrar/DNS owner by doing DNS queries for the nameservers.
The Service Provider then maps the nameserver to a DNS Provider, and typically gives the customer instructions for proper configuration of DNS. This might include help text, screen shots, or even links to the appropriate tools.
This often presents a number of things to the user that they don’t understand. DNS record types, TTLs, HostNames, etc. are all confusing to many users. And the instructions authored by the Service Provider are often out of date, further confusing the issue.
Domain Connect was initially created by GoDaddy to solve this problem. After on boarding a number of Service Providers, they realized that turning this simple protocol into an open standard would help solve an industry wide problem. By implementing a standard interaction between all Service Providers and all DNS Providers, the customer is isolated from the details of DNS settings and complexity and it eliminates the need for each relationship between a Service Provider and DNS Provider to be customized.
After recruiting a number of Service Providers and DNS Providers, the initial versions of the standard were created.