ukConnect a home server with uk.app and dynamic DNS
A name such as home.uk.app can point to your own server. Registration provides the name and DNS management; your network and server must accept the connection.
1. Check network access
Find your public IPv4 or IPv6 address and check whether your router can accept inbound traffic. Carrier-grade NAT commonly prevents direct inbound IPv4 connections. An A record cannot bypass it: arrange a public address with your ISP or use a compatible connectivity service.
2. Replace the parking record
Open your name in the dashboard. For IPv4, change the A record at host @ to your public address. For reachable IPv6, add an AAAA record. Remove stale or unreachable routing records. The @ host means your registered name, not uk.app itself.
If you want names beneath it, create the appropriate records; a wildcard host * applies to otherwise unmatched subnames. Do not remove MX or TXT records belonging to an existing mail or verification setup.
3. Configure the destination
Set your reverse proxy or web server to accept the full hostname. Forward the required ports at your router and allow them through the firewall. Browsers require HTTPS for .app names, so install a valid certificate for the hostname.
4. Handle changing addresses
Generate a DDNS token on the name's page. Configure a dyndns2-compatible client with update server ddns.uk.app, path /nic/update, username equal to the full name, and the DDNS token as the password. Use HTTPS. Keep this token private and revoke it if exposed.
See the DDNS protocol examples for clients that require a custom update URL.
5. Verify
Run the dashboard's domain health check. Correct DNS with an HTTP 403 response points to destination access rules or hostname configuration. A certificate mismatch points to HTTPS configuration. Test from outside your home network as well, because local NAT behaviour can differ.