dynip

Joined 6 months ago

Karma

222

Submissions

51

Member since

Apr 28

View on Hacker News

Recent submissions

Comment · 5 months ago

Your stuff also looks interesting for sure, you have some things that I have on my backlog. regarding my API keys I use python for the per-account access in bearer style and the TSIG keys work as per zone directly to PowerDNS. I only use the powerdns api on the hidden primary setup so the secondaries can run individual zone cleanup, tsig replicatio, axfr meta data etc as sidecars and forward replication for dns updates.

was there anything in particular you were thinking?

Comment · 5 months ago

Back again, "works easily" was a bit of an understatement :D at least when securiting the zones with TSIG sha256 and moving keys around in a secure maner (I had previously used md5 because of compability with fortigate) there is full support now to the extent that I can test with rfc 2136, there is a guide and docs available at https://dynip.dev/docs#integration-external-dns and https://dynip.dev/guides/external-dns and a complete snippet generator. Read the notes as there are a few considerations on policy and depending on mode.

Please have a go if you can and report back if you feel like it

Thanks!

Comment · 5 months ago

Did a manual validation, have a go :)

Comment · 5 months ago

I triggered a resend on all emails that was not verified so possibly you have a new validation token available.

Comment · 5 months ago

Give me you address and I will have a look

Comment · 5 months ago

Well, if your current gripe is no Let's encrypt with NO-IP, then you have just found something that stands out for you :)

Comment · 5 months ago

Marking as fixed, was a prior html change that i overlooked

please have a go but right now it should not matter if you are logged in or not, the reset_token takes precedence.

Thanks for reporting!

Comment · 5 months ago

Thanks, will look into what the best path would be. adding to the bugs list :)

Comment · 5 months ago

mycket viktigt :)

Have not come in contact with Hickory DNS before, looks pretty solid

Comment · 5 months ago

Hi, just wanted to check in again to clarify this a bit. TSIG keys are used for both the api and the direct dns update, this is what authenticates the request and tied to a specific domain. the bearer (long and short) are for the account and is tied to you rather than a specific domain. https://dynip.dev/docs#api-register - you can also list current keys etc for the different domains.

https://dynip.dev/docs#authentication

TSIG Keys: Used strictly for updating DNS records (/update). These are 44-character Base64 encoded strings generated per-zone.

JWT Bearer Tokens: Used for account management and programmatic zone registration (/register). Generated upon user login.

Hope this helps to clear it up, I might link the documentation from the pricing section so that at least there is clarification on it.

Comment · 5 months ago

Comment · 5 months ago

Good points, don't be sorry. At this point in time there are knowns and unknowns, hopes and dreams and a big chunk of tech knowledge. Not as big on the design part but I think its ok for now

Comment · 5 months ago

It has to do with the .dev root zone that needs to have these as records, I am on it but it might take a few days to get those records up. Or it could be fast. Glad that you reported and I will report back when we expect it to work

Comment · 5 months ago

Interesting, will do some digging on what sets them apart from the x amount of byod already precent. Thanks for letting me know!

Comment · 5 months ago

Wow, that sounds like a great idea. I wanted it to be easy with the paddle integration but even that was a pain. Will look into it for sure, thanks!