nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Unleashed 200.19 does DNS lookup of dauth.cloud.ruckuswireless.com every 5 sec.

Alleprt

I run pi-holes. I noticed an uptick in DNS queries at about 6:30am EDT 2026/3/12. I discovered that my Unleashed is looking up this domain name dauth.cloud.ruckuswireless.com every 5 seconds and it caused the uptick. I inspected the pi-hole logs and found that Unleashed looked up this domain every 11 hours (yes, not a typo - eleven, seems unusual) prior to that date and time.

Why did it start doing this every 5 seconds? I am not using any cloud services. I upgraded to 200.19 from 200.18 about 3 days before it started happening. I haven't changed anything in the setup for quite a long time. The domain is resolved by my DNS successfully and the server responds to pings. I am out of ideas why this is happening. My APs are R750.

Find more posts tagged with

Accepted answers

sanjay_kumar

Thanks @Alleprt,
We are able to reproduce the issue and found the root cause.
This will get fixed in 200.19 MR. Current ETA is July 6th.

All comments

Alleprt

Is anybody here? I rebooted my APs and the lookup for that domain is back to every 11 hours. It would have been nice if someone could provide feedback on what happened. I am almost sure it will be back to every 5 seconds in some time.

sanjay_kumar

Hi @Alleprt,
Let me check on this.

sanjay_kumar

Hi,

I have been running the captures for couple hours now and I do not see any dns request to dauth.cloud.ruckuswireless.com.

Could you please let us know the request you see on your side? Probably a screen shot will help.

Alleprt

Hi Sanjay. Thank you for your reply. You need to run captures for at least 11-12 hours to see this query. Before the havoc started, queries to that domain were every 11 hours as I mentioned. Below is a screenshot from the log of my pi-hole. I rebooted my APs around 9:08 on March 16th and after that the queries went back to every 11 hours. But as you can see, before they were every 5 seconds.

Why would Unleashed try to connect to that domain? I am not using anything cloud. Please re-read my original post on how it all started. I guess it will start querying every 5 seconds in a couple of days again. This had never happened before I updated to 200.19.

sanjay_kumar

Hi,

The url dauth.ruckusnetworks.com is part of the AFCD process.
This process is usually for AP connecting to the cloud and disconnect.
During this process, AP will try to get the information on services like AFC (Automatic Frequency Coordination).

However, this should not happen every 5 seconds.
We are looking into this issue, I will get back to you.

sanjay_kumar

Hi,

We are able to reproduce the issue in lab, we have raised an issue with the engineering team to fix the issue.

Alleprt

Thank you for looking into it. Since I rebooted my APs on March 16th that domain has been queried every 11 hours, as expected I suppose.

If that domain is part of AFC process I don't understand why my Unleashed is trying to connect to it as my APs don't support the 6 GHz band, and I disabled it in settings just in case. Although Unleashed is universal and supports other APs with Wi-Fi 6E and 7, I would think it shouldn't do AFC when it's not supported by the hardware or when the band is disabled.

sanjay_kumar

Hi,

AFCD process is up in some APs especially R750 and 850.
Are you using in Dedicated Master mode?

Alleprt

No, I am not using a dedicated master mode.
How and why would R750s use AFC when they don't support WiFi 6E or 7 and don't even have a 6GHz band?

sanjay_kumar

Hi Alleprt,

Yes, you are correct. Which is why we are trying to check which info is AP trying to check and why the AFCD is happening every 5 seconds.

We are looking into this and we are able to reproduce the issue inhouse.
I will keep you posted on the updates.

sanjay_kumar

Hi,

The issue in our is no longer be able to reproduce, if you are still running on 200.19 and facing issue, can you provide a remote session so that we can collect the relevant information?

Alleprt

Hello. The issue never returned after I rebooted all APs when I noticed it. I observed it only after upgrading Unleashed from 200.18 to 200.19. Then, when I noticed the issue, I rebooted all APs and it never returned. It seems to be related to the upgrade process.

sanjay_kumar

Thanks @Alleprt,
We are able to reproduce the issue and found the root cause.
This will get fixed in 200.19 MR. Current ETA is July 6th.