GithubHelp home page GithubHelp logo

octodns-route53's Issues

Single domain that is both public and private in Route53

I have been poking at this off and on for a few months, and I wasn't sure if it was an octoDNS issue or a me issue.

We have a single domain set as two hosted zones in Route53, one public and one private. When attempting an octodns-dump against the domain, octoDNS is throwing an error about an empty geo value. There are no geo records set for either hosted zone.

config:

---
providers:
  config:
    class: octodns.provider.yaml.YamlProvider
    directory: ./data
  route53:
    class: octodns.provider.route53.Route53Provider
    access_key_id: env/AWS_ACCESS_KEY_ID
    secret_access_key: env/AWS_SECRET_ACCESS_KEY

zones:
  sillydomain.com.:
    sources:
      - route53
    targets:
      - config

octodns-dump debug output:

2018-02-06T09:50:14  [140736519537600] INFO  Manager __init__: config_file=config/ro_config_route53.yaml
2018-02-06T09:50:14  [140736519537600] INFO  Manager __init__:   max_workers=1
2018-02-06T09:50:14  [140736519537600] INFO  Manager __init__:   max_workers=False
2018-02-06T09:50:14  [140736519537600] DEBUG Manager __init__:   configuring providers
2018-02-06T09:50:14  [140736519537600] DEBUG YamlProvider[config] __init__: id=config, directory=./data, default_ttl=3600, enforce_order=1
2018-02-06T09:50:14  [140736519537600] DEBUG YamlProvider[config] __init__: id=config, apply_disabled=False, update_pcent_threshold=0, delete_pcent_threshold=0
2018-02-06T09:50:14  [140736519537600] DEBUG Route53Provider[route53] __init__: id=route53, access_key_id=KEY, secret_access_key=***
2018-02-06T09:50:14  [140736519537600] DEBUG Route53Provider[route53] __init__: id=route53, apply_disabled=False, update_pcent_threshold=0, delete_pcent_threshold=0
2018-02-06T09:50:14  [140736519537600] INFO  Manager dump: zone=sillydomain.com., sources=()
2018-02-06T09:50:14  [140736519537600] DEBUG YamlProvider[dump] __init__: id=dump, directory=data/, default_ttl=3600, enforce_order=1
2018-02-06T09:50:14  [140736519537600] DEBUG YamlProvider[dump] __init__: id=dump, apply_disabled=False, update_pcent_threshold=0, delete_pcent_threshold=0
2018-02-06T09:50:14  [140736519537600] DEBUG Manager configured_sub_zones: subs=[]
2018-02-06T09:50:14  [140736519537600] DEBUG Zone __init__: zone=Zone<sillydomain.com.>, sub_zones=set([])
2018-02-06T09:50:14  [140736519537600] DEBUG Route53Provider[route53] populate: name=sillydomain.com., target=False, lenient=False
2018-02-06T09:50:14  [140736519537600] DEBUG Route53Provider[route53] _get_zone_id: name=sillydomain.com.
2018-02-06T09:50:14  [140736519537600] DEBUG Route53Provider[route53] r53_zones: loading
2018-02-06T09:50:15  [140736519537600] DEBUG Route53Provider[route53] _get_zone_id:   id=/hostedzone/PRIVATEID
2018-02-06T09:50:15  [140736519537600] DEBUG Route53Provider[route53] _load_records: zone_id=/hostedzone/PRIVATEID loading
Traceback (most recent call last):
  File "~/tmp/nosync/dns/env/bin/octodns-dump", line 11, in <module>
    load_entry_point('octodns', 'console_scripts', 'octodns-dump')()
  File "~/tmp/nosync/dns/env/src/octodns/octodns/cmds/dump.py", line 31, in main
    manager.dump(args.zone, args.output_dir, args.lenient, *args.source)
  File "~/tmp/nosync/dns/env/src/octodns/octodns/manager.py", line 360, in dump
    source.populate(zone, lenient=lenient)
  File "~/tmp/nosync/dns/env/src/octodns/octodns/provider/route53.py", line 464, in populate
    data = getattr(self, '_data_for_{}'.format(record_type))(rrset)
  File "~/tmp/nosync/dns/env/src/octodns/octodns/provider/route53.py", line 314, in _data_for_geo
    'values': [v['Value'] for v in rrset['ResourceRecords']],
KeyError: u'ResourceRecords'

Please let me know if this is a PEBCAK. 😄

Does Octodns-route53 support sub-domain NS records

Does OctoDNS supports sub domain NS records?

for example.com i have subdomain email.example.com and config file as below however I can't see it is getting created in Route53 and other records are in place.
under config/example.com.yaml i have like below
where I also have other record type of txt with same name!

email:
ttl: 300
type: NS
values:
- a.ns.campaign.adobe.com.
- b.ns.campaign.adobe.com.
- c.ns.campaign.adobe.com.
- d.ns.campaign.adobe.com.
email:
  ttl: 30
  type: TXT
  value: "google.com"

Edit: @ross added yaml quotes so that things would ~format

Updating to 0.0.5 breaks previously existing ALIAS records

I had our pipelines pulling the latest version of providers and we had not made any DNS changes since May.

We recently raised some changes and ran the plan to find that showed all of our ALIAS records set for deletion. Even after trying to octodns-dump the records they were still skipped: [4305765760] WARNING YamlProvider[dump] Route53Provider/ALIAS records not supported for cdn.*****.com.; omitting record

Where as usually we would get: [4345644416] WARNING Route53Provider[route53] cdn.****.com. is an Alias record. Skipping... and the record would be skipped.

I am unsure if I would have to add these records in manually(which we have hundreds and would take a very long time) or I am missing something in config here.

An example of the plan output that occurs to all our ALIAS records when running with 0.0.5:

Delete | ****** | Route53Provider/ALIAS | 942942942 | "******.amazonaws.com." A *****
-- | -- | -- | -- | --

I obviously haven't tested if this actually deletes them since I have no intention of deleting them. But also haven't tested this in an isolated environment.

So for now we are pinning to version 0.0.4 which will skip ALIAS records.

Route53: character limit of 32000 exceeded

I'm trying to sync from dyn to r53. However, this domain have about 2266 records. I'm getting the following error. Our other domains have similar amount of records.

ERROR OUTPUT

2017-06-22T11:58:04  [140736484107200] INFO  Route53Provider[route53] _apply: zone=xyz.net., len(changes)=2266
2017-06-22T11:58:04  [140736484107200] INFO  Route53Provider[route53] _apply:   sending change request for batch of 976 mods, 999 ResourceRecords
Traceback (most recent call last):
  File "/Users/aikram1271/Desktop/CodingStuff/DNS-Automation/octodns/env/bin/octodns-sync", line 11, in <module>
    load_entry_point('octodns==0.8.0', 'console_scripts', 'octodns-sync')()
  File "build/bdist.macosx-10.12-x86_64/egg/octodns/cmds/sync.py", line 39, in main
  File "build/bdist.macosx-10.12-x86_64/egg/octodns/manager.py", line 295, in sync
  File "build/bdist.macosx-10.12-x86_64/egg/octodns/provider/base.py", line 143, in apply
  File "build/bdist.macosx-10.12-x86_64/egg/octodns/provider/route53.py", line 661, in _apply
  File "build/bdist.macosx-10.12-x86_64/egg/octodns/provider/route53.py", line 684, in _really_apply
  File "/Users/aikram1271/Desktop/CodingStuff/DNS-Automation/octodns/env/lib/python2.7/site-packages/botocore/client.py", line 253, in _api_call
    return self._make_api_call(operation_name, kwargs)
  File "/Users/aikram1271/Desktop/CodingStuff/DNS-Automation/octodns/env/lib/python2.7/site-packages/botocore/client.py", line 543, in _make_api_call
    raise error_class(parsed_response, operation_name)
botocore.errorfactory.InvalidChangeBatch: An error occurred (InvalidChangeBatch) when calling the ChangeResourceRecordSets operation: RDATA character limit of 32000 exceeded.```

Route53 pool with health check that doesn't match the cname

Hi, I'm trying to do something that might be a little different than the general usecase, hope you might be able to help me.
I've created the following setup manually in route53 UI, and now trying to write it down to my octodns config:

In my example.com zone, 2 CNAME records for the same name test.example.com with Weighted routing policy, each with its own matching health check. However, the health checks and the CNAME targets have different domains

  1. test-primary.mydomain.com target, with weight 3, attached to health check that monitors test-health-primary.mydomain.com
  2. test-secondary.mydomain.com target, with weight 7, attached to health check that monitors test-health-secondary.mydomain.com

I'm not sure how to do that, as each record in the yaml requires type and value that have to be defined before the weighted routes and I couldn't find out how to create said healthchecks at all.

Can someone please help me with this?

TCP health check failure

Hey, we're looking at using OctoDNS to load balance two network load balancers in AWS.

I have the following configuration:

graphite:
  dynamic:
    pools:
      eu:
        values:
          - value: example.elb.eu-central-1.amazonaws.com.
          - value: example.elb.eu-west-1.amazonaws.com.
    rules:
      - pool: eu
  octodns:
    healthcheck:
      port: 2003
      protocol: TCP
    route53:
      healthcheck:
        failure_threshold: 3
        measure_latency: false
        request_interval: 10
  ttl: 60
  type: CNAME
  value: example.elb.eu-west-1.amazonaws.com.

And I get the following error when running octodns-sync --doit:

2022-10-21T09:54:20  [4331390336] DEBUG Manager sync:   checking safety
2022-10-21T09:54:20  [4331390336] DEBUG Manager sync:   applying
2022-10-21T09:54:20  [4331390336] INFO  Route53Provider[route53] apply: making 1 changes to example.com.
2022-10-21T09:54:20  [4331390336] INFO  Route53Provider[route53] _apply: zone=example.com., len(changes)=1
2022-10-21T09:54:20  [4331390336] DEBUG Route53Provider[route53] _get_zone_id: name=example.com.
2022-10-21T09:54:20  [4331390336] DEBUG Route53Provider[route53] _get_zone_id:   id=/hostedzone/Z3RY1PKX3DW9IJ
2022-10-21T09:54:20  [4331390336] DEBUG Route53Provider[route53] get_health_check_id: fqdn=graphite.example.com., type=CNAME, value=example.elb.eu-central-1.amazonaws.com., status=obey
2022-10-21T09:54:20  [4331390336] DEBUG Route53Provider[route53] health_checks: loading
2022-10-21T09:54:21  [4331390336] DEBUG urllib3.connectionpool https://route53.amazonaws.com:443 "GET /2013-04-01/healthcheck HTTP/1.1" 200 80260
2022-10-21T09:54:21  [4331390336] DEBUG urllib3.connectionpool https://route53.amazonaws.com:443 "GET /2013-04-01/healthcheck?marker=805c7fd0-c1c9-4232-8307-418dfdc84869 HTTP/1.1" 200 62828
2022-10-21T09:54:21  [4331390336] DEBUG urllib3.connectionpool https://route53.amazonaws.com:443 "POST /2013-04-01/healthcheck HTTP/1.1" 400 356
Traceback (most recent call last):
  File "/Users/samuel.parkinson/.local/share/virtualenvs/dns-mTNxZbUA/bin/octodns-sync", line 8, in <module>
    sys.exit(main())
  File "/Users/samuel.parkinson/.local/share/virtualenvs/dns-mTNxZbUA/lib/python3.10/site-packages/octodns/cmds/sync.py", line 57, in main
    manager.sync(
  File "/Users/samuel.parkinson/.local/share/virtualenvs/dns-mTNxZbUA/lib/python3.10/site-packages/octodns/manager.py", line 653, in sync
    total_changes += target.apply(plan)
  File "/Users/samuel.parkinson/.local/share/virtualenvs/dns-mTNxZbUA/lib/python3.10/site-packages/octodns/provider/base.py", line 245, in apply
    self._apply(plan)
  File "/Users/samuel.parkinson/.local/share/virtualenvs/dns-mTNxZbUA/lib/python3.10/site-packages/octodns_route53/__init__.py", line 1819, in _apply
    mods = mod_type(c, zone_id, existing_rrsets)
  File "/Users/samuel.parkinson/.local/share/virtualenvs/dns-mTNxZbUA/lib/python3.10/site-packages/octodns_route53/__init__.py", line 1578, in _mod_Create
    new_records = self._gen_records(change.new, zone_id, creating=True)
  File "/Users/samuel.parkinson/.local/share/virtualenvs/dns-mTNxZbUA/lib/python3.10/site-packages/octodns_route53/__init__.py", line 1574, in _gen_records
    return _Route53Record.new(self, record, zone_id, creating)
  File "/Users/samuel.parkinson/.local/share/virtualenvs/dns-mTNxZbUA/lib/python3.10/site-packages/octodns_route53/__init__.py", line 199, in new
    ret = cls._new_dynamic(provider, record, hosted_zone_id, creating)
  File "/Users/samuel.parkinson/.local/share/virtualenvs/dns-mTNxZbUA/lib/python3.10/site-packages/octodns_route53/__init__.py", line 140, in _new_dynamic
    _Route53DynamicValue(
  File "/Users/samuel.parkinson/.local/share/virtualenvs/dns-mTNxZbUA/lib/python3.10/site-packages/octodns_route53/__init__.py", line 515, in __init__
    self.health_check_id = provider.get_health_check_id(
  File "/Users/samuel.parkinson/.local/share/virtualenvs/dns-mTNxZbUA/lib/python3.10/site-packages/octodns_route53/__init__.py", line 1501, in get_health_check_id
    resp = self._conn.create_health_check(
  File "/Users/samuel.parkinson/.local/share/virtualenvs/dns-mTNxZbUA/lib/python3.10/site-packages/botocore/client.py", line 514, in _api_call
    return self._make_api_call(operation_name, kwargs)
  File "/Users/samuel.parkinson/.local/share/virtualenvs/dns-mTNxZbUA/lib/python3.10/site-packages/botocore/client.py", line 938, in _make_api_call
    raise error_class(parsed_response, operation_name)
botocore.errorfactory.InvalidInput: An error occurred (InvalidInput) when calling the CreateHealthCheck operation: Invalid parameter : TCP IPv4 health checks must have either IP address or fully qualified domain name specified.

And running octodns-sync without the --doit argument is successful and the plan looks like:

********************************************************************************
* example.com.
********************************************************************************
* route53 (Route53Provider)
*   Create <CnameRecord CNAME 60, graphite.example.com., example.elb.eu-west-1.amazonaws.com., {'eu': {'fallback': None, 'values': [{'value': 'example.elb.eu-central-1.amazonaws.com.', 'weight': 1, 'status': 'obey'}, {'value': 'example.elb.eu-west-1.amazonaws.com.', 'weight': 1, 'status': 'obey'}]}}, [{'pool': 'eu'}]> (config)
*   Summary: Creates=1, Updates=0, Deletes=0, Existing Records=4
********************************************************************************

Seems like the logic below assumes that a TCP type check will have an IP address as a value?

octodns-route53/octodns_route53/provider.py

Lines 1473 to 1477 in b442b56

if healthcheck_protocol != 'TCP':
config['FullyQualifiedDomainName'] = healthcheck_host
config['ResourcePath'] = healthcheck_path
if value:
config['IPAddress'] = value

And just to check such a health check can be made in Route 53:

Screenshot 2022-10-21 at 10 03 55

Is there a way to hide "root NS record supported"?

Hi Ross,

I managed many records and I'm asking if there is a way to hide this lines (I'm already using the --quiet mode):

[2023-10-23T15:20:29.695Z] 2023-10-23T15:20:29  [140466193733376] WARNING Route53Provider[route53] root NS record supported, but no record is configured for domain1.com.
[2023-10-23T15:20:29.695Z] 2023-10-23T15:20:29  [140466100107008] WARNING Route53Provider[route53] root NS record supported, but no record is configured for domain2.com.
[2023-10-23T15:20:29.695Z] 2023-10-23T15:20:29  [140466183243520] WARNING Route53Provider[route53] root NS record supported, but no record is configured for domain3.com.
[2023-10-23T15:20:29.695Z] 2023-10-23T15:20:29  [140466193733376] WARNING Route53Provider[route53] root NS record supported, but no record is configured for domain4.com.
[2023-10-23T15:20:29.695Z] 2023-10-23T15:20:29  [140466100107008] WARNING Route53Provider[route53] root NS record supported, but no record is configured for domain5.com.
[2023-10-23T15:20:29.695Z] 2023-10-23T15:20:29  [140466089617152] WARNING Route53Provider[route53] root NS record supported, but no record is configured for domain6.com.
[...]

For this case, the NS are already set inside Route53 and I want to keep them by default without surcharging them.

I think I don't want to hide all WARNING lines because it could interesting to have some, isn't it?

Thanks.

AwsAcmMangingProcessor can't be referenced

I'm not sure if this is the only piece missing, but the setup.py in this module should be using the same find_packages() function as in the main octodns repository here

Without this, octodns_route53.processor is missing from the packages and therefore can't be referenced for usage.

Does OctoDNS handle weighted Route53 records?

Hello OctoDNS,

I'm testing it and it's working great!

I'm wondering if OctoDNS handles weighted Route53 records?

For example, I created 2 records:

Record Name           Type      Routing Policy   Differentiator           Value         Record Id
test1.domain.com      A       Weighted                 100                192.169.0.1       (datacenter1)
test1.domain.com      A       Weighted                 0                 192.169.0.2       (datacenter2)
  1. I can't find a way to generate the right YAML.
  2. I used "octodns-dump" in order to dump the 2 records and shows how the Yaml was generetad but the command nevers dumped the records with "weighted".
    If my zone has 5 records, octodns-dump sees only 3 records:
INFO  Route53Provider[route53] populate:   found 3 records, exists=True
INFO  YamlProvider[dump] plan:   Creates=3, Updates=0, Deletes=0, Existing Records=0

Thanks for your help!

Add option to turn off trailing dot enforcing

Hello!

By default OctoDNS is very particular about trailing dots in records to enforce unified syntax between DNS providers. Meanwhile, Route 53 assumes that the domain name is fully qualified. This means that Route 53 treats www.example.com (without a trailing dot) and www.example.com. (with a trailing dot) as identical.

This can be worked around by running octodns-dump with the --lenient flag, to dump all records into a OctoDNS file, fixing syntax issues and then running octodns-sync.

However, there is a ongoing issue in Route53 that causes the records not to be updated with the trailing dot. The record can be modified in AWS console or with OctoDNS to add the trailing dot, however this change is not applied on save/sync. Therefore OctoDNS tries to apply the trailing dots each run, failing.

In case the trailing dots are removed from OctoDNS config, and sync run the process will exit in the following error:
octodns.record.exception.ValidationError: Invalid record

AWS Support is aware of the issue at hand and are working on a fix from AWS side. Direct quote:

-> I have checked internally and this is also a known issue to our team and they are working on a fix but there is also no ETA.

-> It was brought to the team's attention that via console updating existing records to have the trailing dot will not reflect as well as when using UPSERT for multiple CNAME records with trailing dot not all of them will reflect and have the dot. As seen here: https://repost.aws/questions/QUj9pIHHnyRIGKNJqjqLgaZQ/questions/QUj9pIHHnyRIGKNJqjqLgaZQ/route53-batch-of-changes-succeeding-but-only-making-one-of-the-changes ?

I'm suggesting a feature to be added, where trailing period enforcing could be switched off for octodns-route53 provider. This would make OctoDNS a bit more flexible with Route53 given their stance on the record syntax.

Regression with `lenient` setting for multi-answer PTR record

Hello!

I'm seeing a regression in version octodns==1.0.0rc0 when processing PTR records that have multiple values (typically not conventional but in this case my data source does have these and I believe it's still "technically allowed").

Versions:

octodns==1.0.0.rc0
octodns-route53=0.0.5

manager config:

zones:
  test.ntat.io.:
    lenient: True
    sources:
      - targetyaml
    targets:
      - route53

test.ntat.io.yaml:

  • picked up from targetyaml source
a:
  type: A
  values:
  - 1.1.1.1
  - 2.2.2.2
ptr:
  type: PTR
  values:
  - 1.1.1.1.
  - 2.2.2.2.

Logs:

Failure on 1.0.0rc0

  File "/var/task/octodns/manager.py", line 629, in sync
    ps, d = future.result()
  File "/var/task/octodns/manager.py", line 70, in result
    return self.func(*self.args, **self.kwargs)
  File "/var/task/octodns/manager.py", line 449, in _populate_and_plan
    plan = target.plan(zone, processors=processors)
  File "/var/task/octodns/provider/base.py", line 239, in plan
    desired = self._process_desired_zone(desired)
  File "/var/task/octodns_route53/__init__.py", line 1197, in _process_desired_zone
    return super(Route53Provider, self)._process_desired_zone(desired)
  File "/var/task/octodns/provider/base.py", line 147, in _process_desired_zone
    self.supports_warn_or_except(msg, fallback)
  File "/var/task/octodns/provider/base.py", line 219, in supports_warn_or_except
    raise SupportsException(f'{self.id}: {msg}')
octodns.provider.SupportsException: route53: multi-value PTR records not supported for ptr.test.ntat.io.

Successful fallback on 0.9.21

WARNING:Route53Provider[route53]:multi-value PTR records not supported for ptr.test.ntat.io.; falling back to single value, 1.1.1.1.
WARNING:Route53Provider[route53]:root NS record supported, but no record is configured for test.ntat.io.
INFO:Route53Provider[route53]:root NS record in existing, but not supported or not configured; ignoring it
INFO:Route53Provider[route53]:plan:   Creates=2, Updates=0, Deletes=0, Existing Records=0
INFO:Plan:
********************************************************************************
* test.ntat.io.
********************************************************************************
* route53 (Route53Provider)
*   Create <ARecord A 3600, a.test.ntat.io., ['1.1.1.1', '2.2.2.2']> (targetyaml)
*   Create <PtrRecord PTR 3600, ptr.test.ntat.io., ['1.1.1.1.']> (targetyaml)
*   Summary: Creates=2, Updates=0, Deletes=0, Existing Records=0
********************************************************************************

Route53: dynamic record triggers update even with no changes to the record

I have the following dynamic record:

www:
  dynamic:
    pools:
      eu:
        values:
        - value: aloadofELBstuffhere.amazonaws.com.
    rules:
    - geos:
      - EU
      pool: eu
  ttl: 300
  type: CNAME
  value: web.example.com.

When I sync to route53, it creates the record(s) the first time. All good. When I run a sync the second time, it reports an update, even though nothing has changed:

* route53 (Route53Provider)
*   Update
*     <CnameRecord CNAME 300, www.testing123.com., web.example.com., {'eu': {'fallback': None, 'values': [{'value': 'aloadofELBstuffhere.amazonaws.com.', 'weight': 1}]}}, [{'pool': 'eu', 'geos': ['EU']}]> ->
*     <CnameRecord CNAME 300, www.testing123.com., web.example.com., {'eu': {'fallback': None, 'values': [{'value': 'aloadofELBstuffhere.amazonaws.com.', 'weight': 1}]}}, [{'pool': 'eu', 'geos': ['EU']}]> (config)
*   Summary: Creates=0, Updates=1, Deletes=0, Existing Records=3

I expect the sync to detect that nothing has changed and Updates=0.

Handle R53 'Alias' Records

Route53 Alias records are kinda like CNAME records, but you can have them at the Apex, which as you can imagine isn't going to translate between providers very well.

They also have a different response for list-resource-record-sets (example below)

{
    "ResourceRecordSets": [
        {
            "AliasTarget": {
                "HostedZoneId": "Z1EXAMPLE",
                "EvaluateTargetHealth": false,
                "DNSName": "s3-website-ap-southeast-2.amazonaws.com."
            },
            "Type": "A",
            "Name": "example.com."
        },
        {
            "ResourceRecords": [
                {
                    "Value": "127.0.0.1"
                }
            ],
            "Type": "A",
            "Name": "test.example.com.",
            "TTL": 300
        },

See the AWS Documentation for more info on Alias records

octodns doesn't handle this gracefully, and will throw a KeyError

(env) ☁  dns  octodns-dump --config-file=./config/production.yaml --output-dir=./tmp example.com. route53 --debug
2017-04-30T20:17:19  [139951851439872] INFO  Manager __init__: config_file=./config/production.yaml
2017-04-30T20:17:19  [139951851439872] DEBUG Manager __init__:   configuring providers
2017-04-30T20:17:19  [139951851439872] DEBUG Route53Provider[route53] __init__: id=route53, access_key_id=***, secret_access_key=***
2017-04-30T20:17:19  [139951851439872] DEBUG Route53Provider[route53] __init__: id=route53, apply_disabled=False
2017-04-30T20:17:19  [139951851439872] INFO  Manager dump: zone=example.com., sources=()
2017-04-30T20:17:19  [139951851439872] DEBUG YamlProvider[dump] __init__: id=dump, directory=./tmp, default_ttl=3600
2017-04-30T20:17:19  [139951851439872] DEBUG YamlProvider[dump] __init__: id=dump, apply_disabled=False
2017-04-30T20:17:19  [139951851439872] DEBUG Manager configured_sub_zones: subs=[]
2017-04-30T20:17:19  [139951851439872] DEBUG Zone __init__: zone=Zone<example.com.>, sub_zones=set([])
2017-04-30T20:17:19  [139951851439872] DEBUG Route53Provider[route53] populate: name=example.com.
2017-04-30T20:17:19  [139951851439872] DEBUG Route53Provider[route53] _get_zone_id: name=example.com.
2017-04-30T20:17:19  [139951851439872] DEBUG Route53Provider[route53] r53_zones: loading
2017-04-30T20:17:20  [139951851439872] DEBUG Route53Provider[route53] _get_zone_id:   id=/hostedzone/Z3IUOSSN6JQ0DU
2017-04-30T20:17:20  [139951851439872] DEBUG Route53Provider[route53] _load_records: zone_id=/hostedzone/Z3IUOSSN6JQ0DU loading
Traceback (most recent call last):
  File "/tmp/dns/env/bin/octodns-dump", line 11, in <module>
    sys.exit(main())
  File "/tmp/dns/env/local/lib/python2.7/site-packages/octodns/cmds/dump.py", line 28, in main
    manager.dump(args.zone, args.output_dir, *args.source)
  File "/tmp/dns/env/local/lib/python2.7/site-packages/octodns/manager.py", line 330, in dump
    source.populate(zone)
  File "/tmp/dns/env/local/lib/python2.7/site-packages/octodns/provider/route53.py", line 365, in populate
    data = getattr(self, '_data_for_{}'.format(record_type))(rrset)
  File "/tmp/dns/env/local/lib/python2.7/site-packages/octodns/provider/route53.py", line 235, in _data_for_geo
    'values': [v['Value'] for v in rrset['ResourceRecords']],
KeyError: u'ResourceRecords'
(env) ☁  dns

Latency Routing Policy

Working with a company that use OctoDNS to manage their Route53 DNS, we are wanting to implement latency based routing.

Is this supported? Cant see any mention of it in the documentation.

Have you got a full list of supported features including the correct syntaxes to use in the configuration files?

Need to add a space before ";" (semi-colon)?

Hello,

I'm trying to add a DMARC TXT and I always have "unescaped ;".

TEST 1

Input:

_dmarc:
  - type: TXT
    value: 'v=DMARC1; p=quarantine'

Result:

unescaped ; in "v=DMARC1; p=quarantine"

TEST 2

Input:

_dmarc:
  - type: TXT
    value: "v=DMARC1; p=quarantine"

Result:

unescaped ; in "v=DMARC1; p=quarantine"

TEST 3

Input:

_dmarc:
  - type: TXT
    value: "v=DMARC1\; p=quarantine"

Result:

yaml.scanner.ScannerError: while scanning a double-quoted scalar found unknown escape character ';'

TEST 4

Input:

_dmarc:
  - type: TXT
    value: v=DMARC1; p=quarantine

Result:

unescaped ; in "v=DMARC1; p=quarantine"

TEST 5

So I tried with an escaping "" before the ";":

Input:

_dmarc:
  - type: TXT
    value: v=DMARC1\; p=quarantine

Result:

['v=DMARC1\; p=quarantine']> (config)

TEST 6

But there is the "" which is not great. ;)

Input:

_dmarc:
  - type: TXT
    value: v=DMARC1\; p=quarantine

Result:

['v=DMARC1\; p=quarantine']> (config)

What am I doing wrong?

Thanks.

Add IRSA support

For now access_key_id and secret_access_key are mandatory when configuring octodns_route53.Route53Provider. But we want to avoid using bare AWS credentials and use IAM role for service account to interact with Route53 since OctoDNS deployed in our EKS cluster - https://docs.aws.amazon.com/eks/latest/userguide/iam-roles-for-service-accounts.html

As I see provider using boto3 so it should be possible out of the box because when IRSA used all important environment variables are injected in container:

        - name: AWS_STS_REGIONAL_ENDPOINTS
          value: regional
        - name: AWS_DEFAULT_REGION
          value: us-east-1
        - name: AWS_REGION
          value: us-east-1
        - name: AWS_ROLE_ARN
          value: >-
            arn:aws:iam::xxx:role/xxx
        - name: AWS_WEB_IDENTITY_TOKEN_FILE
          value: /var/run/secrets/eks.amazonaws.com/serviceaccount/token

route53 with healthcheck record sync issue

source: route53
target: digitalocean

failover record bind healthcheck
master:
a.example.com
1.1.1.1
backup:
a.example.com
2.2.2.2

octodns will sync backup records to digitalocean DNS
Not in line with expectations
like:
a.example.com
2.2.2.2
hope:
a.example.com
1.1.1.1

OctoDNS bug when deleting domainkeys on Route53

In Route53 domainkeys appear to get pulled as multiple strings - eg.
"k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA+kQV0ao2xYF2eMb2YjjLWD7CoRg1oW+WugpnONbTXlEYOMGMIOHW7JV8aHBJ5ArE07sYAYq0JpxUrokjhLS4whiyb0VqFcKP3BHbhR" "awlP4v/52ZD1JgxLadC3vuuPXD4GYNBl0wvedUcpgnn5r/q76eZKmaEM6HkjLLoje77qnHYHvzdjPf/MEp0" "gbtGnHPAIB9uUN+Ij+AAIdIKqMBGLg/xOnz+rkr9l64yaBcRBz2NXQHd9Ac+sZNfSM/zvpUPE5xvAK3vYhoGKVdYPEUHrUGZxkh1LFmCjucoM92O4bBWHqDJc2y8xuXD222Rr8tKV6fAYZvSX1MY4vLJoOA1QIDAQAB"

The domainkey had been previously created as a single string through Octo.

The error received from Octo on deletion is :

When botocore.errorfactory.InvalidChangeBatch: An error occurred (InvalidChangeBatch) when calling the ChangeResourceRecordSets operation: [Tried to delete resource record set [name='mailo._domainkey.xxxxxxx.com.', type='TXT'] but the values provided do not match the current values, Tried to delete resource record set [name='pic._domainkey.system.xxxxxxx.com.', type='TXT'] but the values provided do not match the current values]

Temporary workaround was to delete the keys manually.

Route 53: Too many values to unpack MX

Here's my config:

  config:
    class: octodns.provider.yaml.YamlProvider
    directory: /opt/dns/octozones
    enforce_order: false
  # nsone:
  #   class: octodns.provider.ns1.Ns1Provider
  #   api_key: env/NSONE_KEY
  zonefile:
    class: octodns.source.axfr.ZoneFileSource
    directory: /opt/dns/zonefiles
  route53:
    class: octodns.provider.route53.Route53Provider
    access_key_id: env/AWS_ACCESS_KEY_ID
    secret_access_key: env/AWS_ACCESS_KEY
zones:
  example.com.:
    sources:
      - route53
    targets:
      - config

When I then run octodns-sync against this config, i recieve the following error:

2019-03-28T14:17:39  [140109562977128] INFO  Manager __init__:   max_workers=1
2019-03-28T14:17:39  [140109562977128] INFO  Manager __init__:   max_workers=False
2019-03-28T14:17:40  [140109562977128] INFO  Manager sync: eligible_zones=[], eligible_targets=[], dry_run=True, force=False
2019-03-28T14:17:40  [140109562977128] INFO  Manager sync:   zone=example.com.
2019-03-28T14:17:40  [140109562977128] INFO  Manager sync:   sources=['route53'] -> targets=['config']
2019-03-28T14:17:41  [140109562977128] WARNING Route53Provider[route53] awards.example.com. is an Alias record. Skipping...
2019-03-28T14:17:41  [140109562977128] WARNING Route53Provider[route53] aws.example.com. is an Alias record. Skipping...
2019-03-28T14:17:41  [140109562977128] WARNING Route53Provider[route53] beoplay.example.com. is an Alias record. Skipping...
2019-03-28T14:17:41  [140109562977128] WARNING Route53Provider[route53] beta.example.com. is an Alias record. Skipping...
2019-03-28T14:17:41  [140109562977128] WARNING Route53Provider[route53] bowersandwilkins.example.com. is an Alias record. Skipping...
2019-03-28T14:17:41  [140109562977128] WARNING Route53Provider[route53] cdn.example.com. is an Alias record. Skipping...
2019-03-28T14:17:41  [140109562977128] WARNING Route53Provider[route53] css.cdn.example.com. is an Alias record. Skipping...
2019-03-28T14:17:41  [140109562977128] WARNING Route53Provider[route53] images.cdn.example.com. is an Alias record. Skipping...
2019-03-28T14:17:41  [140109562977128] WARNING Route53Provider[route53] community.example.com. is an Alias record. Skipping...
Traceback (most recent call last):
  File "/usr/local/bin/octodns-sync", line 10, in <module>
    sys.exit(main())
  File "/usr/local/lib/python2.7/site-packages/octodns/cmds/sync.py", line 39, in main
    dry_run=not args.doit, force=args.force)
  File "/usr/local/lib/python2.7/site-packages/octodns/manager.py", line 301, in sync
    plans = [p for f in futures for p in f.result()]
  File "/usr/local/lib/python2.7/site-packages/octodns/manager.py", line 56, in result
    return self.func(*self.args, **self.kwargs)
  File "/usr/local/lib/python2.7/site-packages/octodns/manager.py", line 224, in _populate_and_plan
    source.populate(zone)
  File "/usr/local/lib/python2.7/site-packages/octodns/provider/route53.py", line 491, in populate
    data = getattr(self, '_data_for_{}'.format(record_type))(rrset)
  File "/usr/local/lib/python2.7/site-packages/octodns/provider/route53.py", line 385, in _data_for_MX
    preference, exchange = rr['Value'].split(' ')
ValueError: too many values to unpack

There are only 8 MX records, and a total of 86 record sets in this zone. I have tested on smaller zones with identical MX records and the error does not occur. Similarly, i have tested on larger zones with no MX records, and the error does not occur.

Feature Request: Add DS record support to octodns-route53

Hi Ross & Team.

Lack of DS record support is the only thing blocking me from migrating a few of our zones from a custom script over to octodns. All of our other zones are working well with octodns/route53 and we enjoy using it. I'd rather use octodns over my custom script.

With respect to supporting DNSEC-enabled subdomains, DS record values are essentially text records.

Is there a particular reason support was omitted or just a matter of finding someone to do it?

Thanks!

Public and Private DNS in Route53

Am I missing step somewhere? How to distinguish between the public and private hosted zone types in Route53?

We have a single domain for both public and private, the data within is obviosuly very different. We'd like to migrate away from RoadWorker and possible use OctoDNS. When I run octodns-dump it only grabs the private data, not the public. How do you grab both, and ultimately manage and sync both from separate config files?

Thanks

Octodns does one change at a time

Hi!
I just started using Octodns and I came to a problem. I have a bunch of zones and many of them have CNAMEs with no dot at the end. I dumped all the records with --lenient, added trailing dots everywhere but the problem is - when I apply these changes, it changes only one record at a time:

❯ octodns-sync --config-file zones/_config.yml myzone.com. --target route53 --force --doit --debug
...
2022-12-04T22:07:28  [140143402022720] INFO  Manager sync:   11 total changes

❯ octodns-sync --config-file zones/_config.yml myzone.com. --target route53 --force --doit --debug
...
2022-12-04T22:08:34  [140034002523968] INFO  Manager sync:   10 total changes

❯ octodns-sync --config-file zones/_config.yml myzone.com. --target route53 --force --doit --debug
...
2022-12-04T22:09:27  [140107546101568] INFO  Manager sync:   9 total changes

Even with the --debug flag I see no errors or anything. I thought maybe the request contains only one record and so I went patching Route53's _really_apply method to print batch. Apparently, this is not the case since all 8 entries were there:

2022-12-04T22:19:04  [140442529761088] INFO  Route53Provider[route53] _apply:   sending change request for batch of 8 mods, 8 ResourceRecords
[
  {
    "Action": "UPSERT",
    "ResourceRecordSet": {
      "Name": "*.foo.myzone.com",
      "ResourceRecords": [
        {
          "Value": "test.myzone.com"
        }
      ],
      "TTL": 3600,
      "Type": "CNAME"
    }
  },
  ... skipped 6 identical entries
  {
    "Action": "UPSERT",
    "ResourceRecordSet": {
      "Name": "amazonses-eu.myzone.com",
      "ResourceRecords": [
        {
          "Value": "10 feedback-smtp.eu-central-1.amazonses.com."
        }
      ],
      "TTL": 3600,
      "Type": "MX"
    }
  }
]
2022-12-04T22:19:04  [140442529761088] DEBUG Route53Provider[route53] _really_apply:   sending change request, comment=Change: 54fcb03a40ec4c00af42c78449973a3e
2022-12-04T22:19:04  [140442529761088] DEBUG urllib3.connectionpool https://route53.amazonaws.com:443 "POST /2013-04-01/hostedzone/Z01231241214Z6V/rrset/ HTTP/1.1" 200 342
2022-12-04T22:19:04  [140442529761088] DEBUG Route53Provider[route53] _really_apply:   change info={'Id': '/change/C04804732OXR51RNSQD3Y', 'Status': 'PENDING', 'SubmittedAt': datetime.datetime(2022, 12, 4, 19, 19, 4, 465000, tzinfo=tzutc()), 'Comment': 'Change: 54fcb03a40ec4c00af42c78449973a3e'}

Not sure where to look next. Is this a bug?

ALIAS record dump issue

Dumped a zone with an ALIAS record.

With version 0.0.5, the dumped zone contains the evaluate-target-health and hosted-zone-id elements (using a dash).
Running a sync with the unmodified dumped zone completes correctly with no changes.

With version 0.0.5+b10ce65c (latest version), the dumped zone contains the evaluate_target_health and hosted_zone_id elements (using an underscore).
Running a sync with the unmodified dumped zone fails with validation error service alias without hosted-zone-id.

See below for the full outputs.

WORKING CORRECTLY with octodns_route53 0.0.5:

% octodns-dump --config-file=config/production.yaml --output-dir=config/ 'mytest.com.' route53
2023-10-16T22:06:44  [140704378021632] INFO  Manager __init__: config_file=config/production.yaml, (octoDNS 1.2.1)
2023-10-16T22:06:44  [140704378021632] INFO  Manager _config_executor: max_workers=1
2023-10-16T22:06:44  [140704378021632] INFO  Manager _config_include_meta: include_meta=False
2023-10-16T22:06:44  [140704378021632] INFO  Manager _config_auto_arpa: auto_arpa=False
2023-10-16T22:06:44  [140704378021632] INFO  Manager __init__: global_processors=[]
2023-10-16T22:06:44  [140704378021632] INFO  Manager __init__: global_post_processors=[]
2023-10-16T22:06:44  [140704378021632] INFO  Manager __init__: provider=config (octodns.provider.yaml 1.2.1)
2023-10-16T22:06:44  [140704378021632] INFO  botocore.credentials Found credentials in environment variables.
2023-10-16T22:06:44  [140704378021632] INFO  Manager __init__: provider=route53 (octodns_route53 0.0.5)
2023-10-16T22:06:44  [140704378021632] INFO  Manager dump: zone=mytest.com., output_dir=config/, output_provider=None, lenient=False, split=False, sources=['route53']
2023-10-16T22:06:44  [140704378021632] INFO  Manager dump: using custom YamlProvider
2023-10-16T22:06:45  [140704378021632] INFO  Route53Provider[route53] populate:   found 2 records, exists=True
2023-10-16T22:06:45  [140704378021632] INFO  YamlProvider[dump] plan: desired=mytest.com.
2023-10-16T22:06:45  [140704378021632] INFO  YamlProvider[dump] plan:   Creates=2, Updates=0, Deletes=0, Existing Records=0
2023-10-16T22:06:45  [140704378021632] INFO  YamlProvider[dump] apply: making 2 changes to mytest.com.


% cat config/mytest.com.yaml                                                                  
---
? ''
: ttl: 172800
  type: NS
  values:
  - test.co.uk.
  - test.com.
  - test.net.
  - test.org.
myalias:
  ttl: 942942942
  type: Route53Provider/ALIAS
  value:
    evaluate-target-health: false
    hosted-zone-id: Z2FDTNDATAQYW2
    name: xxx.cloudfront.net.
    type: A


% octodns-sync --config-file=config/production.yaml 
2023-10-16T22:07:18  [140704378021632] INFO  Manager __init__: config_file=config/production.yaml, (octoDNS 1.2.1)
2023-10-16T22:07:18  [140704378021632] INFO  Manager _config_executor: max_workers=1
2023-10-16T22:07:18  [140704378021632] INFO  Manager _config_include_meta: include_meta=False
2023-10-16T22:07:18  [140704378021632] INFO  Manager _config_auto_arpa: auto_arpa=False
2023-10-16T22:07:18  [140704378021632] INFO  Manager __init__: global_processors=[]
2023-10-16T22:07:18  [140704378021632] INFO  Manager __init__: global_post_processors=[]
2023-10-16T22:07:18  [140704378021632] INFO  Manager __init__: provider=config (octodns.provider.yaml 1.2.1)
2023-10-16T22:07:18  [140704378021632] INFO  botocore.credentials Found credentials in environment variables.
2023-10-16T22:07:18  [140704378021632] INFO  Manager __init__: provider=route53 (octodns_route53 0.0.5)
2023-10-16T22:07:18  [140704378021632] INFO  Manager sync: eligible_zones=[], eligible_targets=[], dry_run=True, force=False, plan_output_fh=<stdout>
2023-10-16T22:07:18  [140704378021632] INFO  Manager sync:   zone=mytest.com.
2023-10-16T22:07:18  [140704378021632] INFO  Manager sync:   sources=['config']
2023-10-16T22:07:18  [140704378021632] INFO  Manager sync:   targets=['route53']
2023-10-16T22:07:18  [140704378021632] INFO  YamlProvider[config] populate:   found 2 records, exists=False
2023-10-16T22:07:18  [140704378021632] INFO  Route53Provider[route53] plan: desired=mytest.com.
2023-10-16T22:07:19  [140704378021632] INFO  Route53Provider[route53] populate:   found 2 records, exists=True
2023-10-16T22:07:19  [140704378021632] INFO  Route53Provider[route53] plan:   No changes
2023-10-16T22:07:19  [140704378021632] INFO  Plan 
********************************************************************************
No changes were planned
********************************************************************************

NOT WORKING CORRECTLY with octodns_route53 0.0.5+b10ce65c

% octodns-dump --config-file=config/production.yaml --output-dir=config/ 'mytest.com.' route53
2023-10-16T22:12:28  [140704378021632] INFO  Manager __init__: config_file=config/production.yaml, (octoDNS 1.2.1)
2023-10-16T22:12:28  [140704378021632] INFO  Manager _config_executor: max_workers=1
2023-10-16T22:12:28  [140704378021632] INFO  Manager _config_include_meta: include_meta=False
2023-10-16T22:12:28  [140704378021632] INFO  Manager _config_auto_arpa: auto_arpa=False
2023-10-16T22:12:28  [140704378021632] INFO  Manager __init__: global_processors=[]
2023-10-16T22:12:28  [140704378021632] INFO  Manager __init__: global_post_processors=[]
2023-10-16T22:12:28  [140704378021632] INFO  Manager __init__: provider=config (octodns.provider.yaml 1.2.1)
2023-10-16T22:12:28  [140704378021632] INFO  Route53Provider[route53] __init__: id=route53, access_key_id=None, max_changes=1000, delegation_set_id=None, get_zones_by_name=False
2023-10-16T22:12:28  [140704378021632] INFO  botocore.credentials Found credentials in environment variables.
2023-10-16T22:12:28  [140704378021632] INFO  Manager __init__: provider=route53 (octodns_route53 0.0.5+b10ce65c)
2023-10-16T22:12:28  [140704378021632] INFO  Manager dump: zone=mytest.com., output_dir=config/, output_provider=None, lenient=False, split=False, sources=['route53']
2023-10-16T22:12:28  [140704378021632] INFO  Manager dump: using custom YamlProvider
2023-10-16T22:12:29  [140704378021632] INFO  Route53Provider[route53] populate:   found 2 records, exists=True
2023-10-16T22:12:29  [140704378021632] INFO  YamlProvider[dump] plan: desired=mytest.com.
2023-10-16T22:12:29  [140704378021632] INFO  YamlProvider[dump] plan:   Creates=2, Updates=0, Deletes=0, Existing Records=0
2023-10-16T22:12:29  [140704378021632] INFO  YamlProvider[dump] apply: making 2 changes to mytest.com.


% cat config/mytest.com.yaml                                                                  
---
? ''
: ttl: 172800
  type: NS
  values:
  - test.co.uk.
  - test.com.
  - test.net.
  - test.org.
myalias:
  ttl: 942942942
  type: Route53Provider/ALIAS
  value:
    evaluate_target_health: false
    hosted_zone_id: Z2FDTNDATAQYW2
    name: xxx.cloudfront.net.
    type: A


% octodns-sync --config-file=config/production.yaml
2023-10-16T22:13:05  [140704378021632] INFO  Manager __init__: config_file=config/production.yaml, (octoDNS 1.2.1)
2023-10-16T22:13:05  [140704378021632] INFO  Manager _config_executor: max_workers=1
2023-10-16T22:13:05  [140704378021632] INFO  Manager _config_include_meta: include_meta=False
2023-10-16T22:13:05  [140704378021632] INFO  Manager _config_auto_arpa: auto_arpa=False
2023-10-16T22:13:05  [140704378021632] INFO  Manager __init__: global_processors=[]
2023-10-16T22:13:05  [140704378021632] INFO  Manager __init__: global_post_processors=[]
2023-10-16T22:13:05  [140704378021632] INFO  Manager __init__: provider=config (octodns.provider.yaml 1.2.1)
2023-10-16T22:13:06  [140704378021632] INFO  Route53Provider[route53] __init__: id=route53, access_key_id=None, max_changes=1000, delegation_set_id=None, get_zones_by_name=False
2023-10-16T22:13:06  [140704378021632] INFO  botocore.credentials Found credentials in environment variables.
2023-10-16T22:13:06  [140704378021632] INFO  Manager __init__: provider=route53 (octodns_route53 0.0.5+b10ce65c)
2023-10-16T22:13:06  [140704378021632] INFO  Manager sync: eligible_zones=[], eligible_targets=[], dry_run=True, force=False, plan_output_fh=<stdout>
2023-10-16T22:13:06  [140704378021632] INFO  Manager sync:   zone=mytest.com.
2023-10-16T22:13:06  [140704378021632] INFO  Manager sync:   sources=['config']
2023-10-16T22:13:06  [140704378021632] INFO  Manager sync:   targets=['route53']
Traceback (most recent call last):
  File "/private/tmp/dns-latest/env/bin/octodns-sync", line 8, in <module>
    sys.exit(main())
             ^^^^^^
  File "/private/tmp/dns-latest/env/lib/python3.11/site-packages/octodns/cmds/sync.py", line 57, in main
    manager.sync(
  File "/private/tmp/dns-latest/env/lib/python3.11/site-packages/octodns/manager.py", line 694, in sync
    ps, d = future.result()
            ^^^^^^^^^^^^^^^
  File "/private/tmp/dns-latest/env/lib/python3.11/site-packages/octodns/manager.py", line 60, in result
    return self.func(*self.args, **self.kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/private/tmp/dns-latest/env/lib/python3.11/site-packages/octodns/manager.py", line 439, in _populate_and_plan
    source.populate(zone, lenient=lenient)
  File "/private/tmp/dns-latest/env/lib/python3.11/site-packages/octodns/provider/yaml.py", line 362, in populate
    self._populate_from_file(source, zone, lenient)
  File "/private/tmp/dns-latest/env/lib/python3.11/site-packages/octodns/provider/yaml.py", line 314, in _populate_from_file
    record = Record.new(
             ^^^^^^^^^^^
  File "/private/tmp/dns-latest/env/lib/python3.11/site-packages/octodns/record/base.py", line 82, in new
    raise ValidationError(fqdn, reasons, context)
octodns.record.exception.ValidationError: Invalid record "myalias.mytest.com.", ./config/mytest.com.yaml, line 11, column 3
  - service alias without hosted-zone-id

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.