cancel
Showing results for 
Search instead for 
Did you mean: 

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

Alleprt
New Contributor II

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.

1 ACCEPTED SOLUTION

sanjay_kumar
Moderator
Moderator

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.

View solution in original post

13 REPLIES 13

sanjay_kumar
Moderator
Moderator

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
Moderator
Moderator

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?

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
Moderator
Moderator

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.