Whether OceanStor 9000 supports accesses through domain names

1

OceanStor 9000 supports accesses through domain names. OceanStor 9000 has dynamic and static domain names. You can either connect an external DNS server or use OceanStor 9000 itself for domain name resolution. For details about the access mode, see the OceanStor 9000 InfoEqualizer Feature Guide:
- OceanStor 9000 V100R001C01 InfoEqualizer Feature Guide
- OceanStor 9000 V100R001C20 InfoEqualizer Feature Guide
- OceanStor 9000 V100R001C30 File System Feature Guide

Other related questions:
Concept of a dynamic domain name of OceanStor 9000
OceanStor 9000 dynamic domain name: A domain name that is resolved to return a dynamic front-end service IP address of a node

Concept of a static domain name of OceanStor 9000
OceanStor 9000 static domain name: A domain name that is resolved to return a static front-end service IP address of a node

How to configure AR routers in branches to use a domain name to access the headquarters through DSVPN
In the figure on the right, the branch and headquarters access the Internet through PPPoE dialup, and the branch uses the domain name to access the headquarters through DSVPN. Assume that the public network route is reachable. The following describes only key configurations. 1. Configure Spoke1. The configuration of Spoke2 is similar to that of Spoke1, and is not mentioned here. interface Dialer1 //Configure a dialer interface. link-protocol ppp ppp chap user user@huawei.com //Configure CHAP authentication. ppp chap password cipher huawei@123 //Set the CHAP authentication password to huawei@123. ip address ppp-negotiate dialer user huawei //Configure the peer user name for the dialer interface. dialer bundle 1 //Configure a dialer bundle for the dialer interface. dialer-group 1 // Configure a dialer access group. # interface Tunnel0/0/0 //Configure a DSVPN tunnel interface. ip address 10.16.1.2 255.255.255.0 tunnel-protocol gre p2mp source dialer 1 //Configure the dialer interface as the source interface. ospf network-type broadcast nhrp entry 10.16.1.1 www.123.com register //Configure an NHRP mapping table. # interface GigabitEthernet1/0/0 pppoe-client dial-bundle-number 1 //Configure the PPPoE client to use dialer bundle 1. # dialer-rule //Configure a dialer ACL. dialer-rule 1 ip permit # ip route-static 0.0.0.0 0.0.0.0 dialer1 //Configure a default route pointing to the dialer interface. 2. Configure the hub. dns resolve //Enable the dynamic DNS (DDNS) function. dns server 2.1.1.1 //Configure an IP address for the DNS server. # interface Dialer1 link-protocol ppp ppp chap user user@huawei.com ppp chap password cipher huawei@123 ip address ppp-negotiate dialer user huawei dialer bundle 1 dialer-group 1 ddns apply policy mypolicy //Bind the DDNS policy to the interface. # ddns policy mypolicy //Specify the URL in a DDNS update request. The user name is steven and the password is nevets@123. url ""http://:@members.3322.org/dyndns/update?system=dyndns&hostname=&ip="" username steven password nevets@123 # interface Tunnel0/0/0 ip address 10.16.1.1 255.255.255.0 tunnel-protocol gre p2mp source dialer 1 ospf network-type broadcast nhrp entry multicast dynamic # interface GigabitEthernet1/0/0 pppoe-client dial-bundle-number 1 # dialer-rule dialer-rule 1 ip permit # ip route-static 0.0.0.0 0.0.0.0 dialer1

Whether the USG2000 and USG5000 series support the NAT based on domain names accessed by intranet users
USG firewalls do not support NAT based on domain names accessed by intranet users. To allow users to access specified websites, you can configure the URL filtering.

If you have more questions, you can seek help from following ways:
To iKnow To Live Chat
Scroll to top