752e25471d
* Move the registrar features to a separate file * Prepare the testing framework * Roughed out functions * Fix up structs * WIP! * First tests pass * wip! * Flesh out remaining rTypes, get nameservers, etc * Fix TXT records * Clean up code * More cleanups. Fix CAA/SRV * Linting * Cleanups/linting * Fix CAA [more] and more cleanups * CSC does not like very long txt records * Use timer only when interactive * Disable CAA for now * Update docs * Remove debug printf * add go-isatty * cleanups
1.5 KiB
| name | title | layout | jsId |
|---|---|---|---|
| CSC Global | CSC Global Provider | default | CSCGLOBAL |
CSC Global Provider
DNSControl's CSC Global provider supports being a Registrar. Support for being a DNS Provider is not included, although CSC Global's API does provide for this so it could be implemented in the future.
NOTE: Experimental support for being a DNS Provider is available. However it is not recommended as updates take 5-7 minutes, and the next update is not permitted until the previous update is complete. Use it at your own risk. Consider it experimental and undocumented.
Configuration
To use this provider, add an entry to creds.json with TYPE set to CSCGLOBAL.
In your creds.json file, you must provide your API key and user/client token. You can optionally provide an comma separated list of email addresses to have CSC Global send updates to.
Example:
{
"cscglobal": {
"TYPE": "CSCGLOBAL",
"api-key": "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx",
"user-token": "yyyyyyyy-yyyy-yyyy-yyyy-yyyyyyyyyyyy",
"notification_emails": "test@exmaple.tld,hostmaster@example.tld"
}
}
Usage
An example dnsconfig.js configuration:
var REG_CSCGLOBAL = NewRegistrar("cscglobal");
var DSP_BIND = NewDnsProvider("bind");
D("example.tld", REG_CSCGLOBAL, DnsProvider(DSP_BIND),
A("test", "1.2.3.4")
);
Activation
To get access to the CSC Global API contact your account manager.