Roon Server on Mac Mini can't connect to cloud services due to DNS issues (ref#10AMU5)

[Dextro (Finn)]

Hi! What’s not quite right with Roon?

· None of the above quite fits

None of the above quite fits

· None of these quite match

Tell us what's going on

· Fresh Roon Server install on a Mac mini (Intel i7, 16GB RAM) running macOS Sequoia 15.7.4, set up on 16 March 2026. Downloaded the latest Roon Server installer from roon.app/downloads.

The core finds and plays local files without issue. However, Roon Server cannot connect to Roon's cloud services. The About page shows 'Waiting for Roon Server' and never completes. Tidal authentication completes successfully in the browser (green tick on oauthcb.roonlabs.net) but Roon never picks up the callback. Metadata improver is paused. Roon ARC cannot connect.

I've confirmed internet connectivity is fine. Ping to google.com, auth.tidal.com, and curl to roon.app all succeed. However, nslookup for accounts.roonlabs.com and discovery.roonlabs.com both return NXDOMAIN, even when queried directly against Google's public DNS (8.8.8.8). This suggests these domains are not resolving in public DNS.

Things I've already tried: restarting Roon Server multiple times, rebooting the Mac mini, clearing the Roon cache and temp folders, reinstalling with the latest Roon Server download, flushing macOS DNS cache, manually setting DNS to 8.8.8.8 and 1.1.1.1, disabling Tailscale VPN, and removing and re-adding Tidal. None have resolved the issue.

Mac mini is connected via ethernet.

Located in Dunedin, New Zealand.

Tell us about your home network

· VPN is off. TP link Dexo X20 mesh router + satellite, fibre with contact. ONT goes to the TP link router. Old router used as a dumb switch. Had no issues in the past until yesterday.

[vadim]

Hello @Dextro

Thank you for reaching Roon support.

I have enabled diagnostics on your account so our technical staff can get some more insight into what’s going on here. The next time your Roon Server is active a diagnostics report will automatically be generated and uploaded directly to our servers

I wanted to reach out because I’ve been keeping an eye on our servers, waiting for the aforementioned diagnostics report.

For some reason it is not reaching our servers, even after I tried re-enabling diagnostics on your account. I also ran a quick test and I was able to submit a similar report from my setup here, so something else is going on.

So we can move forward, I was hoping for now you could use the directions found here and send them to our Logs Uploader Service and let us know after, thanks!