Porkbun sub domain identification seems flawed for multiple subdomain levels about ddclient HOT 4 CLOSED

Hi,

I just pushed a not-yet tested update onto the feature_porkbun_subdomains branch. With that change, your configuration should now work like this:

usev6=ifv6, ifv6=pppoe0, \
usev4=ifv4, ifv4=pppoe0, \
protocol=porkbun, \
apikey=pk1_123, \
secretapikey=sk1_123, \
login=pk1_123, \
root-domain=domain.com, \
password=sk1_123 \
sub2.sub1.domain.com

Please test whether this works and fully covers your usecase/issues.

from ddclient.

I've tested the changes and it works without issues, thank you very much!

p.s. I've migrated to porkbun since google domains are deprecating DDNS within February, so there might be an uptick of people using other ddclient services including porkbun
p.s.s. For some reason notes are wiped on porkbun end, but since I see it's clearly sent by ddclient, that's definitely on porkbun side
data="{\"content\":\"123.123.123.123\",\"apikey\":\"pk1_123\",\"ttl\":\"600\",\"notes\":\"DDNS\",\"secretapikey\":\"sk1_123\"}"

from ddclient.

I updated the docs and refactored the code a bit - could you run your check once more to confirm? Then I'll merge this into master for the next release.

from ddclient.

I've applied changes and tested both documentation and functionality, and everything works and looks good

from ddclient.