X Tutup
The Wayback Machine - https://web.archive.org/web/20200914053609/https://github.com/github/octodns/pull/45
Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add SoaRecord object and tests #45

Open
wants to merge 2 commits into
base: master
from
Open

Add SoaRecord object and tests #45

wants to merge 2 commits into from

Conversation

@ross
Copy link
Contributor

ross commented May 27, 2017

  • Add SoaRecord object and tests for it's behavior
    • will ignore diffs in mname and serial, other fields will count
  • Make a pass through adding SOA management support to providers
    • Route53 takes whatever I give it, this means it can be managed but the whole record will be overriten by what's in config including the mname and serial.
    • Dyn api seems to ignore the call to change the SOA record no matter what I pass in, no error or anything, so I don't think it can be managed through the API. A few of the fields can be managed in the UI. Will ask them about this, but as of now it's not going to support SOA.

Fixes #39
/cc @vanbroup

@ross ross self-assigned this May 27, 2017
@ross
Copy link
Contributor Author

ross commented May 27, 2017

I have Route53 working, but Dyn seems to ignore SOA updates via the API. If Dyn is a one-off I might continue this, but if the wonkiness continues elsewhere I'm probably going to abort the attempt and not wade into the mess.

@vanbroup
Copy link
Contributor

vanbroup commented Jun 2, 2017

The Dyn API looks to support updates to the SOA record:
https://help.dyn.com/update-soa-record-api/

Same for the used Dyn API Python SDK:
http://dyn.readthedocs.io/en/latest/tm/records/records.html#soarecord

Could the problem be that you try to delete/create an SOA record instead of updating it? I haven't looked at the code so not sure about the used logic.

NOTE: Dynect users do not have the permissions required to create or delete SOA records on the Dynect System.

@vanbroup
Copy link
Contributor

vanbroup commented Jun 2, 2017

For NS1 you can modify the ttl, refresh, retry, expiry, or nx_ttl within the SOA record by modifying the zone:
https://jsapi.apiary.io/apis/ns1api/reference/zones-and-records/zone/modify-a-zone.html

The SDK documentation for updating the zone information:
http://nsone.readthedocs.io/en/latest/api/zones.html#nsone.zones.Zone.update

@ross ross mentioned this pull request Nov 14, 2017
vanbroup added a commit to vanbroup/octodns that referenced this pull request Jan 31, 2018
This change imports records that are marked as proxied so that they can be synced to other DNS providers as described in
[this support acticle](https://support.cloudflare.com/hc/en-us/articles/115000830351-How-to-configure-DNS-for-CNAME-partial-setup-when-managing-DNS-externally).
Records that use this functionality will be ignored by this provider and not be synced back to Cloudflare as we don't know the origin record values that would be required.

This change does not allow you to enable, disable or configure the CDN itself as that would require a lot of metadata to be handled by OctoDNS.
The intention of this change is to allow users to run a multi-DNS provider setup without sending any traffic to their origin directly.

See also github#45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

None yet

2 participants
You can’t perform that action at this time.
X Tutup