mirror of https://github.com/StackExchange/dnscontrol.git synced 2025-02-25 16:13:04 +08:00

Brian Hartvigsen 156c684be6

Initial support for easyname as registrar (#1277 )

* Initial support for easyname as registrar

* DRY

Moving a bunch of the HTTP stuff into a single function for cleanliness and ease of future maintianence.

* Seperate API and Provider logic

* Updating error messages and sorting found nameservers

* Adding provider info to OWNERS and README

This also moves a few of the not-actually-DNS Providers to their own section.

* Update README.md

Co-authored-by: Tom Limoncelli <tlimoncelli@stackoverflow.com>

2021-10-04 13:01:38 -04:00

983 B

Raw Blame History

name	title	layout	jsId
easyname	easyname Provider	default	EASYNAME

easyname Provider

DNSControl's easyname provider supports being a Registrar. Support for being a DNS Provider is not included, but could be added in the future.

Configuration

In your credentials file, you must provide your API-Access information

{% highlight json %} { "easyname": { "userid": 12345, "email": "example@example.com", "apikey": "API Key", "authsalt": "API Authentication Salt", "signsalt": "API Signing Salt" } } {% endhighlight %}

Metadata

This provider does not recognize any special metadata fields unique to easyname.

Usage

Example Javascript:

{% highlight js %} var REG_EASYNAME = NewRegistrar('easyname', 'EASYNAME');

D("example.com", REG_EASYNAME, NAMESERVER("ns1.example.com."), NAMESERVER("ns2.example.com."), ); {% endhighlight %}

Activation

You must enable API-Access for your account.

983 B Raw Blame History