@dumbergerl I switched from #Duckdns to #Dynu, first their free version and then switched to the paying version as needed more than four addresses, works perfectly and use it with the IP update client running in the background, Perfect 👍
@dumbergerl I switched from #Duckdns to #Dynu, first their free version and then switched to the paying version as needed more than four addresses, works perfectly and use it with the IP update client running in the background, Perfect 👍
Hey #homeassistant Community,
i currently use #DuckDNS for my Homeassistsnt that is running on a Raspberry Pi to reach it from the Internet. I have a #FritzBox as Router.
I often have connection problems. Do any of you have a good and stable alternative? Or ideas how to fix connection issues for DuckDNS?
🆕#blog🆕
ZeroTier – home VPN without a public IP address [ENG 🇬🇧]
👇👇👇👇👇
https://blog.tomaszdunia.pl/zerotier-eng/
#️⃣#️⃣#️⃣#️⃣#️⃣
#Android #DHCP #DuckDNS #DynamicDNS #HomeAssistant #iOS #IoT #NabuCasa #NoIP #OpenVPN #SelfHosted #VPN #Wireguard #ZeroTier
🆕#blog🆕
ZeroTier – domowy VPN bez publicznego adresu IP
👇👇👇👇👇
https://blog.tomaszdunia.pl/zerotier/
#️⃣#️⃣#️⃣#️⃣#️⃣
#Android #DHCP #DuckDNS #DynamicDNS #HomeAssistant #iOS #IoT #NabuCasa #NoIP #OpenVPN #SelfHosted #VPN #Wireguard #ZeroTier
DuckDNS is down. Website has been updated. #duckdns
@kevinctofel I use a couple Pis for everything which seems to work well. home assistant as the nginx host pointing to everything else. but it is whackamole for sure. today my ddns solution is down (#duckdns). might get my own domain just for home stuff, which I had been thinking of doing for a while
I've had troubles and downtimes of my #selfhosted external services on a daily basis and for quite some time now. Decided to try another #DynDNS provider and switches from #duckdns to #ipv64. Everything looking real good and I haven't had any downtime since yesterday.
Today's battle: renew a #LetsEncrypt certificate when I use #DuckDns and don't have an #ipv6 address...
What's up with #duckdns 😑
#duckdns is down again maybe those backup services would have been a smart idea wile i could ssh into my server.
I found out my gopherhole (and possibly server in general) has high latency because of #duckdns latency.
I will be switching to afraid.org.
des utilisateurs de #duckdns par ici ?
Je me demande s'il n'y a pas des problèmes chez eux ce soir. Mon nom de domaine se résoud de manière aléatoire (ou très lente).
boost apprécié pour atteindre les plus geek d'entre vous.
A cette occasion, je découvre ce site qui porte bien son nom :
i have been using #duckdns since… forever. unfortunately, in the beginning i've opted for twitter id as my authentication method, — for some years now i've only kept twitter profile only for this! now, there's no clear way to migrate to another id provider, no is there an id option independent of external services.
thus the question: are there dynamic dns services out there like duckdns (donation based) but with email registration?
#Homeassistant-erfahrene #Netzwerk-Gurus hier?
Mein Homeassistant soll per #LetsEncrypt-Zertifikat über #HTTPS erreichbar sein. Das funktioniert auch nach Anleitung schon über #DuckDNS (einigermaßen – die interne Verbindung zickt, aber das ist zweitrangig). Ich hab eine Domain bei Strato, und einen CNAME-Record gesetzt, der auch aufgelöst wird – aber das Homeassistant-Letsencrypt-Plugin mag ihn nicht.
DynDNS hätte ich auch direkt über Strato, und hass.mydomain.de wär besser als name.duckdns.org…
Impostiamo un #DNS #Dinamico (#DynHost #DynDNS) con #DuckDNS per accedere ai nostri servizi da fuori, senza preoccuparci dell'IP Dinamico, in maniera #semplice e #veloce:
https://www.risposteinformatiche.it/configurare-dns-dinamico-duckdns-raspberry-pi/
#UnoLinux #IP #Server #raspberrypi #linux #RaspberryPiOS #curl #developers #services #access
Habe auf #HomeAssistant nun #LetsEncrypt und #DuckDNS laufen und hat (mit etwas Bastelei) funktioniert. Ich hatte zuvor eigene Zertifikate und es hatte sich etwas verhakt.
Danach hatte #deCONZ seine Zusammenarbeit aufgekündigt. Ich konnte aber schnell herausfinden, dass das wohl ein bekannter Fehler ist (falsche IP Autokonfig, die nicht mehr auf den Container zeigte) und man mit einem beherzten Eingriff in einer JSON config-Datei der Integrationen das Problem beseitigen kann.
Langsam wird es.
Q: When I will learn to start checking for the cause of weird network related problems from the DNS?
A: As soon, as I stop using the crappy provider-given router as wifi access point, which is always my first suspect.
Narrator: it was DNS. It seems #duckdns has some hiccups.
Anyone using #duckdns? Could you check, if your name is resolving?