No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

The precaution about the DDNS configuration on USG5320

Publication Date:  2012-09-18 Views:  2 Downloads:  0
Issue Description
1.1 Topology

1.2 Abstract
As the figure, the IP of DDNS client‘s (USG) interface (1) is obtained by the carrier dynamically, it’s not identical, so the PC should access the USG through domain name. The traditional DNS can’t update the mapping between the domain name and IP, this will case the PC falling to access the USG. Here, we can deploy DDNS to resolve this problem.
1.3 The problem description
(1)Having completed the configuration of DDNS, take the order: “display ddns current-state”, we see the state is “inactive” all long.
08:42:47  2012/05/03
---------------------------------------------
Policy-name: linshi
Domain-name: xxxx.3322.org
IP-address:
State:   inactive
Time:  00:00:00 0000-00-00
---------------------------------------------
Alarm Information
none
Handling Process
After checking the remote accessing device carefully, we find three problems, which are easily to be mistaken or omitted:
1 Forget to open the function of DDNS’s client globally: ddns client enable;
2 The application of DDNS must be at the logic interface “Dialer” but not at the physical interface “Etherenet 0/0/0”;
3 The operator is tend to ignore the configuration of the DNS, this will cause the wrong resolving of the DNS, then the state of DDNS is abnormal: dns resolve.
Adjust the above three problems, and renew the DNS policy manually, take the order: “display ddns current-state”, we find out the state is normal.
display ddns current-state                                     
08:53:35  2012/05/03
---------------------------------------------
Policy-name: linshi
Domain-name: qdswjt.3322.org
IP-address:  1.1.1.113
State:       active
Time:      15:55:54 2012-05-02
---------------------------------------------
Root Cause
After some related figuration checking, we diagnosed the problem: there are lots of errors or omits which result in the DDNS can't respond the DDNS server of the public network, then the DDNS's state is "inactive" all the time.
The handle process:
After checking the remote accessing device carefully, we find three problems, which are easily to be mistaken or omitted:
1 Forget to open the function of DDNS’s client globally: ddns client enable;
2 The application of DDNS must be at the logic interface “Dialer” but not at the physical interface “Etherenet 0/0/0”;
3 The operator is tend to ignore the configuration of the DNS, this will cause the wrong resolving of the DNS, then the state of DDNS is abnormal: dns resolve.
Adjust the above three problems, and renew the DNS policy manually, take the order: “display ddns current-state”, we find out the state is normal.
display ddns current-state                                      
08:53:35  2012/05/03
---------------------------------------------
Policy-name: linshi
Domain-name: qdswjt.3322.org
IP-address:  1.1.1.113
State:       active
Time:      15:55:54 2012-05-02
---------------------------------------------
Suggestions
After having deployed the DDNS, when the external network interface’s IP changed, the USG5320 will send request to the DDNS server to renew the mapping relation between the new domain name and IP automatically. After the DDNS server deal with this request, it will feed back the new mapping relation to the DNS server, then the message in the DNS server is updated. When the PC taking another time to access the USG through domain name, it can obtain the correct IP, and access successfully. Pay attention to the above three points, don’t configure incorrectly or omit some necessary configuration.

END