VPN Split Tunnel DNS not working after update to 3.4

[Liam-VerifAction]

System details

Omarchy 3.4.1, Sonic Wall Connect Tunnel 12.5

What's wrong?

I use the Linux Sonic Wall Connect Tunnel client to access clients VPN network. Previously on 3.3 this all worked fine with the split tunnel correctly diverting any of the internal sites through the VPN. Since updating to 3.4 this has stopped working.

If I manually add the routes into my /etc/hosts file then I am able to reach them no problem, but other routes on the network remain unavailable. It seems something is not allowed the VPN's DNS to engage properly

[Liam-VerifAction]

Problem seems to be once connected to the tunnel, resolvectl status gives

Link 32 (tun0)
    Current Scopes: LLMNR/IPv4 LLMNR/IPv6
         Protocols: -DefaultRoute +LLMNR -mDNS DNSOverTLS=opportunistic DNSSEC=no/unsupported
     Default Route: no

Manually running
sudo resolvectl domain tun0 ~domain_name and sudo resolvectl dns tun0 172.19.xxx.xx 172.19.xxx.xx

Which then allowed me to access internal sites and status correctly reported

Link 32 (tun0)
    Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6
         Protocols: -DefaultRoute +LLMNR -mDNS DNSOverTLS=opportunistic DNSSEC=no/unsupported
Current DNS Server: 172.19.xxx.xx
       DNS Servers: 172.19.xxx.xx 172.19.xx.xx
        DNS Domain: ~domain.com 
     Default Route: no

But this has to be rerun every time I connect to the VPN