An example of remote access to home network resources with KeenDNS

With your Keenetic router, you can provide remote access from the Internet to home network resources or its web interface via the secure HTTPS web protocol. This can be done through the KeenDNS service using 4th level domain names, even without a public IP address.

First, you need to select a free KeenDNS domain name in the settings and configure the service. Detailed setup is presented in the article 'KeenDNS service'.

This feature is also available for Keenetic devices in additional operating modes.

NOTE: Important! The digital certificate and HTTPS private key are stored directly on the Keenetic router. When accessing via a cloud server, using HTTPS, a secure tunnel is built up to the router, ensuring the security and confidentiality of data transmitted via the Internet. The session is established using end-to-end encryption. This means, among other things, that the information transmitted between the router and the browser via HTTPS is not available to KeenDNS cloud servers, which provide data transfer at the transport layer. With cloud access via HTTP, a secure channel is established between the router and the KeenDNS server using a KeenDNS digital certificate, which also guarantees security and data protection against interception.

Here is an example of remote access to the Transmission torrent client's web interface (running on the router on port 8090) and the web interface of a QNAP NAS (running on port 80) connected to the home network.

You can configure remote access to any web-enabled device in your home network (it can be a webcam, network drive, router, server, etc.).

1. To start with, it is necessary to register the devices in the router to be remotely accessible. More information can be found in the article 'Connected devices registration'.

2. On the 'Domain name' page, on the 'KeenDNS' tab, in the section 'Access to web applications running on your network', click 'Create'.

kdns-01-en.png

3. The 'Access settings' page appears.

kdns-02-en.png

In the 'Host' field, select the device registered in your home network on which the web application is running. You can select the router itself to access the built-in services (e.g. Transmission GUI) or any other device registered in your home network.

In the 'Domain name' field, create a domain name for this application. The name should be in the Latin alphabet.
In our example, the application uses the router's domain name 'myrouter01.keenetic.link' and the 4th level domain name 'dls'. Thus, the Transmission application will be available by the domain name 'dls.myrouter01.keenetic.link'.

To access the application, you should enable the 'Allow access' option.

In the 'TCP port' field, specify the port number on which the web application runs on your home network.

To access the web interface of the built-in Transmission client, the rule will look like this:

kdns-03-en.png

And to access the QNAP network storage:

kdns-04-en.png

General view of the rules:

kdns-05-en.png

4. Once configured, home network devices will be available via the following 4th level domain names from the Internet:

dls.myrouter01.keenetic.link

access01-en.png

qnap.myrouter01.keenetic.link

access02-en.png

That being said, the Keenetic router has a private IP address for the Internet connection.

kdns-06-en.png

NOTE: Important! If you have changed the pre-installed Keenetic management port from 80 to one of the following: 81, 280, 591, 777, 5080, 8080, 8090 or 65080, then access home network resources via the 4th level domain will also be via the changed port. For example, for port 777:
dls.myrouter01.keenetic.link:777
qnap.myrouter01.keenetic.link:777

You can change the Keenetic web interface control port on the 'Users and access' page in the 'TCP port for managing the Keenetic' section in the 'HTTP port' field.

TIP: Tips:

Examples of how to provide access to an IP camera from the Internet can be found in the article 'Internet access to an IP camera connected to Keenetic'.

'Enable authorization for the device with an open web interface when using KeenDNS remote access.'

 

Have more questions? Submit a request

Comments

0 comments

Please sign in to leave a comment.