Project

General

Profile

Actions

Bug #16007

open

Dynamic DNS, Porkbun, "@.mydomain.xyz"

Added by Emanuel Persson about 2 months ago. Updated about 1 month ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Dynamic DNS
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Default
Affected Version:
2.7.x
Affected Architecture:

Description

Jan 22 12:50:13 pfSense php-fpm[44841]: /services_dyndns_edit.php: Configuration Change: admin@192.168.0.2 (Local Database): Dynamic DNS client configured.
Jan 22 12:50:13 pfSense php-fpm[44841]: /services_dyndns_edit.php: Dynamic DNS: updatedns() starting
Jan 22 12:50:13 pfSense php-fpm[44841]: /services_dyndns_edit.php: Dynamic DNS porkbun (@.mydomainname.xyz): _checkIP() starting.
Jan 22 12:50:13 pfSense php-fpm[44841]: /services_dyndns_edit.php: Dynamic DNS porkbun (@.mydomainname.xyz): xx.xxx.xxx.xx extracted from local system.
Jan 22 12:50:13 pfSense php-fpm[44841]: /services_dyndns_edit.php: Dynamic DNS (@.mydomainname.xyz): running get_failover_interface for wan. found igc0
Jan 22 12:50:13 pfSense php-fpm[44841]: /services_dyndns_edit.php: Dynamic DNS porkbun (@.mydomainname.xyz): _update() starting.
Jan 22 12:50:14 pfSense php-fpm[44841]: /services_dyndns_edit.php: Error message: 

igc0 is correct, that is my WAN.

So I'm unsure what changed? " *.mydomainname.xyz " have worked before if I remember correctly I used this for a really long time. I've had it configured like this for well over a year.


Files

clipboard-202501221253-aai6z.png (122 KB) clipboard-202501221253-aai6z.png Emanuel Persson, 01/22/2025 11:53 AM
Actions #1

Updated by Lev Prokofev about 2 months ago

Porkbun working fine for me on 24.11 software. Make sure you have API enabled for the domain in the Porkbun dashboard and have the proper key in the DynDNS config.

Actions #2

Updated by Emanuel Persson about 2 months ago

API Access is enabled. But for subdomains it would work but this is a "Root domain update". Not a subdomain update. I'm unsure what to write in the hostname field. for some providers its @ and that is what i have used before.. But i won't update.

Actions #3

Updated by Kris Phillips about 2 months ago

Emanuel Persson wrote in #note-2:

API Access is enabled. But for subdomains it would work but this is a "Root domain update". Not a subdomain update. I'm unsure what to write in the hostname field. for some providers its @ and that is what i have used before.. But i won't update.

Entering an @ symbol should be correct for updating the root of the domain. Is the error logs cut off or is there nothing below the "Error Message" section of your logging in the original bug report?

Actions #4

Updated by Emanuel Persson about 2 months ago

Kris Phillips wrote in #note-3:

Emanuel Persson wrote in #note-2:

API Access is enabled. But for subdomains it would work but this is a "Root domain update". Not a subdomain update. I'm unsure what to write in the hostname field. for some providers its @ and that is what i have used before.. But i won't update.

Entering an @ symbol should be correct for updating the root of the domain. Is the error logs cut off or is there nothing below the "Error Message" section of your logging in the original bug report?

It just ends there and nothing more was written in the logs. on the services_dyndns_edit.php page it says to use @ for "Cloudflare, Linode, Porkbun:" and still it won't work.. and i even tried to do a update now but without verbose enabled and the logs still just write "/services_dyndns_edit.php: Error message: ".

Actions #5

Updated by Ben Woods about 1 month ago

Could this be caused by porkbun moving the URL for their API recently?
Old Value: porkbun.com
New Value: api.porkbun.com
Deadline: 2024-12-01 00:00:00 UTC

Actions #6

Updated by Mustache Mustache about 1 month ago

Ben Woods wrote in #note-5:

Could this be caused by porkbun moving the URL for their API recently?
Old Value: porkbun.com
New Value: api.porkbun.com
Deadline: 2024-12-01 00:00:00 UTC

This was the issue.

Here is the fixed dyndns.class file:

https://github.com/Mustache84/swine-namic-dns/blob/main/etc/inc/dyndns.class

In the GUI, go to Diagnostics >> Edit File. Open up /etc/inc/dyndns.class
Copy and paste that wonderfully punny repository's dyndns.class' contents.
Save and then go restart your dyndns configuration by going to DynaicDNS service and click the "stop service" next to that particular DDNS config, and then start it back up.

Enjoy

Actions #7

Updated by Emanuel Persson about 1 month ago

Mustache Mustache wrote in #note-6:

Ben Woods wrote in #note-5:

Could this be caused by porkbun moving the URL for their API recently?
Old Value: porkbun.com
New Value: api.porkbun.com
Deadline: 2024-12-01 00:00:00 UTC

This was the issue.

Here is the fixed dyndns.class file:

https://github.com/Mustache84/swine-namic-dns/blob/main/etc/inc/dyndns.class

In the GUI, go to Diagnostics >> Edit File. Open up /etc/inc/dyndns.class
Copy and paste that wonderfully punny repository's dyndns.class' contents.
Save and then go restart your dyndns configuration by going to DynaicDNS service and click the "stop service" next to that particular DDNS config, and then start it back up.

Enjoy

This worked well! Thank you kindly! :)

Actions

Also available in: Atom PDF