dns-lexicon 2.4.3

Manipulate DNS records on various DNS providers in a standardized/agnostic way

lexicon

Manipulate DNS records on various DNS providers in a standardized/agnostic way.

Introduction

Lexicon provides a way to manipulate DNS records on multiple DNS providers in a standardized way. Lexicon has a CLI but it can also be used as a python library.

Lexicon was designed to be used in automation, specifically letsencrypt.

• Generating Intranet & Private Network SSL Certificates using Lets Encrypt & Lexicon

Providers

Only DNS providers who have an API can be supported by lexicon.

The current supported providers are:

• AuroraDNS (docs)
• AWS Route53 (docs)
• Cloudflare (docs)
• ClouDNS (docs)
• CloudXNS (docs)
• Constellix (docs)
• DigitalOcean (docs)
• DNSimple (docs)
• DnsMadeEasy (docs)
• DNSPark (docs)
• DNSPod (docs)
• EasyDNS (docs)
• Gandi (docs: RPC (old) / LiveAPI)
• Glesys (docs)
• GoDaddy (docs)
• Linode (docs)
• Linode v4 (docs)
• LuaDNS (docs)
• Memset (docs)
• Namecheap (docs)
• Namesilo (docs)
• NS1 (docs)
• OnApp (docs)
• OVH (docs)
• PointHQ (docs)
• PowerDNS (docs)
• Rackspace (docs)
• Rage4 (docs)
• Sakura Cloud by SAKURA Internet Inc. (docs)
• SoftLayer (docs)
• Subreg (docs)
• Transip (docs)
• Yandex (docs)
• Vultr (docs)
• Zonomi (docs)

Potential providers are as follows. If you would like to contribute one, please open a pull request.

• AHNames (docs)
• DurableDNS (docs) _{Can't set TXT records}
• Dyn (docs) :dollar: _{requires paid account}
• EntryDNS (docs) :dollar: _{requires paid account}
• FreeDNS (docs)
• Google Cloud DNS (docs)
• Host Virtual DNS (docs) :dollar: _{requires paid account}
• HostEurope
• ironDNS (docs) :dollar: _{requires paid account}
• INWX (docs)
• Liquidweb (docs) :dollar: _{requires paid account}
• Loopia (docs) :dollar: _{requires paid account}
• Mythic Beasts(docs)
• NFSN (NearlyFreeSpeech) (docs) :dollar: _{requires paid account}
• RFC2136 (docs)
• UltraDNS (docs) :dollar: _{requires paid account}
• WorldWideDns (docs) :dollar: _{requires paid account}
• Zeit (docs)
• Zerigo (docs) :dollar: _{requires paid account}
• Zoneedit (docs)
• Any others I missed

Setup

To use lexicon as a CLI application, do the following:

pip install dns-lexicon

Some providers (like Route53 and TransIP) require additional dependencies. You can install provider specific dependencies separately:

pip install dns-lexicon[route53]

You can also install the latest version from the repository directly.

pip install git+https://github.com/AnalogJ/lexicon.git

and with Route 53 provider dependencies:

pip install git+https://github.com/AnalogJ/lexicon.git#egg=dns-lexicon[route53]

Usage

$ lexicon -h
  usage: lexicon [-h] [--version] [--delegated DELEGATED]
                 {cloudflare,cloudxns,digitalocean,dnsimple,dnsmadeeasy,dnspark,dnspod,easydns,luadns,namesilo,nsone,pointhq,rage4,route53,vultr,yandex,zonomi}
                 ...

  Create, Update, Delete, List DNS entries

  positional arguments:
    {cloudflare,cloudxns,digitalocean,dnsimple,dnsmadeeasy,dnspark,dnspod,easydns,luadns,namesilo,nsone,pointhq,rage4,route53,vultr,yandex,zonomi}
                          specify the DNS provider to use
      cloudflare          cloudflare provider
      cloudxns            cloudxns provider
      digitalocean        digitalocean provider
    ...
      rage4               rage4 provider
      route53             route53 provider
      vultr               vultr provider
      yandex              yandex provider
      zonomi              zonomi provider

  optional arguments:
    -h, --help            show this help message and exit
    --version             show the current version of lexicon
    --delegated DELEGATED
                          specify the delegated domain


  $ lexicon cloudflare -h
  usage: lexicon cloudflare [-h] [--name NAME] [--content CONTENT] [--ttl TTL]
                            [--priority PRIORITY] [--identifier IDENTIFIER]
                            [--auth-username AUTH_USERNAME]
                            [--auth-token AUTH_TOKEN]
                            {create,list,update,delete} domain
                            {A,AAAA,CNAME,MX,NS,SPF,SOA,TXT,SRV,LOC}

  positional arguments:
    {create,list,update,delete}
                          specify the action to take
    domain                specify the domain, supports subdomains as well
    {A,AAAA,CNAME,MX,NS,SPF,SOA,TXT,SRV,LOC}
                          specify the entry type

  optional arguments:
    -h, --help            show this help message and exit
    --name NAME           specify the record name
    --content CONTENT     specify the record content
    --ttl TTL             specify the record time-to-live
    --priority PRIORITY   specify the record priority
    --identifier IDENTIFIER
                          specify the record for update or delete actions
    --auth-username AUTH_USERNAME
                          specify email address used to authenticate
    --auth-token AUTH_TOKEN
                          specify token used authenticate

Using the lexicon CLI is pretty simple:

# setup provider environmental variables:
export LEXICON_CLOUDFLARE_USERNAME="[e-mail]"
export LEXICON_CLOUDFLARE_TOKEN="cloudflare-api-token"

# list all TXT records on cloudflare
lexicon cloudflare list example.com TXT

# create a new TXT record on cloudflare
lexicon cloudflare create www.example.com TXT --name="_acme-challenge.www.example.com." --content="challenge token"

# delete a  TXT record on cloudflare
lexicon cloudflare delete www.example.com TXT --name="_acme-challenge.www.example.com." --content="challenge token"
lexicon cloudflare delete www.example.com TXT --identifier="cloudflare record id"

Authentication

Most supported DNS services provide an API token, however each service implements authentication differently. Lexicon attempts to standardize authentication around the following CLI flags:

• --auth-username - For DNS services that require it, this is usually the account id or email address
• --auth-password - For DNS services that do not provide an API token, this is usually the account password
• --auth-token - This is the most common auth method, the API token provided by the DNS service

You can see all the --auth-* flags for a specific service by reading the DNS service specific help: lexicon cloudflare -h

Environmental Variables

Instead of providing Authentication information via the CLI, you can also specify them via Environmental Variables. Every DNS service and auth flag maps to an Environmental Variable as follows: LEXICON_{DNS Provider Name}_{Auth Type}

So instead of specifying --auth-username and --auth-token flags when calling lexicon cloudflare ..., you could instead set the LEXICON_CLOUDFLARE_USERNAME and LEXICON_CLOUDFLARE_TOKEN environmental variables.

Letsencrypt Instructions

Lexicon has an example dehydrated hook file that you can use for any supported provider. All you need to do is set the PROVIDER env variable.

PROVIDER=cloudflare dehydrated --cron --hook dehydrated.default.sh --challenge dns-01

Lexicon can also be used with Certbot and the included Certbot hook file (requires configuration).

TroubleShooting & Useful Tools

There is an included example Dockerfile that can be used to automatically generate certificates for your website.

ToDo list

• [x] Create and Register a lexicon pip package.
• [ ] Write documentation on supported environmental variables.
• [x] Wire up automated release packaging on PRs.
• [x] Check for additional dns hosts with apis (from fog, dnsperf, libcloud)
• [ ] Get a list of Letsencrypt clients, and create hook files for them (letsencrypt clients)

Contributing Changes.

If the DNS provider you use is not already available, please consider contributing by opening a pull request.

License

MIT

References

tox