Supabase
No A records for database. DNS not resolving. #41048
|
As from Tuesday morning I have been unable to connect a client to my database. The Supabase console is up and running and I can access the database with no problems, the connection string is correct and I have also tried to create a new database to no avail. I'm no network admin, but my investigation seems to pinpoint the problem to be a failed DNS resolution due to no A records being present. Has anyone currently got similar issues, or can you suggest a work around (thinking a local instance maybe the way forward for dev)? Any help greatly appreciated. See the following dig output: % dig db.nhhwrfhsaqvwbntehafw.supabase.co ;; OPT PSEUDOSECTION: ;; AUTHORITY SECTION: ;; Query time: 22 msec |
Replies: 2 comments 1 reply
|
The URL you are using is IPv6 only. Are you on an IPv6 computer/server, router, network provider? |
|
I am and it was working fine, but running some tests now and it looks like the ISP could be the problem. Thanks for the feedback.
Mark
On Thursday 4 December 2025 at 13:53:06 GMT, GaryAustin1 ***@***.***> wrote:
The URL you are using is IPv6 only. Are you on an IPv6 computer/server, router, network provider?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
|
Confirming this is a IPv6 issue. Switched to IPv4 supported session spooler everything worked. Thanks @GaryAustin1! Still trying to resolve with ISP to get IPv6 support back.... |
The URL you are using is IPv6 only. Are you on an IPv6 computer/server, router, network provider?