today, I switched my DNS provider - from now on, I would like to use desec.io
However, I found out the hard way that there are rate limits in place which makes updating a challenge.
My provider offers me a dynamic IPv6 prefix, and after getting a new prefix, I wish to update my IPv6 addresses for the servers in my network.
Is there a possibility to increase the number of possible updates per minute to maybe 20? As this will only happen whenever my prefix changes, the impact to the overall system will still be small.
That is against RIPE recommendations and you should switch your ISP if possible.
I know this isn’t always easy. This is just to say that we should not need to make changes to desec.io, just because some ISP is a fool.
On a more practical level, how about you randomise or stage the updates?
The rate limits are there for a reason, as they are the most expensive operation in our API. But, that doesn’t make updates hard – see below.
The canonical way to do that is to use our dynamic update API, where the docs say:
In some cases, it is useful to only update the network prefix of existing A or AAAA records. To achieve this, append the prefix length to the IP address query parameter, such as ipv6=2a01:a:b:c::/64, myipv4=1.2.3.0/24, etc. The host part of the value is ignored.
Whether dynamic prefixes, which complement the privacy extensions for the interface identifier, are a good idea or not is a controversial topic. The document you referred to is RIPE-690. It bases its persistent prefix recommendation on the technical difficulty of renumbering, which is necessary because in the absence of NAT, the hosts need to know their actual public IP addresses. There are other considerations besides this highly technical view, and calling ISPs who come to different conclusions “fools” is not helpful.
