Hi opti2k4,
First some design talk., virtual-wan-link is intended to either load balance or failover between internet connections.. Sounds like your use case is different.
Pls ensure you do not have virtual lan link enabled. Just have two WAN ports. Put the internet in wan1 and the connection for VPN in wan2.
Configure policy routing so that any traffic destined for the remote IPSec endpoint goes out Wan2, this will ensure your VPN traffic goes out the right circuit.
Now write a rule to wan1 blocking the IP of the remote IPsec endpoint, and a rule beneath to allow internet access. That ensures your VPN traffic will never go out wan1 while providing internet access to others Thats the design piece.
Pls ensure you have the DNS server enabled correctly on the internal facing interface on the firewall, and that it' s configured properly. None of the work you did should have affected the DNS server on the firewall, I can' t imagine it was enabled on the WAN ports.
You can try pasting the DNS server config you have (redacting any confidential info) for review, but it' s hard to say if that' s the ultimate cause without knowing the rest of the config.
I could also suggest that you open a TAC case and include a backup of config as well as diag debug report / exe tac report.
Hope that helps!
Cheers!
--
Sean Toomey, CISSP FCNSP
Consulting Security Engineer (CSE)
FORTINET— High Performance Network Security