question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Support UltraDNS's Apex Alias records

See original GitHub issue

It seems that currently octodns does not support the Apex Alias records that one can configure on UltraDNS. E.g. trying to dump a zone from UltraDNS with such records causes octodns-dump to crash:

octodns-dump --config-file ./config/staging.yaml --output-dir ./ stg.XXX.com. ultradns                                                                                                                   
2020-12-10T16:27:50  [4492312000] INFO  Manager __init__: config_file=./config/staging.yaml
2020-12-10T16:27:50  [4492312000] INFO  Manager __init__:   max_workers=2
2020-12-10T16:27:50  [4492312000] INFO  Manager __init__:   include_meta=False
2020-12-10T16:27:51  [4492312000] INFO  Manager dump: zone=stg.XXX.com., sources=()
Traceback (most recent call last):
  File "/Users/ndenev/te/octodns/venv/bin/octodns-dump", line 8, in <module>
    sys.exit(main())
  File "/Users/ndenev/te/octodns/venv/lib/python3.9/site-packages/octodns/cmds/dump.py", line 34, in main
    manager.dump(args.zone, args.output_dir, args.lenient, args.split,
  File "/Users/ndenev/te/octodns/venv/lib/python3.9/site-packages/octodns/manager.py", line 469, in dump
    source.populate(zone, lenient=lenient)
  File "/Users/ndenev/te/octodns/venv/lib/python3.9/site-packages/octodns/provider/ultra.py", line 290, in populate
    _type = self.RECORDS_TO_TYPE[record['rrtype']]
KeyError: 'APEXALIAS (65282)'

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Comments:5 (5 by maintainers)

github_iconTop GitHub Comments

1reaction
rosscommented, Dec 10, 2020

Likely 2 things there:

  1. The Ultra DNS provider should ignore types it/octoDNS doesn’t understand/support
  2. I suspect APEXALIAS can be mapped to octoDNS’s ALIAS type, but I’m not familiar with Ultra DNS so can’t say for sure.

/cc @phelpsw who wrote the provider

0reactions
rosscommented, Jun 3, 2021

@ross When the next release is cut, the README.md should be updated to reference ALIAS support on UltraDNS.

Feel free to PR the edit now. If I’d thought of it we would have done it in the PR that added support.

Read more comments on GitHub >

github_iconTop Results From Across the Web

UltraDNS Managed Services Portal User Guide - CSC Global
This guide provides comprehensive step-by- step instructions on how to manage your DNS. Records and Domains on the Neustar UltraDNS. Portal. UI ...
Read more >
Resource: ultradns_record - Terraform Registry
Use this resource to manage standard DNS records in UltraDNS ... Create DNS record of type APEXALIAS (65282) ... The following arguments are...
Read more >
Why can't a CNAME record be used at the apex (aka root) of a ...
CNAME records were originally created to allow multiple names that provide the same resource to be aliased to a single "canonical name" for...
Read more >
Create alias records for services hosted in AWS
Amazon Route 53 alias records are mapped internally to the DNS name of alias targets such as AWS resources. Route 53 monitors the...
Read more >
Why I can't add the assigned CNAME to my DNS provider?
Here is a list of common DNS providers that support APEX CNAME (or ALIAS, ... DNS provider, Supported APEX record type ... UltraDNS,...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found