You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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
Standard Boilerplate
I would like to volunteer to maintain the credentials and account for the AXFR+DDNS provider.
Yes.
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.
Not applicable, I'm unemployed.
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
andtransfer-mode
tcp
andtcp-tls
both work;udp
will not.transfer-key
andupdate-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
andtransfer-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
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 domainswith-dnssec.dnscontrol.internal.
andwithout-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!
The text was updated successfully, but these errors were encountered: