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 AXFRDDNS to automated tests #3279

Closed
gucci-on-fleek opened this issue Jan 1, 2025 · 0 comments · Fixed by #3290
Closed

Add AXFRDDNS to automated tests #3279

gucci-on-fleek opened this issue Jan 1, 2025 · 0 comments · Fixed by #3290

Comments

@gucci-on-fleek
Copy link
Contributor

gucci-on-fleek commented Jan 1, 2025

Standard Boilerplate

I would like to volunteer to maintain the credentials and account for the AXFR+DDNS provider.

  • The account/credentials should only access the test domain.

Yes.

  • Renew the domain in a timely manner.

Not applicable, uses an internal domain.

On the more general “availability” topic, the server should be up most of the time, but this is just a single server that hosts my personal website, so it may be down occasionally for updates. Uptime is generally pretty good though, just not quite as good as you'd expect from a commercial provider.

  • Don't do anything that will get you in trouble with your employer, like charging it to your employer without permission.

Not applicable, I'm unemployed.

To securely send the credentials to the project, use this link: https://transfer.secretoverflow.com/u/tlimoncelli

Done (item D8N1-RJUK).

Configuration

AXFR+DDNS is a little special in that it's a protocol and not a specific provider, so there are quite a few different valid configurations here. I'll go through the configuration options and list the valid values for my server. You can either choose to test just one possible valid configuration or multiple combinations of different options.

update-mode and transfer-mode

tcp and tcp-tls both work; udp will not.

transfer-key and update-key

Both are required, and both use the same keys. I've generated keys for as many algorithms as possible, so the valid values are:

  • hmac-md5:dnscontrol-testing-md5:[REDACTED]
  • hmac-sha1:dnscontrol-testing-sha1:[REDACTED]
  • hmac-sha224:dnscontrol-testing-sha224:[REDACTED]
  • hmac-sha256:dnscontrol-testing-sha256:[REDACTED]
  • hmac-sha384:dnscontrol-testing-sha384:[REDACTED]
  • hmac-sha512:dnscontrol-testing-sha512:[REDACTED]

master

Must be ns.maxchernoff.ca.

nameservers and transfer-server

Not necessary, but you can set them to ns.maxchernoff.ca if you want.

Details

Currently, the server is running Knot v3.4.3; to see what the version is in the future, you can run

$ dig @ns.maxchernoff.ca. CH TXT version.bind.

AXFR+DDNS is unable to configure DNSSEC, so AUTODNSSEC behaves as a check instead of as a command. Because of this, I've configured two domains with-dnssec.dnscontrol.internal. and without-dnssec.dnscontrol.internal. that behave as their names indicate. Aside from DNSSEC, both domains are identical.


That should be everything, but let me know if you have any questions or if something doesn't work properly. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants