Site to Site VPN - Name Resolution issue

We have a site to site VPN setup between 2 mikrotik’s. It works great except for a few of the machines on the remote end have an issue about twice a week. The issue they are having is that they can’t resolve DNS for local machines at the main office. We have a terminal server that they connect to, and we connect to this machine by name “termserver”. When they have this issue, they can ping the machine just fine by IP, but they can’t ping it by name. These machines are joined to the domain (DC is in the main office).

The fix is simple, ipconfig /renew. After that DNS resolution works just fine.

I can’t seem to figure out why it just all of a sudden stops working in the middle of the day, they will be working fine all day and then just randomly it stops and they call us.

The main office is at 192.168.1.0/24
Remote office is at 192.168.88.0/24

Remote office pulls DHCP from their local mikrotik, which I have the DNS Servers set to 192.168.1.11(our DNS server at main office) and secondary of 192.168.88.1(mikrotik router at remote office).

This configuration works fine for multiple other clients that we have an IPSEC site-to-site VPN setup for. I can’t seem to find anything different about this configuration versus our other ones.

Can anyone point me in the right direction??

Is the remote mikrotik using an external DNS? I wonder if it is sometes being queried and not answering as desired.