Hairpin NAT instruction inconsistency?

In case all port-forwarding rules keep the destination ports intact (no mapping from 8443 to 443 for example), it might be preferable to, in addition to hairpin-NAT, also implement split DNS.

We would have different subdomains for each of the service hosts. From the outside, all the subdomains point to the public WAN IP address, and DSTNAT is set up. But locally in the LAN, the local DNS resolver will resolve the subdomains directly to their local IP addresses.

LAN devices in the same subnet as the service hosts will then be able to make direct connections to them, bypassing the router (and skip hairpin-NAT), which should improve performance considerably, especially for high throughput services like NAS.

Of course, hairpin-NAT is still configured, for devices that don't use the local DNS servers.