Description
When user need to open internal device to the public Internet, who need do something to protect the resource from hackers. DDNS is a popular feature which is always used to avoid internal devices surfer external attacks. All Milesight routers support DDNS and multiple types of third party DDNS services. Here, we will use one of service types Dyn DNS to configure DDNS below.
Requirement
- Dyn DNS Account
- Any one Milesight Router/CPE
- A Camera under Router Subnet
Configuration
Step 1. Create a Host name on Dyn DNS platform.
Access to My Dyn Account, click Add Hostname.
Host Name: Type in a hostname of your choice into the Hostname field and select one of the domains from drop-down menu. This will be your device’s new web address.
Service Type: Select Host with IP address.
IP address: Type in your current router public IP address into the IP Address field.
TLS: If https will be used to access later, enable TLS. Here we disable it.
Note:
1. If users unknown their router network IP address, go to checkip on one computer inside of your network.
2. If user hasn’t registered a Dyn DNS account before, please click here to create an account first.
Then click Activate.
Step 2. Enable and configure Dyn DDNS service type on Milesight router below, then click Save and Apply it.
Service type: Choose Dyn DNS.
User name: Type in your Dyn DNS account
User ID: User-define
Password: Fill in password of Dyn DNS account
Hostname: Paste related host name created on Dyn DNS platform before.
Use HTTPS: Disable
Wait a moment, we can see that the DDNS status change to Connected.
Step 3. When access to complete hostname by browser of external computer, we can go to router web page directly.
Note: ensure the remote access services are enabled before accessing the web GUI.
Step 4. Access to subnet devices in router LAN.
Add a Port mapping rules to subnet device, then we can access to camera web GUI directly when accessing to hostname:9090.
When you need access subnet devices connect with this router, please refer to this to configure other Port Mapping rules, then you can access to subnet devices by “Hostname:port” directly.