33
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 06 Aug 2026
33 points (94.6% liked)
homeassistant
20436 readers
25 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.
Home Assistant can be self-installed on ProxMox, Raspberry Pi, or even purchased pre-installed: Home Assistant: Installation
Discussion of Home-Assistant adjacent topics is absolutely fine, within reason.
If you're not sure, DM @GreatAlbatross@feddit.uk
founded 3 years ago
MODERATORS
That wouldn't work for this...
A domain, a full fledged one or a free dyndns subdomain tells the world how to communicate with your ip, but it isn't involved when you talk to the world.
When your software is hitting the API from your network, all the API sees is your IP address, it has no knowledge of any urls that may point to it.
OP just needs to hope their IP address doesn't change regularly, and give them their public IP to whitelist.
Seems to be working fine for my VPN tunnel I use to get access to my home network, instead of an IP, it has the hostname + port to connect to it and technically I do have a non static IP. The hostname gets resolved via noip.com in this case to an IP address.
That's kind of irrelevant for a third party resolving where network traffic is coming from. They aren't connecting to OP, OP is connecting to them. Assuming their firewall even supports reverse DNS lookups, it'd actually resolve to something like .res.ispdomain.com or something weird. And since it's dynamic there'd be no consistent domain to give.