Free Dynamic DNS Service: How to Choose and Set Up

A free dynamic DNS service keeps a hostname pointed at your changing public IP address, so you can reach a home server or VPN without memorizing a new number after every ISP change. It only works when an updater can report your address and your connection accepts incoming traffic. A hostname alone cannot get you past carrier-grade NAT.
Before you pick a provider, check your address on Loqmi. Then compare it with the WAN or Internet address shown in your router. Compare the same IP version: IPv4 with IPv4, or IPv6 with IPv6. If those addresses differ, your router may sit behind another NAT layer. After forwarding a service, test its TCP port with Loqmi’s port checker; the hostname alone cannot confirm reachability. That small check can save an evening of fiddling with DDNS settings that were never the problem.
What dynamic DNS does (and what it does not)
DNS, the Domain Name System, turns a hostname such as garage.example.net into an IP address. A dynamic DNS updater tells the provider when that address changes, and the provider updates the hostname's DNS record. The DNS UPDATE protocol is standardized in IETF RFC 2136. Consumer providers, though, often use their own authenticated HTTPS update APIs instead.

Your ISP (internet service provider) may give your router a public address that changes. DHCP, the Dynamic Host Configuration Protocol, hands out addresses on a lease, but a lease does not mean the address changes on a fixed schedule. Think of a hostname like a contact name in your phone: the number behind it can change, and the name still reaches the same person. For the difference between address types, see static versus dynamic IP addresses.
DDNS does not create a secure connection, forward a port, or make a device reachable through every ISP. It is the signpost, not the road. If remote access is your goal, you may need a router rule that forwards a specific service to a device on your LAN (local area network), or a VPN endpoint; see how port forwarding works.
How to choose a free dynamic DNS service
Many dynamic DNS services give you either a provider-owned subdomain or a way to update a domain you already own. Free tiers change, so check the current terms rather than trusting a provider’s old reputation. Look at the details that affect your setup:
| Your need | Check before signing up | Why it matters |
|---|---|---|
| One remote connection | Does the free plan include a hostname, and must you renew or confirm it? | A low-maintenance name is useful only if it stays active. |
| Router updates | Does your router list the provider, or support a compatible custom updater? | A built-in client avoids leaving a computer running solely to send updates. |
| Your own domain | Can you update its A or AAAA record, and does the provider support your DNS host? | A free hostname and free hosting for a domain you own are different offers. |
| IPv6 or several services | Are IPv6 updates and the record types you need included? | Feature labels vary; check the updater and record limits for your exact plan. |
A records point to IPv4 addresses, and AAAA records point to IPv6 addresses. A record’s TTL (time to live) partly controls how long caches keep an answer, so a newly updated address may take a while to appear everywhere. DNS caches do not check your new forwarding address just because you asked politely. Cloudflare’s TTL guide explains why a cache can keep an answer until its timer runs out.
DuckDNS, Dynu, and No-IP, for example, publish different mixes of hostnames, router compatibility, and update methods. Treat them as candidates, not endorsements. A provider’s current renewal, security, record, and account-recovery rules matter more than a stale ranking. If you already own a domain, ask whether your DNS host offers an API updater. That may be simpler than adding another provider.
Check whether your home connection is reachable
Check Loqmi’s public IP at the IP lookup page, then sign in to the router and find its WAN/Internet address. If they match, your router probably has the public IPv4 address. If the router shows a private address such as one in 10.0.0.0/8, 172.16.0.0/12, or 192.168.0.0/16, another router or provider network sits in front of it. RFC 1918 reserves those ranges for private networks.
If the WAN address starts in 100.64.0.0/10, it sits in the shared address space reserved for carrier-grade NAT (CGNAT), as described by RFC 6598. A private WAN address can also mean ordinary double NAT. Ask your ISP or check the upstream router before deciding which one you have. Either way, a DDNS update can succeed while unsolicited inbound connections still fail. Ask the ISP whether it can give you a public address, or use a supported outbound VPN/tunnel approach instead.
For more background, read what CGNAT is and how public and private IP addresses differ. Comparing the public address with the router’s WAN address tells you more than restarting the updater over and over. Restarting feels productive because something visibly happens (a spinning icon is very reassuring). It is not a diagnosis.
Set up the hostname and updater
- Create the hostname. Register with a provider, then pick its free hostname or connect a domain you own. Note the exact host name and update method.
- Pick one updater. In your router, look under Internet, WAN, Network, or Dynamic DNS. Names differ by manufacturer and firmware, so expect a little hunting. Enter the provider, the hostname, and the account credential or update token it requires. A TP-Link guide, for example, shows one model’s menu path, and other routers may put DDNS somewhere else.
- Use a client if needed. If the router does not support that provider, install its official updater on a device that stays on, such as a home server. Avoid running several updaters for one hostname. A misconfigured client can overwrite the correct record.
- Protect the credential. Treat update passwords and API tokens like account passwords. Use a token limited to the required DNS record if the provider supports that, keep it out of public scripts and screenshots, and revoke it if exposed.
- Test from outside. Check the provider dashboard for the current address, then query the hostname with
nslookupordig. Compare the answer with Loqmi’s public IP. Then test the service from mobile data or another external network, since a router may not support connecting back to its own public hostname from inside.
Quick check: Load Loqmi on the home connection, then compare its public IP with the hostname’s DNS answer. If they match but remote access fails, look next at port forwarding, the device firewall, and ISP restrictions before you recheck the spelling of the hostname.
Troubleshoot by symptom
| Symptom | Likely cause | Next check |
|---|---|---|
| Hostname returns an old IP | Updater is offline, credentials were rejected, or DNS cache has not expired. | Check updater status and the provider dashboard; then allow the record TTL to pass before testing again. |
| Name matches public IP, service times out | Missing port-forward rule, local firewall, service not listening, or ISP filtering. | Test from another network and verify the chosen service port and destination device. |
| Router WAN differs from Loqmi | Double NAT or CGNAT means the router may not receive the public address. | Identify the upstream device and ask the ISP about public IPv4 or IPv6 access. |
| Name works on mobile data, not at home | Router may lack NAT loopback, also called hairpin NAT. | Test from outside; use a local DNS override or local address at home if appropriate. |
A DDNS hostname does not hide your public IP. Anyone who can resolve it can see the address it points to, and a hostname by itself does not encrypt traffic. Do not expose router administration or a device’s management page directly to the internet. Use current software and strong authentication, and expose only the specific service you intend to reach. If privacy is the goal, DDNS is no substitute for hiding your IP address.
Key takeaways
- DDNS updates a hostname when your public IP changes; it does not create internet reachability.
- Compare the router’s WAN address with Loqmi’s public address before troubleshooting the provider.
- Choose based on hostname or domain needs, updater support, renewal rules, IPv6, and record limits.
- Verify the DNS answer and test the service from outside your home network.
- Protect update credentials and expose only the service you deliberately intend to access.
Frequently asked questions
Is dynamic DNS the same as changing my DNS server?
No. A DDNS updater changes the address record for a particular hostname when your public IP changes. Changing your DNS server changes which resolver your device asks to look up names. One edits a destination record; the other changes the service that answers your lookups.
Will a DDNS hostname hide my public IP address?
No. A hostname normally resolves to the address where your connection can be reached, so it can make that address easier to discover. DDNS is a convenience for routing to a changing connection, not a privacy tool. Use a VPN or a carefully configured private access service when you want to restrict who can connect.
Does dynamic DNS work with IPv6?
It can, if the provider, updater, and destination device all support IPv6 updates. The provider may update an AAAA record rather than an IPv4 A record. IPv6 connectivity and firewall rules work differently from IPv4 port forwarding, so check your router and ISP support before relying on it.
Why does a DDNS name sometimes keep showing the old address?
The updater may not have reported the new address, or a resolver may still have the old answer cached until its DNS time to live expires. Check the provider dashboard first, then query the hostname with a public DNS lookup tool. If the dashboard is current but your device is not, wait for caching to expire or test from another network.