IKEv2 Payload attribute 25 INTERNAL_DNS_DOMAIN not working

%3CLINGO-SUB%20id%3D%22lingo-sub-991354%22%20slang%3D%22en-US%22%3EIKEv2%20Payload%20attribute%2025%20INTERNAL_DNS_DOMAIN%20not%20working%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-991354%22%20slang%3D%22en-US%22%3E%3CP%3EHello%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI'm%20setting%20up%20a%20IKEv2%20VPN%20in%20a%20Windows%2010%20machine%2C%20that%20connects%20to%26nbsp%3Ba%20Strongswan%20server.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20VPN%20works%20fine%20except%20for%20DNS%20suffix%20that%20are%20not%20installed%20when%20I%20connect.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIs%20this%20Payload%20attribute%20supported%20on%20Windows%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThank%20you.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Occasional Visitor

Hello,

 

I'm setting up a IKEv2 VPN in a Windows 10 machine, that connects to a Strongswan server.

 

The VPN works fine except for DNS suffix that are not installed when I connect.

 

Is this Payload attribute supported on Windows?

 

Thank you.

0 Replies