Issue with subnet not getting resolved via vpn's dns (using systemd-resolved)

[janusqa]

Hi is there any known issue with systemd-resolved?

I am pushing some subnets thru vpn-slice the connect seems to go well and connect. I can reach some hosts but host on a particular subnet I am unable to reach. It so happens its the same subnet the vpn's dns server is a part of. It is a /16 class a subnet 10.10.0.0/16

Interestingly enough when i append --dump i can see the vpn pushing routes my way which are identical to the routes I am pushing at it, also its passing along some search domains.

If the vpn is passing all this info how do I make use of it, I am unable to ping short names based on the hosts that I can reach.

I have had to resort to disabling resovled and using dnsmasq to manually force traffic from the subnets pushed above to the vpn and i can reach all that I am to reach.

Is there a way to make it work with systemd-resolved inclusive of the use of the search domains being pushed at me?

openconnect v8
vpn-slice 0.11
ubuntu 18.04

command in use

sudo ./openconnect --protocol=gp --user=xxx \
    --csd-wrapper=./scripts/hip-report.sh \
    --servercert pin-sha256:xxx xxx --dump \
    --script='/home/xxx/.local/bin/vpn-slice --dump 
        xxx/32 xxx/25 xxx/26 xxx/25 xxx/26 xxx/32 xxx/29 xxx/27 xxx/32 10.10.0.0/16' 

[dlenski]

Interestingly enough when i append --dump i can see the vpn pushing routes my way which are identical to the routes I am pushing at it, also its passing along some search domains.

I don't understand the problem you are describing. What does “pushing routes” mean?

What is it that you expect this command to do, which it doesn't do?

If the vpn is passing all this info how do I make use of it, I am unable to ping short names based on the hosts that I can reach.
…
Is there a way to make it work with systemd-resolved inclusive of the use of the search domains being pushed at me?

You can use the -d option (repeatedly, if desired) to override the default search domain specified by vpn-slice, for the purpose of looking up hostnames specified on the command line…

  -d DOMAIN, --domain DOMAIN
                        Search domain inside the VPN (default is
                        $CISCO_DEF_DOMAIN)

… but I am not sure that this is what you are trying to do, since you don't seem to be specifying any hostnames for DNS lookup on the command line — at least not in your obfuscated example.