dynip

4 ms·

1. 31.▲
   by dynip 4mo ago

   Thanks for looking out and letting me know!
2. 32.▲
   by dynip 4mo ago

   Yes, I have been thinking about that as well and have unpkg / tailwindcss.com in the backlog. good point, appreciated. Cloudflare is a bigger backlog item because of the current infrastructure build.
3. 33.▲
   by dynip 4mo ago

   Tailscale is awesome, and Netbird is awesome, and Wireguard is awesome. It is a great time to be alive for sure. I have a guide that I wrote https://dynip.dev/guides/tailscale where I explain how and why they can exist
4. 34.▲
   by dynip 4mo ago

   The geo sync updates are handled with distributed keys over internal api, here is the documentation for powerdns around it: https://doc.powerdns.com/authoritative/dnsupdate.html#dnsupd... so the updates are pushed and
5. 35.▲
   by dynip 4mo ago

   Thanks! Hope there is room for something fresh and flexible! And yes, BIND allows for a lot of different things, RFC 2136 being one of them and I have been looking at multiple options before settling down on the current structure. I built a
6. 36.▲
   by dynip 4mo ago

   There are multiple multiples :) both (hidden) primary and secondaries are multiple, snapshots every 20 minutes and forward-update functionality from the secondaries with replicated tsig over powerdns api every 120 seconds. since they are st
7. 37.▲
   by dynip 4mo ago

   "Long-lived token" means API tokens for the management API (creating/ deleting zones, listing them, automating via Terraform-style flows), not the TSIG keys for actual DNS updates. Every zone on every tier gets its TSIG key
8. 38.▲
   by dynip 4mo ago

   "Long-lived token" means API tokens for the management API (creating/ deleting zones, listing them, automating via Terraform-style flows), not the TSIG keys for actual DNS updates. Every zone on every tier gets its TSIG key
9. 39.▲
   by dynip 4mo ago

   Yep, this is also true for dyndns curl/wget/fetch, have a look at the /docs on other special things that we can do except those. there is a larger functionality base here that I try to cover and not only (but including) curl&
10. 40.▲
    by dynip 4mo ago

    yep sounds valid, keeps the internet traffic nice and secure
11. 41.▲
    by dynip 4mo ago

    Skål!
12. 42.▲
    by dynip 4mo ago

    Best use case! Check the snippets after you create a zone, hopefully less hacky scripts :D
13. 43.▲
    by dynip 4mo ago

    One of my things are that I am an engineer and I build functionality for engineers, this has always been the case. I am bad with visualizing this so the vue framework has helped tremendously with that. With that said, I hope as well that it
14. 44.▲
    by dynip 4mo ago

    I did the same! back when DNS was new and exciting and not a full on requirement for everyhing you touch nowadays. I have been thinking about that since then really and finally thought I would bring some of that back! Thanks for being awwes
15. 45.▲
    by dynip 4mo ago

    But you do touch DNS :) and the idea here is to create as little friction or easy setup as possible with either fixed, dynamic or unknown ips. One example I used it for just a few days ago was to set up dual ipsec tunnels for redundancy in
16. 46.▲
    by dynip 4mo ago

    Thanks — external-dns + RFC 2136 is a great call. Honestly that's a guide we should write; we already have one for fleet operations and the k8s pattern is the natural extension.
17. 47.▲
    by dynip 4mo ago

    lol, we can probably figure something out :)
18. 48.▲
    by dynip 4mo ago

    There are a few things to think about yes, I actually post in the fleet guide parts of it that it should be considered before posting. the dns rebind issue but that should be controlled by host header validation, CSRF, same-site cookies etc
19. 49.▲
    by dynip 4mo ago

    Thanks, I am very happy with it. Reading the /guides or /docs myself actually feels good. inside the dashboard I have built a "snippets" javascript that creates the config for you. I mostly live in the cli myself so most
20. 50.▲
    DynIP – Dynamic DNS with RFC 2136, IPv6, DNSSEC, and BYOD(dynip.dev)

    341 points by dynip 4mo ago|128 comments
21. 51.▲
    by dynip 4mo ago

    I'm Daniel, network engineer in Sweden. Built DynIP because every DDNS service I tried was designed around 2010-era networks: proprietary HTTP-only update protocols, poor IPv6, no DNSSEC, little support for actuallymodern devices. What