Solved Hairpin NAT in Place of Split DNS for v20?

[TaylorStevens23]

Hello! I am looking to go to version 20 here in the next week. I had a call with our network admin to review the split DNS configuration before the update. The admin said we should not have to setup a split DNS and that the hairpin NAT we have in place already should do the trick. He said the hairpin NAT should be better than a split DNS. The FQDN does resolve currently internally and externally. Before moving forward I wanted to get feedback here, is a hairpin NAT sufficient to upgrade to v20? Are there any test I can run beforehand to verify it is setup correctly?

Details:
On Prem: Yes
Version: 18.0 (Build 31)
License: Professional Annual

 

[NicholasP_3CX]

Yes, of course. If you dont have an internal DNS server, you can use your firewalls hairpin NAT capabilities.

We also have this in our guide at https://www.3cx.com/docs/creating-fqdn-split-dns/

 

[TaylorStevens23]

Yes, of course. If you dont have an internal DNS server, you can use your firewalls hairpin NAT capabilities.

We also have this in our guide at https://www.3cx.com/docs/creating-fqdn-split-dns/

View attachment 45412

Thank you very much!!