V14 - Passthrough on registration interface not working

[hakehsw]

Describe the bug
All domains are on the registration network are resolved to the portal IP 66.70.255.147. Even with passthrough enabled and the domains entered in the corresponding field.

To Reproduce
Steps to reproduce the behavior:

1. Go to 'Configuration->Network Configuration->Fencing'
2. Click on 'Passthrough' to enable it
3. Enter a domain in 'Passthroughs Domains' for example 'login.microsoftonline.com'
4. Try to nslookup 'login.microsoftonline.com' on a device in the registration network
5. See error IP 66.70.255.147 instead of the real one

Expected behavior
if the domain is in passtrough and passtrough is enabled a nslookup shouldgive back the real ip of the domain

Desktop (please complete the following information):

• OS: WIN10
• Command Shell

Additional context
If I change something under for example 'Configuration->System Configuration->Cluster' (we have no cluster running)
For example activate 'pfdns on VIP only' and click on safe I will get the real IP returned in a short time frame probably 5-10 seconds after the click.

[heapdavid]

We're seeing similar for Facebook and LinkedIn auth on PF14.0 - pfdns is also returning 66.70.255.147 rather than the expected actual IPs for all the Authorized domains set in the auth source config

Edit: We're running it on Debian 12 if that's relevant