You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have ran into an issue with my current designs for a multi-site set of forwarding servers using Advanced Fowarding app. We have a situation where we have multiple sites and there's NAT'ing between sites, and I've found that Advanced Forwarding works great for forward zones. However, in trying to do reverse lookups against the forwarding servers, it seems to ignore the rules no matter how I set it up. If the zone is "150.20.10.in-addr.arpa", I've tried the following ways of putting it into the config without luck:
"150.20.10.in-addr.arpa"
"150.20.10"
"10.20.150"
I've even tried just doing "*" so that all matching clients just go there, and the forward zones are good, but none of the reverse zones. Is this something that could conceivably be possible?
The text was updated successfully, but these errors were encountered:
Thanks for the post. If your network is 10.20.150.0/24 then the corresponding reverse zone will be 150.20.10.in-addr.arpa. So, that's the only option you have to configure for conditional forwarding.
Since you have issue with forwarding config, you will need to share the config that you have running so that I can help with any issues with that. You can share it here or send it to [email protected].
I have ran into an issue with my current designs for a multi-site set of forwarding servers using Advanced Fowarding app. We have a situation where we have multiple sites and there's NAT'ing between sites, and I've found that Advanced Forwarding works great for forward zones. However, in trying to do reverse lookups against the forwarding servers, it seems to ignore the rules no matter how I set it up. If the zone is "150.20.10.in-addr.arpa", I've tried the following ways of putting it into the config without luck:
"150.20.10.in-addr.arpa"
"150.20.10"
"10.20.150"
I've even tried just doing "*" so that all matching clients just go there, and the forward zones are good, but none of the reverse zones. Is this something that could conceivably be possible?
The text was updated successfully, but these errors were encountered: