Topics

1

24.7 Production Series / DDNS with Porkbun - Req to update API hostname

« on: November 06, 2024, 11:48:26 pm »

I've been using the ddclient backend with Porkbun for some time now and its been working flawlessly.  I've recently have been getting notifications from my Porkbun account that the API Hostname is going to be changed and that if I dont update the API hostname that the API will cease to work and it gives me a deadline of 12/1/24 to sort this out.

Is it possible someone can update the os-ddclient plugin to reflect this change please?  The letter I received is pasted below.

Code: [Select]

Hello there,

The reason you are receiving this email is because you have an API key associated with your account and are sending commands to a deprecated API hostname. We sent a previous warning on 2024-10-11. In order to ensure that any apps or tools you may have that utilize our API continue to work, we wanted to let you know about some upcoming critical updates.

We know these kinds of changes are annoying but the time has come to separate the processing of incoming API commands from our website. In previous documentation the hostname porkbun.com was used for the API but we have recently updated it to api.porkbun.com and in the near future will start enforcing its use. Please update the hostname for our API to api.porkbun.com as soon as possible.

CRITICAL UPDATE DETAILS

Type: API Hostname Change

Old Value: porkbun.com

New Value: api.porkbun.com

Deadline: 2024-12-01 00:00:00 UTC

Please note that after the deadline, API calls made to the old hostname will no longer be allowed. If you have any questions or concerns please contact support.


Thank you,
The Porkbun Team

2

24.7 Production Series / Problem with DDClient and its new Widget.

« on: August 06, 2024, 08:01:24 pm »

I get this with the new widget in the attached picture, a blank space with no IP for Current IP or a Date and Time for Updated.  I've obscured the hostname.  I'm pretty sure there's just an issue with how the ddclient.cache file is generated on my opnsense.  I've uninstalled and reinstalled the plugin but I still get this blank in the plugin.  Everything is working fine with ddclient otherwise and I'm getting successful updates in the logs using Porkbun API as a service.

My ddclient.cache file looks like this:

## ddclient-3.11.2
## last updated at Mon Aug  5 09:34:24 2024 (1722864864)
host=host.domain.com host.domain.com


In Services: Dynamic DNS: Settings, the Current IP and Dated are blank there as well.

Code: [Select]

2024-08-06T12:48:22-04:00 Notice ddclient SUCCESS: updating ipv4: skipped: host.domain.com address was already set to xxx.xxx.xxx.xxx.
2024-08-06T11:48:21-04:00 Notice ddclient SUCCESS: updating ipv4: skipped: host.domain.com address was already set to xxx.xxx.xxx.xxx.
2024-08-06T10:48:21-04:00 Notice ddclient SUCCESS: updating ipv4: skipped: host.domain.com address was already set to xxx.xxx.xxx.xxx.
2024-08-06T09:48:20-04:00 Notice ddclient SUCCESS: updating ipv4: skipped: host.domain.com address was already set to xxx.xxx.xxx.xxx.
2024-08-06T08:48:20-04:00 Notice ddclient SUCCESS: updating ipv4: skipped: host.domain.com address was already set to xxx.xxx.xxx.xxx.
2024-08-06T07:48:19-04:00 Notice ddclient SUCCESS: updating ipv4: skipped: host.domain.com address was already set to xxx.xxx.xxx.xxx.
2024-08-06T06:48:18-04:00 Notice ddclient SUCCESS: updating ipv4: skipped: host.domain.com address was already set to xxx.xxx.xxx.xxx.
2024-08-06T05:48:17-04:00 Notice ddclient SUCCESS: updating ipv4: skipped: host.domain.com address was already set to xxx.xxx.xxx.xxx.
2024-08-06T04:48:16-04:00 Notice ddclient SUCCESS: updating ipv4: skipped: host.domain.com address was already set to xxx.xxx.xxx.xxx.
2024-08-06T03:48:15-04:00 Notice ddclient SUCCESS: updating ipv4: skipped: host.domain.com address was already set to xxx.xxx.xxx.xxx.
2024-08-06T02:48:14-04:00 Notice ddclient SUCCESS: updating ipv4: skipped: host.domain.com address was already set to xxx.xxx.xxx.xxx.
2024-08-06T01:48:13-04:00 Notice ddclient SUCCESS: updating ipv4: skipped: host.domain.com address was already set to xxx.xxx.xxx.xxx.
2024-08-06T00:48:12-04:00 Notice ddclient SUCCESS: updating ipv4: skipped: host.domain.com address was already set to xxx.xxx.xxx.xxx.
2024-08-05T23:48:11-04:00 Notice ddclient SUCCESS: updating ipv4: skipped: host.domain.com address was already set to xxx.xxx.xxx.xxx.
2024-08-05T22:48:10-04:00 Notice ddclient SUCCESS: updating ipv4: skipped: host.domain.com address was already set to xxx.xxx.xxx.xxx.
2024-08-05T22:34:37-04:00 Notice ddclient SUCCESS: updating ipv4: skipped: host.domain.com address was already set to xxx.xxx.xxx.xxx.
2024-08-05T22:34:37-04:00 Notice ddclient RECEIVE: {"status":"SUCCESS","cloudflare":"enabled","records":[{"id":"399246864","name":"host.domain.com","type":"A","content":"xxx.xxx.xxx.xxx","ttl":"600","prio":"0","notes":null}]}
2024-08-05T22:34:37-04:00 Notice ddclient RECEIVE:
2024-08-05T22:34:37-04:00 Notice ddclient RECEIVE: content-language: en-US, en
2024-08-05T22:34:37-04:00 Notice ddclient RECEIVE: referrer-policy: origin
2024-08-05T22:34:37-04:00 Notice ddclient RECEIVE: x-xss-protection: 1; mode=block
2024-08-05T22:34:37-04:00 Notice ddclient RECEIVE: x-content-type-options: nosniff
2024-08-05T22:34:37-04:00 Notice ddclient RECEIVE: x-frame-options: sameorigin
2024-08-05T22:34:37-04:00 Notice ddclient RECEIVE: strict-transport-security: max-age=63072000; includeSubDomains; preload
2024-08-05T22:34:37-04:00 Notice ddclient RECEIVE: pragma: no-cache
2024-08-05T22:34:37-04:00 Notice ddclient RECEIVE: cache-control: no-store, no-cache, must-revalidate
2024-08-05T22:34:37-04:00 Notice ddclient RECEIVE: expires: Thu, 19 Nov 1981 08:52:00 GMT
2024-08-05T22:34:37-04:00 Notice ddclient RECEIVE: set-cookie: BUNSESSION2=ck1; path=/; secure; HttpOnly; SameSite=Lax
2024-08-05T22:34:37-04:00 Notice ddclient RECEIVE: server: openresty
2024-08-05T22:34:37-04:00 Notice ddclient RECEIVE: set-cookie: AWSALBCORS=ck1; Expires=Tue, 13 Aug 2024 02:34:37 GMT; Path=/; SameSite=None; Secure
2024-08-05T22:34:37-04:00 Notice ddclient RECEIVE: set-cookie: AWSALB=ck1; Expires=Tue, 13 Aug 2024 02:34:37 GMT; Path=/
2024-08-05T22:34:37-04:00 Notice ddclient RECEIVE: content-type: application/json
2024-08-05T22:34:37-04:00 Notice ddclient RECEIVE: date: Tue, 06 Aug 2024 02:34:37 GMT
2024-08-05T22:34:37-04:00 Notice ddclient RECEIVE: HTTP/2 200
2024-08-05T22:34:37-04:00 Notice ddclient SENDING: data="{\"secretapikey\":\"sk1\",\"apikey\":\"pk1\"}"
2024-08-05T22:34:37-04:00 Notice ddclient SENDING: header="Content-Type: application/json"
2024-08-05T22:34:37-04:00 Notice ddclient SENDING: url="https://porkbun.com/api/json/v3/dns/retrieveByNameType/domain.com/A/host"
2024-08-05T22:34:37-04:00 Notice ddclient SENDING: request=POST
2024-08-05T22:34:37-04:00 Notice ddclient SENDING: max-time=120
2024-08-05T22:34:37-04:00 Notice ddclient SENDING: connect-timeout=120
2024-08-05T22:34:37-04:00 Notice ddclient SENDING: user-agent="ddclient/3.11.2"
2024-08-05T22:34:37-04:00 Notice ddclient SENDING: include
2024-08-05T22:34:37-04:00 Notice ddclient SENDING: silent
2024-08-05T22:34:37-04:00 Notice ddclient SENDING: Curl system cmd to https://porkbun.com
2024-08-05T22:34:37-04:00 Notice ddclient UPDATE: updating host.domain.com
2024-08-05T22:34:37-04:00 Notice ddclient INFO: setting ipv4 address to xxx.xxx.xxx.xxx for host.domain.com
2024-08-05T22:34:37-04:00 Notice ddclient WARNING: 'if-skip' is deprecated and does nothing for IPv4


3

General Discussion / Raspberry Pi Stratum 1 PPS NTP Time Server

« on: September 22, 2023, 04:55:02 am »

Not exactly OPNsense related but since a lot of people run PiHole and OPNsense, I thought this YouTube tutorial was just as relevant as an NTP Time Source within your own local network.  It can get your NTP delay measured in nanoseconds as opposed to the milliseconds that most NTP Sources provide. 

In my attached pic you can see how low the delay is compared to the pool.ntp.org and NIST Servers provide.

It uses a Raspberry Pi and a GPS module with PPS signal to get a very accurate time and synchronize clocks over your network.

https://youtu.be/7aTZ66ZL6Dk?si=hhHNEFYC4jmrvbKy

4

19.7 Legacy Series / System: Settings: Tunables Duplicates and Missing entries 19.7.5

« on: October 12, 2019, 09:48:07 pm »

I upgraded to 19.7.5 so not sure when this started but if I create a new Tunable, the setting seems to take effect but the Tunable will not be listed with the others.

Also, there are two entries for net.inet.ip.redirect duplicated.  If I delete one, then there will then be a duplicate entry for security.bsd.see_other_uids which is the Tunable right above it. 

Yes, I've already tried using the Default button and it re-creates the same behavior.  I see this on all 3 of my boxes.

Strange, can anyone else confirm?