Change the order of DNS lookup when connected in the VPN

You can prioritize one adapter over another. Read through this article for how to do it.

However, when you say "I'd like the DNS lookup to first try the default DNS for the LAN and then if there was no match, try the default DNS for the wireless.", that is not going to work. Your LAN DNS Server, if available, will either resolve the name for you, answer that the name does not exist, or refer you to another DNS server. While you might think that the third option would be your ticket, understand that the DNS resolver in Windows (an most other systems) is a stub resolver that can not follow referrals, and so your DNS query will fail at that point.

If what you truly want is to get the internal IP adresses of your systems when you are connected through your LAN, and external resolved addresses when connected outside, or in general for any external names. This can be achieved by setting up split DNS on your LAN DNS server.

When your VPN is disconnected, your client's resolver uses your home DNS server to resolve names. When you try to access the hostname router, it uses the search path and asks your server for the address of router.dailey.home.com, and all is well.

When your VPN is connected, your VPN client and network settings point your client's resolver to your work DNS server. When you try to access the hostname router, your computer asks your work DNS server for the address of router.dailey.home.com. Since, as you've noted, the authoritative servers for the home.com domain return a valid answer for that domain name, the resolver stops there. If, instead, you changed your domain name to something not resolvable by Internet DNS servers, such as home.local, your work DNS server would still have no way of resolving router.home.local to an IP address, and would likely return an authoritative NXDOMAIN answer, i.e. "this domain does not exist." This configuration would fix your inability to reach intranet hosts without fully qualified names, since your client would proceed to the next element of your search path, but you still wouldn't be able to reach your home machines.

The best solution I can think of is to set up your client to prefer your Local Area Connection 2 (Control Panel > Network and Internet (View network status and tasks)> Change adapter settings; press Alt and choose Advanced Settings; and then modify the adapter order), and then to configure your DNS server to delegate responsibility for the pacs.local domain to your work DNS server. This arrangement still has the problem that you won't be able to get to any Internet-facing machines in pacs.local when your VPN is not connected, but given that the TLD is .local, I expect that won't be a problem. You may possibly still run afoul of requirements from your VPN client.