Hi ikappas,
I have run into the same situation while connecting to a VPN where the VPN defined search domains are pushed to resolver #1 in addition to the ones from DHCP along with an additional resolver entry #2 which points the domain entry to the VPN DNS Server.
This is correct behaviour and not a cause of any Split DNS problems. I’m including a reply below from another thread:
This is normal and expected. The important part to look at for Split DNS is the “DNS configuration (for scoped queries)” section. This is the section that indicates what DNS server will be associated with what domain/s. From your output any subdomains of “my.domain” will use the “192.168.0.2” DNS server.
If you’re wondering what the domains listed in the “DNS configuration” section mean, they indicate what suffixes macOS will try if a single label is entered. For example, if you try and resolve simply “exampleserver” (and that fails), macOS will then try “exampleserver.my.domain” (and keep trying any other search domains listed). The default/first resolver will always have all search domains listed (but again, this isn’t used for Split DNS).
Cheers,
James
