Will It Work? · Guide

Dynamic DNS for a home camera or server: set up and check it

By , founder of ElectronicsInfoline (since 2000)

You set up port forwarding for a camera or a home server, it works today, and next week the address you saved stops working. Your internet provider changed your public IP address. Dynamic DNS (DDNS) fixes that by giving your home a name that follows the address. This guide is drawn from two router makers' support pages (one read on its US and India sites). Menus differ by model, so treat the paths here as examples.

Turn on DDNS in the router (one maker puts it under Advanced > Network > Dynamic DNS, the other under ADVANCED > Advanced Setup > Dynamic DNS), register a host name, and use that name with the port number instead of the IP address. The router updates the name each time the address changes. DDNS does not open anything: you still need a port-forwarding rule, and it only helps if the router's WAN address is public.

What DDNS does

Most providers give your router a dynamic IP address, which can change at any time and makes remote access unreliable (TP-Link). Dynamic DNS gives the network a name that stays the same even when the provider changes the address (NETGEAR). Once the router is set up, it puts your registered name in place of the current IP address, whatever the provider has changed it to (NETGEAR).

Dynamic DNS keeps one name pointing at an address that changesMonday: the internet provider gives the router the public address 113.116.60.229, and the name myhome.example.net points at it. Thursday: the provider changes the address to 113.116.71.40. The router's DDNS client sends the new address to the DDNS service, which updates the name. A phone outside the home still types the same name and reaches the router; the router's port-forwarding rule passes the connection to the camera.Mondaymyhome.example.net→ 113.116.60.229Thursdaymyhome.example.net→ 113.116.71.40providerchanges the addressrouterDDNS client:reports the new oneupdatecamerabehind a ruleFrom outside: type the name, not the numbermyhome.example.net:9000name → router (DDNS) → camera (port forwarding)
Figure 1. The provider can change the router's public address at any time. The router reports each new address to the DDNS service, so the same name keeps working. Port forwarding is still needed to reach a device behind the router.

Do you need it?

You need it when something outside your home has to find your home: a web server, a VPN connection to your router (NETGEAR), or a camera you reach through a port-forwarding rule. If you only browse, stream and play from inside the house, you do not.

Before you start, check the router's WAN address on its status page. A port-forwarding rule only works from the internet when that address is public (TP-Link). A private address (such as 192.168.x.x) means another box sits in front of your router. An address from 100.64.0.0 to 100.127.255.255 means carrier-grade NAT at the provider; see when port forwarding cannot work.

Set up the router’s own service

One maker builds a free DDNS service into routers with cloud functions, with names like yourhostname.tplinkdns.com (TP-Link). First sign in to the router with the maker's cloud account (it calls it an ID) and bind it; the maker says this step is required (TP-Link). Then go to Advanced > Network > Dynamic DNS, choose the maker as the provider, click Register, type a host name and save, with the router online (TP-Link). If registration fails, someone else already has that host name, so try another (TP-Link). To change the name later, click Unbind, then Register a new one (TP-Link).

The other maker runs its free names through No-IP (NETGEAR). Go to ADVANCED > Advanced Setup > Dynamic DNS (some models say Settings > Advanced Settings > Dynamic DNS), choose "Use a Dynamic DNS Service", pick the maker, say you have no account, and enter a host name such as yourname.mynetgear.com with an e-mail and password. Then open the e-mail from No-IP and click the activation link (NETGEAR).

Use an account you already have

If you already pay for a name or have a free one elsewhere, the router can update it. One maker's routers accept an existing DynDNS.org or NoIP.com account: pick your provider, then enter the host name, e-mail and password (NETGEAR). On the other maker's older menus, you enter the user name, password and domain name, tick Enable DDNS and log in (TP-Link). The list of providers differs by router, so check yours before you sign up anywhere.

Check that it works

On the DDNS page, show the status and compare the address it lists with the WAN address on the router's status page; one maker says the two must match (NETGEAR). You can also run nslookup with your host name, on your computer or from a device outside your network (TP-Link).

The other maker says the name is bound to the network's public address, and that a private WAN address on the router is no problem for the name (TP-Link). The two statements fit together. If the router's WAN address is private, the name points at the public address of the box in front, so a camera behind your router is reachable only if that box forwards the port too (TP-Link).

Read the DDNS status against the router's WAN addressFour cases. One: the WAN address is 113.116.60.229 and the DDNS page shows 113.116.60.229; they match, so the name reaches the router. Two: WAN 113.116.60.229, DDNS shows 113.116.60.12; they do not match, so the name has not been updated yet. Three: WAN 192.168.1.20, a private address; the DDNS name still points at the home's public address 113.116.60.229, which belongs to another box in front of the router, so the port must be opened on that box too. Four: WAN 100.72.15.9, inside the carrier-grade NAT range 100.64.0.0 to 100.127.255.255; the name points at the provider's shared address, and only a public address from the provider helps.router WANDDNS showswhat it means113.116.60.229113.116.60.229match: the name reaches youadd the forwarding rule113.116.60.229113.116.60.12no match: not updated yetwait, then check again192.168.1.20113.116.60.229private WAN: a box in frontopen the port there too100.72.15.9113.116.60.229shared WAN: provider NATask for a public address
Figure 2. One maker says the two addresses must match. The other says the name follows the network's public address even when the router's WAN address is private. The two fit together: a private WAN address means the name lands on the box in front of your router.

Keep a free name

The free names on No-IP must be confirmed every 30 days, or they are deleted (NETGEAR). An e-mail comes 7 days before confirmation is due; if you have not confirmed 14 days after it, the name is removed and stops resolving (NETGEAR). Counted from the last confirmation, that is day 23 for the e-mail and about day 37 for removal. A deleted name can be registered again if nobody has taken it, and a paid tier drops the confirmation (NETGEAR).

A free host name must be confirmed every 30 daysOne maker's free host names, run by its partner service. Day 0: the name is registered or last confirmed. Day 23: an e-mail arrives, 7 days before confirmation is due. Day 30: confirmation is due. If the link in the e-mail is still not clicked 14 days after the e-mail, about day 37, the name is removed and stops resolving. Clicking the link restarts the count at day 0. A paid tier removes the requirement.day 0confirmedday 23e-mail arrivesday 30confirm dueday 37name removedClick the link in the e-mail: the count starts again at day 0.
Figure 3. Day 23, 30 and 37 are worked out from the maker's three figures: confirm every 30 days, an e-mail 7 days before, removal 14 days after that e-mail. Other DDNS services have their own rules.

Tips and tricks

  • Check the router’s WAN address first. If it is private or in the 100.64 range, sort that out before you set up DDNS.
  • Add the port-forwarding rule and reserve the device’s IP address; DDNS on its own only finds the router.
  • Test the name from outside, such as a phone on mobile data with Wi-Fi off.
  • With a free name that needs confirming, add a calendar reminder for every 30 days in case the e-mail goes to spam.
  • Pick a host name that does not reveal your address or what the device is.

What we would do

We would use the DDNS service built into the router if it has one, because the router then updates the name by itself. We would check that the DDNS status matches the WAN address, add one port-forwarding rule for the camera or server, and test from a phone on mobile data. If the WAN address were private or shared, we would fix that with the provider first, since no name can reach a device behind it.

Questions people ask

What does dynamic DNS do? It gives your home network a name that stays the same while the public IP address your provider gives you changes. The router tells the DDNS service each new address, so the name keeps pointing at your home.

Do I still need port forwarding with DDNS? Yes, if you want to reach a camera, server or other device behind the router. DDNS only finds your router. A port-forwarding rule passes the connection on to the device.

Is DDNS on my router free? Some routers have a free service built in. One maker offers names like yourhostname.tplinkdns.com on routers with its cloud functions; the other offers names like yourname.mynetgear.com through its partner, No-IP. That free name must be confirmed every 30 days.

Why does the DDNS address not match my router’s WAN address? Either the name has not been updated yet, or the router’s WAN address is private. A private WAN address means another box, such as the provider’s modem router, sits in front. The name points at that box, so open the port there too.

Will DDNS work with carrier-grade NAT or 4G/5G home internet? Not for reaching a device at home. If the WAN address is between 100.64.0.0 and 100.127.255.255, the public address belongs to the provider and is shared, so a port-forwarding rule on your router cannot be reached. Ask the provider for a public IP address.

How do I check that my DDNS name works? Look at the status on the router’s DDNS page and compare it with the WAN address on the status page. Then run nslookup with the name, from your computer or from a device outside your network.

What happens if I do not confirm a free mynetgear.com name? You get an e-mail 7 days before confirmation is due. If you still have not confirmed 14 days after that e-mail, the name is removed and stops resolving. You can register it again if nobody else has taken it.

Sources

Each figure on this page is quoted from the source below or worked out from them. Sources checked , each quote read again against the source in a second pass.

  1. NETGEAR, NETGEAR KB 1058: what Dynamic DNS is: Dynamic DNS (DDNS) provides a stable domain name for a network, allowing users to consistently access a network even when an Internet service provider (ISP) might change the network’s IP address. … You might need this ability if you run your own web server, or if you use your router to make a VPN connection. … most ISPs frequently change your network's IP address, using a protocol called Dynamic Host Configuration Protocol (DHCP) … it automatically substitutes your registered host name for the current IP address, no matter what your ISP has changed it to kb.netgear.com/1058/What-is-Dynamic-DNS-DDNS
  2. TP-Link, TP-Link FAQ 1367 (US): setting up the maker’s free DDNS: Most Internet service providers (ISPs) assign a dynamic IP address to your router. This address can change at any time, which makes remote access unreliable. … TP-Link DDNS is a free DDNS service built into compatible TP-Link wireless routers, giving you a stable address like yourhostname.tplinkdns.com … This guide applies to TP-Link wireless routers with cloud functions, such as the Archer C8 V3 and Archer C9 V3/V4. … This step is required for TP-Link DDNS to work. … Go to Advanced > Network > Dynamic DNS … Make sure you have an active Internet connection when registering a TP-Link domain name. … If registration fails, the hostname you entered has already been registered by another user. Try a different hostname. … Your domain name is bound to the external public IP address of your network. … You do not need to worry if your ISP assigns a private WAN IP address (such as 192.168.1.x) to the router. … click Unbind and delete your current domain name, then click Register to bind a new one tp-link.com/us/support/faq/1367/
  3. TP-Link, TP-Link FAQ 297 (US): DDNS with a third-party account: Enter the User Name, Password, and Domain Name. Check the Enable DDNS box and click the Login to sign into the DDNS service. … You can check the connectivity by using nslookup on your computer or from a device outside your network. tp-link.com/us/support/faq/297/
  4. NETGEAR, NETGEAR KB 23860: setting up a free mynetgear.com host name: NETGEAR is partnered with No-IP to provide DDNS services. … you must confirm your host name once every 30 days or it will be deleted … Select ADVANCED > Advanced Setup > Dynamic DNS … Settings > Advanced Settings > Dynamic DNS … (for example, yourname.mynetgear.com) … open the confirmation email from No-IP and click or tap the activation link … Make sure that the IP address listed matches the WAN IP address of your router. kb.netgear.com/23860/How-do-I-set-up-a-NETGEAR-Dynamic-DNS-a…
  5. NETGEAR, NETGEAR KB 23930: using an existing DDNS account: If you already have DynDNS.org or NoIP.com DDNS service, you can use it with your NETGEAR router. … In the Service Provider menu, select your service provider. Enter your Host Name, Email, and Password. kb.netgear.com/23930/How-do-I-set-up-Dynamic-DNS-DDNS-on-my-…
  6. NETGEAR, NETGEAR KB 000064547: keeping a free mynetgear.com host name: You will receive an email 7 days before your host name requires confirmation. … If you don't confirm your host name within 14 days of receiving your confirmation notice, your host name will be removed from your account and DNS and the host name will no longer resolve. … As long as your deleted host name isn't taken by someone else after it is removed from your account, you can get it back by registering the host name with No-IP again. … upgrade to a paid No-IP Dynamic DNS service tier and remove the confirmation requirement kb.netgear.com/000064547/How-do-I-keep-my-free-mynetgear-com…
  7. TP-Link, TP-Link FAQ 1379 (US): setting up port forwarding: Port forwarding tells your router to direct incoming Internet traffic on a specific port to a device on your local network. … It is commonly used for gaming, remote access, and hosting a server or website from home. … the local IP address of the device you are forwarding to, the port number your service requires, and the protocol (TCP, UDP, or ALL) … The External Port and Internal Port are usually the same, unless you are forwarding the same port to multiple devices. … assign a static IP address to your device or use address reservation on your router … Port forwarding only works from the Internet if your router has a public WAN IP address. … Go to Forwarding > Virtual Servers … Go to Advanced > NAT Forwarding > Virtual Servers … Go to Advanced > NAT Forwarding > Port Forwarding … If you are not sure, select ALL … If you need to enter a port range (for example, xx-xx), leave the Internal Port field empty. … http://WAN IP:port number (for example, http://192.203.115.77:90) … you must first change the router's remote management port, because port 80 is the default … such as 8080 … port 90 on both 192.168.0.106 and 192.168.0.103), create two separate rules using different External Ports (such as 9000 and 9001) and the same Internal Port (90) … there is another network address translation (NAT) device between your router and the Internet. You will need to open the required ports on that device as well. … Some ISPs (such as those using Carrier-Grade NAT, or CG-NAT) assign private IPs by default, which prevents port forwarding from working over the Internet. … Some models support different External Ports and Internal Ports. tp-link.com/us/support/faq/1379/

Author: Bulan Sarkar · Report an error

Numbers here are quoted from standards bodies and makers, or worked out from them. Nothing on this page was measured or tested by us.