github.com/teknogeek/dnscontrol/v2@v2.10.1-0.20200227202244-ae299b55ba42/docs/_providers/hexonet.md (about) 1 --- 2 name: HEXONET 3 title: HEXONET Provider 4 layout: default 5 jsId: HEXONET 6 --- 7 # HEXONET Provider 8 9 HEXONET is a leading developer and operator of domain names and DNS platforms. 10 Individual, service provider and registrars around the globe choose HEXONET for 11 domains and DNS because of our advanced technology, operational performance and 12 up-time, and most importantly for DNS expertise. DNSControl with HEXONET's DNS 13 marries DNS automation with an industry-leading DNS platform that supports DNSSEC, 14 PremiumDNS via Anycast Network, and nearly all of DNSControl's listed provider features. 15 16 ## Configuration 17 18 Please provide your HEXONET login data in your credentials file `creds.json` as follows: 19 20 {% highlight json %} 21 { 22 "hexonet": { 23 "apilogin": "your-hexonet-account-id", 24 "apipassword": "your-hexonet-account-password", 25 "apientity": "LIVE", // for the LIVE system; use "OTE" for the OT&E system 26 "ipaddress": "172.31.3.16", // provide here your outgoing ip address 27 "debugmode": "0", // set it to "1" to get debug output of the communication with our Backend System API 28 } 29 } 30 {% endhighlight %} 31 32 Here a working example for our OT&E System: 33 34 {% highlight json %} 35 { 36 "hexonet": { 37 "apilogin": "test.user", 38 "apipassword": "test.passw0rd", 39 "apientity": "OTE", 40 "debugmode": "0", 41 } 42 } 43 {% endhighlight %} 44 45 ## Usage 46 47 Here's an example DNS Configuration `dnsconfig.js` using our provider module. 48 Even though it shows how you use us as Domain Registrar AND DNS Provider, we don't force you to do that. 49 You are free to decide if you want to use both of our provider technology or just one of them. 50 51 {% highlight javascript %} 52 // Providers: 53 var REG_HX = NewRegistrar('hexonet', 'HEXONET'); 54 var DNS_HX = NewDnsProvider('hexonet', 'HEXONET'); 55 56 // Set Default TTL for all RR to reflect our Backend API Default 57 // If you use additional DNS Providers, configure a default TTL 58 // per domain using the domain modifier DefaultTTL instead. 59 // also check this issue for [NAMESERVER TTL](https://github.com/StackExchange/dnscontrol/issues/176). 60 DEFAULTS( 61 {"ns_ttl":"3600"}, 62 DefaultTTL(3600) 63 ); 64 65 // Domains: 66 D('abhoster.com', REG_HX, DnsProvider(DNS_HX), 67 NAMESERVER('ns1.ispapi.net'), 68 NAMESERVER('ns2.ispapi.net'), 69 NAMESERVER('ns3.ispapi.net'), 70 NAMESERVER('ns4.ispapi.net'), 71 A('elk1', '10.190.234.178'), 72 A('test', '56.123.54.12') 73 ); 74 {% endhighlight %} 75 76 ## Metadata 77 78 This provider does not recognize any special metadata fields unique to HEXONET. 79 80 ## New domains 81 82 If a dnszone does not exist in your HEXONET account, DNSControl will *not* automatically add it with the `dnscontrol push` or `dnscontrol preview` command. You'll need to do that via the control panel manually or using the command `dnscontrol create-domains`. 83 This is because it could lead to unwanted costs on customer-side that we want to avoid. 84 85 ## Debug Mode 86 87 As shown in the configuration examples above, this can be activated on demand and it can be used to check the API commands send to our system. 88 In general this is thought for our purpose to have an easy way to dive into issues. But if you're interested what's going on, feel free to activate it. 89 90 ## IP Filter 91 92 In case you have ip filter settings made for you HEXONET account, please provide your outgoing ip address as shown in the configuration examples above.