Very likely, the VPN app on your laptop is forcing to use the VPN DNS, but this it is not the case on the router! All DNS requests are still using the default DNS outside of the VPN!
You would need to either set up the router DNS to the VPN one or force all DNS traffic to use the VPN one with some iptables rules.
Issue is if you do this statically, DNS stops working if you stop the VPN tunnel on the router.
So you'd have to automate it.
If you have the Kamoj add-on, then there are already scripts /etc/openvpn/ovpnclient-up.sh and /etc/openvpn/ovpnclient-down.sh
Then in /etc/openvpn/ovpnclient-up.sh put the logic that needs to be performed if the VPN is started. (for instance change the router DNS-servers (in resolv.conf) to the VPN DNS servers.
Alternatively, make it integrate in kamoj-addon, from there extract the devices that would use the VPN tunnel, and add iptables rules to redirect all DNS queries from those devices to 1 of the VPN DNS servers (so you lose a bit of redundancy).
All other devices that bypass VPN would then still use the normal DNS servers.
(to make it more dynamic, parse the vpn connection log to find the newest "PUSH: Received control message: 'PUSH_REPLY,.....,dhcp-option DNS x.y.z.1,dhcp-option DNS x.y.z.2", and extract the VPN DNS servers from that.)
(challenge of this approach: existing processes on the router could rewrite resolv.conf or reload the firewall, again undoing the changes of this script.
For the iptables approach, the solution would be to generate an additional /opt/scripts/firewall-start-xxx.sh to create the redirect rules. (this way they are recreated if something restarts the firewall)
For the resolv.conf approach, perhaps the new VPN DNS servers must also be written to specific nvram variables. (so that if something recreates the resolv.conf that it then uses those DNS servers from nvram.)
In /etc/openvpn/ovpnclient-down.sh you would have to put the logic to restore the original DNS in resolv.conf or remove the iptables redirect rules.
(but if VPN crashes, then probably ovpnclient-down.sh won't be run. So then DNS is also (partially) broken until someone restarts VPN)