Skip to content

Conversation

@theAeon
Copy link
Contributor

@theAeon theAeon commented Jun 16, 2025

This should be enough to get dynamic dns working. I say should because I haven't tested it just yet.

As far as remaining types go, libdns provides CAA/MX/SRV/ServiceBinding/SvcParams, all of which require further parsing and may be best saved for later.

these are the types that do not require further parsing
@theAeon
Copy link
Contributor Author

theAeon commented Jun 16, 2025

pardon the force pushes

@theAeon
Copy link
Contributor Author

theAeon commented Jun 17, 2025

2025/06/17 15:26:47.177	INFO	dynamic_dns	domain not found in DNS	{"domain": "robbinsa.me", "type": "A"}

2025/06/17 15:26:47.235	INFO	dynamic_dns	updating DNS record	{"zone": "robbinsa.me", "type": "A", "name": "@", "ip": "75.46.42.113", "ttl": 3600}

2025/06/17 15:26:47.290	INFO	dynamic_dns	finished updating DNS	{"current_ips": ["75.46.42.113"]}

Seems setting is working, but checking is not. Bizarre.

Weirder still is that it was failing to look up the host by name (this log is by ID), which is presumably causing the check failure.

@mholt was the ZONE api changed in 1.0?

@mholt
Copy link

mholt commented Jun 17, 2025

@theAeon Do you mean like the ZoneLister interface? I don't think so.

@theAeon
Copy link
Contributor Author

theAeon commented Jun 17, 2025

Yeah, that one.

Wonder if thats a bug internal to the plugin. I suppose its worth testing w/ 2.9/released version

@mholt
Copy link

mholt commented Jun 17, 2025

It could definitely be a bug in the dynamic-dns plugin. 🤷‍♂️ (Sorry I've been a bit too busy to look into it!)

@theAeon
Copy link
Contributor Author

theAeon commented Jun 17, 2025

It could definitely be a bug in the dynamic-dns plugin. 🤷‍♂️ (Sorry I've been a bit too busy to look into it!)

no worries-"update every time despite failing checks" is still functional!

@oliwer
Copy link

oliwer commented Jul 10, 2025

Maybe we could also bump the libdns dependency to v1.1.0 while we're at it?

@theAeon
Copy link
Contributor Author

theAeon commented Jul 11, 2025

would rec. just doing it after merging the pr tbh

@AndrianBdn
Copy link
Collaborator

While working on #289 I fixed several things - including proper libdns types. I think that PR provides stronger coverage support overall. I acknowledge you were ahead of me here - it wasn’t my intention to duplicate your work.

@theAeon
Copy link
Contributor Author

theAeon commented Sep 22, 2025

No worries-this was mostly for my own sake. If you have better coverage you have better coverage.

@theAeon
Copy link
Contributor Author

theAeon commented Sep 22, 2025

closing in favor of #289

@theAeon theAeon closed this Sep 22, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants