I have an OpenVPN instance on AWS I'm using to control access to admin tools. I have an internal Route53 zone and a BIND instance which OpenVPN sets as the client DNS. Everything works great, except than whenever I open my laptop if I have a dashboard open to grafana.mydomain.com
it attempts to resolve to the public Route53 zone and fails since this record is only in the private zone. When the VPN connects a moment later the previous failure remains cached for 5 minutes.
Is there any way to fix this behavior (without modifying the client machine)? Something like clearing the DNS cache on connect to the VPN or reduce the time the missed lookups are cached for?