Standard TZO DNS HOWTO

To begin, first install and configure the network device or service you will want to remotely access. For example: a web or FTP server running on a PC, a network-enabled security DVR or camera, VNC or Remote Desktop.

Using another PC or system on the same network, verify you can make a local connection to your network server/service. Depending on your network server software, you would either connect using the server's LAN IP address (192.168.x.x) or you may be able to 'browse' the local network.

This step is optional, but very strongly recommended.

Inside your network, your server could be at (for example) a LAN IP address of 192.168.1.201, but tomorrow (or next week or month) it could change to 192.168.1.200. Just know that inside your network, devices can change their LAN IP address and this has to do with default policies on your router and server.

In Step 3, you will be configuring your router to port forward traffic from the outside to the inside, targeting the IP address of your server. If your server changes LAN IP as warned about here, know that your router will continue forwarding traffic to the old IP address (which would go unanswered, or worse it may go to another one of your systems you did not want remote connections going to). To avoid this inconvenience (or potential security issue), you want to fix your server to a Static LAN IP address which is outside your router's DHCP range. Your server and router documentation will describe how to do this, or you could look at our Support and DVR Tutorials where we walk through those steps.

Because you are reconfiguring your server's network settings, before continuing to the next step be sure that everything is still working (repeat the tests in Step 1).

For this step you will need to know your server's Port requirements (what TCP or UDP ports it uses). For example, webservers and most DVRs/cameras use 'TCP Port 80'. Check your server documentation if unsure about ports. The other important detail is your server's LAN IP address, which you know from previous steps.

Using your router's Port Forwarding setup (sometimes under Applications and Gaming), create a Forwarding rule for the TCP or UDP port. You need to indicate this traffic will be forwarded to a LAN IP address (the IP of your server). Save this new setting.

Also in your router, there should be a section about Firewalls. When router's firewalls are enabled (particularly if set to 'High') they will block all incoming traffic... even traffic which you already approved using the router's Port Forwarding. Lowering the router's Firewall setting to Medium is usually required. If unsure, consult your router's documentation or technical support.

In some cases where your server is a computer, there may be a firewall local to that server. However a local server firewall would have been discovered earlier, prevented you from running a local connection test. If needed, configure your OS firewall for an 'Exception' or 'Allow' to permit incoming traffic on your service port. If your server were a DVR or camera or network storage device, it is unlikely to have any firewall to worry about.

At this point your network should forward outside Internet traffic to your server. You need to test this a few different ways (if there are problems, the tests will help you narrow down the problem). While still onsite, do a remote 'open port check' with your browser by visiting Whatsmyip.org Port Test. The test tool already knows your network IP address from your browser, so you just need to enter what port it should test. A report that the port is closed (fails) means something on your end is blocking the connection (and must be fixed), while an open port means success..

Now you can run your remote tests. While still on-site, visit TZO Test or TZO IP Echo Page and take note of your WAN/network IP address. For the remote test, it is best if you can call someone and have them try to connect to your server using the correct viewer (browser, camera client, etc) and your WAN IP. Do not complicate the test by using your TZO domain name just yet. If you do not have someone on the outside who can help test, then you need to go to another network (neighbor, work, etc) and try connecting to your WAN IP. You can not test your WAN IP from inside (due to NAT loopback issues).

If the outside connections fail to connect, double-check your port settings and router firewall. Also check your server to see if it has a local firewall. If some ports work and others fail, ask your Internet provider's support about which port(s) they block.

Note: some DSL and cable companies provide modems with a built-in NAT router, which require additional configuration (enabling 'Bridge Mode'). Ask your Internet provider's support for help enabling Bridge mode. If their support asks for details, what you want to do is 'pass through the Internet IP' to inside your network, so your own router can handle Port Forwarding. Failing that, there is also a way to port forward from the modem to your router (which port forwards to your server..), but the Bridge Mode method is easier.

You may be wondering why we suggested you first configured your network for remote connections, before adding and configuring TZO. The reason is because it much easier to find and fix any problem with your network configuration. Once you successfully make remote connections into your network, using your WAN IP address, then you can have confidence everything will work. If you were not able to get this far due to a technical problem setting up your network, our Support can get you pointed in the right direction.

At this point you can either request a free 30-day TZO trial, or proceed to order the service 'TZO Standard' (which has a 30 day money back guarantee). In the ordering, select the duration you wish. For either a trial or an order of TZO Standard, TZO will email you a TZO key for this domain.

Now you can configure your TZO update client. The TZO client will detect the shared Internet IP address for the network you install it on. The TZO client should only be installed at the network you wish to remotely connect 'to', so that the client can automatically update your domain whenever your Internet provider gives you a new Internet address.

You have a choice of using a TZO software client downloaded from our website, or a third party DDNS client found in your router or camera. If your network has a PC, it is best to use the TZO software client as it is designed and certified by TZO. You may also use a TZO Certified hardware client. Simply fill out the fields for your TZO account and save your settings. Note that some router and camera clients will ask for 'username' and 'password', just fill that in with your TZO domain's email address and your TZO key, respectively.

Once your TZO client is activated, it should indicate a successful update, and display your domain name and current WAN IP address. You can also verify this domain information under your account on the TZO website. Everything should just work when you go off-site and you can connect to your domain name and everything works. If you are using a third party DDNS client, be sure you do not let the TZO account expire, as this will require you to manually restart DDNS at that location.