homeassistant

11896 readers

51 users here now

Home Assistant is open source home automation that puts local control and privacy first. Powered by a worldwide community of tinkerers and DIY enthusiasts. Perfect to run on a Raspberry Pi or a local server. Available for free at home-assistant.io

founded 1 year ago

MODERATORS

[email protected]

Duckdns/wireguard/... Which one do you prefer and why? (jlai.lu)

submitted 16 hours ago by [email protected] to c/homeassistant

31 comments fedilink hide all child comments

Hi everyone

So, that's a 2 in 1 post. First a more general question then looking for advice for a friend.

What is your preferred way to access HA from outside (and why)?
a friend of mine use duckdns and I often read (recently) that some people are having issue with it. Is wireguard a better way or another solution that is not too techy to deal with?

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 5 points 15 hours ago (1 children)

Apples and oranges.

Wireguard is a VPN technology. DuckDNS is a service that lets you create a subdomain on the duckdns TLD and point it at your server. They do completely different things.

You would use DuckDNS if you don't want to rent your own domain ("rent" because it's a recurring payment for something over which you have only nominal control). It provides no security, no access control, and it creates no network. It's just a pointer in the global DNS DB.

Wireguard is a VPN technology, for creating private networks.

One is like a mailing address. The other is like a strongbox. You could give the strongbox to a friend to deliver it to someone who has the key (Wireguard). Or you could write a message on a postcard and mail it (DuckDNS). Or you could put the address on the strongbox and mail it (DuckDNS + Wireguard). The point is, they serve completely different functions.

The two could be used together.

[–] [email protected] 1 points 14 hours ago

Ok, so wireguard seems a better alternative for him. Thanks