Hi everyone. Just today I am no longer able to connect to my database, via TablePlus and Wireguard. I thought it was an issue with expired key so I went ahead and generated a new wireguard key but having the same issue. The error that was given by TablePlus reads:
could not translate host name "club-db.internal" to address: nodename nor servname provided, or not known
When trying to proxy via fly proxy localhost -a club-db, it returns Error club-db.internal: host was not found in DNS
Fortunately, the app that connects to this database is still working fine. I’m certainly worried that that will break too at some point and I’m left with a database that I can’t connect to.
What DNS server are you using to resolve the .internal address? It’s only possible to do so using our private DNS server hosted at [fdaa::3]:53 which is only available when connected via WireGuard or from an app hosted on us.
dig @fdaa::3 AAAA club-db.internal
You also have to be connected using a peer on the same private network (usually that means in the same organization).
Thanks for the speedy response and fix @jerome - I can confirm that I’m able to connect to the database again using both my old and new wireguard config. I looked up the config and was able to get the right network ID and dig now returns success.