HPE FlexNetwork MSR Series - Bidirectional NAT for External-To-Internal NAT Server Access through Domain Name Configuration Example

171
RTSP : Enabled
RSH : Disabled
SCCP : Disabled
SIP : Disabled
SQLNET : Disabled
TFTP : Disabled
XDMCP : Disabled
Static NAT load balancing: Disabled
# Display NAT session information generated when Host accesses Web server.
[Router] display nat session verbose
Slot 1:
Initiator:
Source IP/port: 202.1.1.2/1694
Destination IP/port: 202.38.1.3/8080
DS-Lite tunnel peer: -
VPN instance/VLAN ID/Inline ID: -/-/-
Protocol: TCP(6)
Inbound interface: GigabitEthernet2/0/2
Responder:
Source IP/port: 10.110.10.2/8080
Destination IP/port: 202.1.1.2/1694
DS-Lite tunnel peer: -
VPN instance/VLAN ID/Inline ID: -/-/-
Protocol: TCP(6)
Inbound interface: GigabitEthernet2/0/1
State: TCP_ESTABLISHED
Application: HTTP
Start time: 2012-08-15 14:53:29 TTL: 3597s
Initiator->Responder: 7 packets 308 bytes
Responder->Initiator: 5 packets 312 bytes
Total sessions found: 1
Bidirectional NAT for external-to-internal NAT Server access
through domain name configuration example
Network requirements
As shown in Figure 69, an intranet uses the subnet 192.168.1.0/24. The Web server at
192.168.1.2/24 provides Web services for external users and the DNS server at 192.168.1.3/24
resolves the domain name of the Web server. The company has 3 public addresses 202.38.1.2,
202.38.1.3, and 202.38.1.4.
Configure NAT to allow external host at 192.168.1.2 in the external network to use the domain name
to access the internal Web server.