Use FQDN

Use Fully Qualified Domain Names

Using a Fully Qualified Domain Name (FQDN) instead of an IPv4 address for devices is now supported. To use it, enter the FQDN instead of the IP and UpSnap will take care of the rest.

• Window/MacOS hosts - FQDN will work without additional configuration

• Linux/FreeBSD hosts - FQDN with .local domains requires dbus and avahi

• Docker - FQDN with .local domains requires dbus and avahi on the Docker host, and /var/run/dbus/system_bus_socket must be mounted readonly in the container. Refer to the example here.

  Make sure you understand the risks associated with mounting dbus in a Docker container before doing so. It is highly recommended to secure your container with strong docker-compose settings if you choose to mount dbus.

Important notes

• For the best reliability for wake/shutdown and realtime monitoring of device power on status, using static IPv4 addresses is the recommended configuration.
• Single name hostnames (without a ".") are not supported. You must provide a FQDN such as mydevice.local or mydevice.mydomain.com and it must be resolvable to an IPv4 address.
• Devices with .local domains are resolved using mDNS. As such, it has the potential to cause a multicast network "storm" if there are many UpSnap devices configured with it, or if there are many other devices listening for mDNS queries on the network. This may also potentially impact WiFi devices and prevent certain devices from going into low-power/standby. This is because UpSnap needs to continously ping each device (default: every 3 seconds.) When a .local is used, an mDNS query is sent every 3 seconds for each device. Therefore, the impact on your network may vary, so see what works for your setup. Use .local FQDNs sparingly!
• Devices using any other domain e.g. mydevice.mydomain.com are resolved using normal DNS lookups and shouldn't have issues.
• Devices with FQDN cannot use the IP Tracking feature, for obvious reasons.