Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.
Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upMajor reworking of root NS handling, create & update, no delete #53
Conversation
- Can't get in to test Cloudflare so mark it as unknown state - Dyn & DnsimpleProvider don't support editing root NS records, Dyn may be able to sort of, but you can't remove their own... - Improve DnsimpleClient's info on http errors - Remove special root NS handling code from PowerDnsProvider, in this the case it used to support things should now be managed in the zone. Dynamic support still exists in PowerDnsBaseProvider to enable "other" use cases - _is_eligible removed from zone, all records are eligible as far as it's concerned now. - Bunch of tweaks to tests to handle the fact that root NS stuff are now included in changes.
|
OK. Looked this over more closely and have done some dry-run testing internally. The behavior seems to be as designed/desired so this is probably ready for thinking/review. |
|
any news on this? |
|
@joschi36 IIRC this stalled out when we ran into problems with many/most providers allowing us to manage the root NS records. Specifically that each provider's behavior was different and hard unify. It'd likely require a new provider ability "SUPPORTS_ROOT_NS" etc and even though would get tricky to handle all the edge cases. It may be possible to go through and get everything working in a best effort fashion, but this PR probably isn't sufficient. It's been left here to record the thinking/work. It'd be nice to have, but unfortunately isn't high on the priorities list. |
|
For us this has high priority as we plan to migrate around 600 zones with multiple octodns repos in github. For us it isn't an option and I'm currently working on a new PR resolving this issue for the providers that support it. |
dchauran
commented
Jan 15, 2020
|
@joschi36 do you have a link to that? My team also needs this. @basirjamil, @Arunothia FYI |
|
There's some WIP towards this over in #434. |
ross commentedJun 4, 2017
•
edited
able to sort of, but you can't remove their own...
case it used to support things should now be managed in the zone. Dynamic
support still exists in PowerDnsBaseProvider to enable "other" use cases
concerned now.
included in changes.
Closes #38