[Example Service Home]  [Signature Tools]

Example Service Provider

This serice demonstrates a sample Domain Conect Service Provider.

The service hosts a website for a domain name that displays a custom message. Like many hosting SaaS providers, this service requires modifications to DNS in the form of an A Record. It also happens to store the custom message in DNS in a TXT record. This is rather clever, as it is using DNS as a distributed database. While we would not advocate this in a real world application, it allows for a simple example application that requires no state data.

The application also demonstrates two templates. The first template sets up DNS as described above. The second adds an additional CNAME, and requires signatures. Like all templates, these can be found on github.

Template 1

Template 2

Domain Connect works in one of two ways. One is synchronous and one is asynchronous using oauth.

Synchronous

For the synchronous protocol, we need the domain name, the optional host (subdomain), and the message. The subsequent page will detect the DNS Provider and provide links to apply the template.

Domain Name
Host (optional)
Message
 

Asynchronous

For the asynchronous protocol, we need the domain name and the hosts. These are the hosts (sub-domains) upon which the template can be applied programatically later. There is no message collected here, because this is input to the API later.

Hosts is a list of comma delimted host names. An empty value allows the root domain.

Example Parameters

Domain NameHostsValid fully qualified domain names for template application
foo.comfoo.com
foo.combarbar.foo.com
foo.combar1,bar2,foo.com|bar1.foo.com|bar2.foo.com

The subsequent pages will get permission, and then allow application of template1 or template2 on domain/host tuples via the API.

Domain Name
Host (optional)