NEW PROVIDER: OpenWRT#4166
Conversation
The integration testing log:As noted above it fails the TTL tests and some IGNORE tests because it skips the first half of the test due to not being able to create TXT records. |
|
Hello DNS friend! Thank you for submitting this! Looks good so far. I'll do a deeper PR review later. Just FYI: Don't worry about failing tests for unsupported record types. We're thinking about updating the test system to be aware of such differences. That might be a summer project. |
|
Now that the org move is complete, I'm sending a friendly ping to PRs. Please rebase and I'd be glad to review. |
|
Friendly ping? |
|
Sorry about that, it's the middle of exams season here so I won't be able to get back to this for a little while. |
|
No problem! Good grades are more important than DNS! |
|
Finally got around to rebasing it. The new integration testing log:Like before it's failing the same tests because of TTL and TXT support. |
Hello! This commit adds support for OpenWrt as a DNS provider, managing its entries through the LuCi RPC .
Some notes on the code:
It's my first time writing Go, so there be dragons beware.
The API is based on JSON-RPC, but from what I've read the rpc implementation in the standard library is deprecated, and other implementations are mainly crypto related, which I wouldn't want to pull as a dependency without asking first.
Since OpenWrt is pretty limited as a DNS it supports neither TXT records nor setting TTLs, this creates problems with integration tests.
Please create the GitHub label "provider-openwrt"