Hello.
As far as I can see, the SOA parameters were changed in the update https://github.com/hestiacp/hestiacp/commit/e14239e59f2deda0267734d2d6078c3cfcf88a8b
But I noticed it’s not working. Even though there are changes in /usr/local/hestia/func/domain.sh
$SERIAL
14400
$refresh
1209600
3600 )
But when I run v-rebuild-dns-domain, the value unfortunately changes to 3600000.
Something is clearly wrong. Please pay attention to this.
Hi,
I can’t reproduce it, it works fine in the tests I’m doing.
Show the output of these commands (replace example.com with the actual domain):
grep -A 6 SOA /home/*/conf/dns/example.com.db
dig @127.0.0.1 example.com SOA +short
ns1.com.ua. root.example.com . 30000001 14400 3600 1209600 3600
@ IN SOA ns1.com.ua. root.example.com . (
0030000001
14400
3600
1209600
3600 )
I created a new test domain specifically
It’s not clear where the number 0030000001 comes from.
That shows the right value 1209600
It should be 3000000001 instead of 0030000001 and I created a PR a few minutes ago to “fix” it but it doesn’t break anything.
If your concern is why we are now using 3000000001, 3000000002, 3000000003… instead of YYYYMMDDnn, the answer is in this PR:
main ← sahsanu:fix-soa-serial
merged 05:30PM - 29 Jul 26 UTC
Replace date-based DNS SOA serial numbers with a monotonic numeric counter to av… oid failures caused by the `YYYYMMDDNN` format, which is limited to 99 updates per day.
The new implementation initializes serials from a fixed base value (`30000000`) and increments them on every zone update. Legacy date-based serials are automatically migrated to the new format.
Serial overflow is handled using serial number arithmetic as defined by RFC 1982, ensuring correct wrap-around behavior while remaining compliant with DNS SOA serial comparison rules.
Fixes #5533
OK. No problem.
How do I fix current domains?
Rebuilding them should fix the value, that’s why I asked to use the commands against the actual dns domain. Maybe you forgot to restart bind.
main ← sahsanu:fix-serial-typo
opened 08:20PM - 17 Aug 26 UTC
Variable `serial` is using `30000000` instead of `3000000000`. It doesn't break … anything but we need to be consistent with the default serial used in function script `domain.sh`
I have already applied this fix manually.
committed 08:03AM - 14 Aug 26 UTC
Reduce the value from `3600000` to `1209600`
Fixes #5603
Should the value here be 1209600 and not 3600000?
Sorry, I don’t understand, that PR is replacing 3600000 with 1209600.
Well, I don’t understand either (But I understand that something is clearly wrong…
Could you please execute the commands against the domain where you are seeing the wrong value?
This applies to all domains. Because it was included in the update.
Unfortunately, I can’t show the actual domains for security reasons.
You just need to understand how to do it correctly in the end.
I don’t care about the actual domain, just execute the command and when pasting here replace it…
I can’t reproduce the issue, if I rebuild the dns domain the value is applied correctly to the SOA record.
ns1.example.com . root.example.com . 3000000005 14400 3600 1209600 3600
Ok, is this the correct meaning?
Yes, that’s the right value, it is using 1209600 (14 days) and it’s ok.
Thank you. I hope these minor changes will be made in the new version of the panel.
I tested it. Yes, for new domains, it adds the 3000000001 format, no problem.
But for existing ones, it stays at 30000002.
v-rebuild-dns-domain doesn’t help.
Existing ones will keep using 30000001,2,3... (8 numbers) the serial won’t be replaced with 3000000001,2,3... (10 numbers) because there is no need to do so. Both serials will work fine, so you should not worry about it.
I would prefer to use one soa standard for all domains.
I’m also interested in how and where I can globally change the address from root.example.com to my email address.