Firewall Intranet users access internal servers through public network domain names or public IP addresses

Firewall Intranet users access internal servers through public network domain names or public IP addresses I. Networking requirements: www.2cto.com allows internal users to access internal servers through the domain names provided by the carrier (WWW, FTP ). Assume that the domain names of the internal WWW and FTP servers are www.fuwu.com and ftp.fuwu.com. The configuration example is as follows: <Quidway> dis cur # sysname Quidway # firewall packet-filter enable firewall packet-filter default permit # undo insulate # undo connection-limit enable connection-limit default deny connection-limit default amount upper -limit 50 lower-limit 20 # nat dns-map www.fuwu.com 10.153.49.212 80 tcpnat dns-map ftp.fuwu.com 10.153.49.212 21 tcp # firewall stat Istic system enable # radius scheme system # domain system # acl number 2000 rule 0 permit source 172.16.0.0 0.0.255.255 # interface Aux0 async mode flow # interface Ethernet0/0 ip address 172.16.2.1 255.255.255.0 # interface Ethernet1/0 ip address 10.153.49.193 255.255.252.0 nat outbound 2000 nat server protocol tcp global 10.153.49.212 www inside 172.16.1.2 www # interface Ethernet1/1 # interface Ethernet1/2 ip Address 172.16.1.1 255.255.255.0 # interface NULL0 # firewall zone local set priority 100 # firewall zone trust add interface Ethernet0/0 set priority 85 # firewall zone untrust add interface Ethernet1/0 set priority 5 # firewall zone DMZ add interface Ethernet1/2 set priority 50 # firewall interzone local trust # firewall interzone local untrust # firewall interzone local DMZ # firewall interzone trust untrust # f Irewall interzone trust DMZ # firewall interzone DMZ untrust # ip route-static 0.0.0.0 0.0.0.0 10.153.48.1 preference 60 # user-interface con 0user-interface aux 0user-interface vty 0 4 authentication-mode none # return <Quidway> 3 note: 1. after you use a domain name to access the server, you cannot use a public IP address to access the server. 2. There must be a real domain name on the public network (this domain is provided by the carrier, and the public network users can access internal servers through this domain name ). 3. Currently, on the SecPath firewall, there is no way for Intranet users to simultaneously access the Intranet server through domain names, Internet IP addresses, and private IP addresses.