H3C Technologies H3C SecPath F1000-E - Manual (Page 250)

225
Static domain name resolution configuration example
Network requirements
As shown in Figure 135 , the SecPath wants to access the host by using an easy-to-remember domain
name rather than an IP address.
Configure static domain name resolution on the SecPath so that the SecPath can use the domain name
host.com to access the host whose IP address is 10.1.1.2.
Figure 135 Network diagram
Configuration procedure
# Configure a mapping between host name host.com and IP address 10.1.1.2.
<Sysname> system-view
[Sysname] ip host host.com 10.1.1.2
# Use the ping host.com command to verify that the firewall can use static domain name resolution to
resolve domain name host.com into IP address 10.1.1.2.
[Sysname] ping host.com
PING host.com (10.1.1.2):
56 data bytes, press CTRL_C to break
Reply from 10.1.1.2: bytes=56 Sequence=1 ttl=128 time=1 ms
Reply from 10.1.1.2: bytes=56 Sequence=2 ttl=128 time=4 ms
Reply from 10.1.1.2: bytes=56 Sequence=3 ttl=128 time=3 ms
Reply from 10.1.1.2: bytes=56 Sequence=4 ttl=128 time=2 ms
Reply from 10.1.1.2: bytes=56 Sequence=5 ttl=128 time=3 ms
--- host.com ping statistics ---
5 packet(s) transmitted
5 packet(s) received
0.00% packet loss
round-trip min/avg/max = 1/2/4 ms
Dynamic domain name resolution configuration example
Network requirements
As shown in Figure 136 , the SecPath wants to access the host by using an easy-to-remember domain
name rather than an IP address, and to request the DNS server on the network for an IP address by using
dynamic domain name resolution. The IP address of the DNS server is 2.1.1.2/16 and the DNS server has
a com domain, which stores the mapping between domain name host and IP address 3.1.1.1/16.
Configure dynamic domain name resolution and the domain name suffix com on the SecPath that serves
as a DNS client so that the SecPath can use domain name host to access the host with the domain name
host.com and the IP address 3.1.1.1/16.