NAT from source IP by FQDN
![PeterUK](https://us.v-cdn.net/6029482/uploads/avatarstock/n6YKXRWWBKFRM.png)
![Community MVP](https://us.v-cdn.net/6029482/uploads/badges/ZZWI1YYJVW84.png)
![First Anniversary](https://us.v-cdn.net/6029482/uploads/badges/SJKCAIG91R5S.png)
![10 Comments](https://us.v-cdn.net/6029482/uploads/badges/818CA6MI9BTU.png)
![Friend Collector](https://us.v-cdn.net/6029482/uploads/badges/HNJASEUSC535.png)
When making a NAT rule for Virtual Server your able to select for source IP a FQDN which would allow a dynamic connection by given FQDN to IP to match the NAT rule.
WILDCARD FQDN are not selectable.
Comments
-
NAT <> Virtual Host.NAT chews only IPs, no hostnames.0
-
You're probably right.
I'll gladly read the lecture, if you will write it when you'll have enough time.0 -
Thanks Peter, do you refer to security policy? It's the only rules where I can specify a source IP as FQDN, but if I set this I can't set the dest. port and I wouldn't that this has effect for all NAT because I have some port forwarding without restriction and other with this source restriction.
Thanks in advance
0 -
The idea is for the NAT rule to have select traffic by source FQDN go to a port like port 80 at say 192.168.0.2 but with another rule below for port 80 to have any other traffic go to 80 192.168.0.80
there is a way you can do the above but needs a VLAN switch and another USG and not with NEBULA
if your not needing that then you can use security policy
0
Categories
- All Categories
- 413 Beta Program
- 2.3K Nebula
- 192 Nebula Ideas
- 87 Nebula Status and Incidents
- 5.3K Security
- 142 USG FLEX H Series
- 253 Security Ideas
- 1.3K Switch
- 75 Switch Ideas
- 993 Wireless
- 51 Wireless Ideas
- 6.1K Consumer Product
- 231 Service & License
- 362 News and Release
- 74 Security Advisories
- 23 Education Center
- 5 [Campaign] Zyxel Network Detective
- 2.6K FAQ
- 34 Documents
- 34 Nebula Monthly Express
- 101 About Community
- 67 Security Highlight