Our Network team has raised concerns about a high volume of DNS requests originating from IGEL devices targeting the StoreFront URL and external gateway URLs. It appears this behaviour is related to the StoreFront beacon configuration. Currently: • The StoreFront base URL (base.externaldomain.com) is configured as the internal beacon • The gateway URLs (url1.externaldomain.com and url2.externaldomain.com) are set as external beacon checkpoints However, these external gateway URLs are not accessible internally. From what we’re observing, the IGEL devices are: 1. Attempting to reach the base URL 2. Then, try the external gateway URLs 3. Then retrying those external URLs with DNS suffixes appended 4. Potentially repeating this across multiple DNS servers This is causing a noticeable increase in DNS traffic. Is this expected behaviour for IGEL/StoreFront beacon detection? If so, are there any recommendations for fine-tuning or reducing the number of DNS requests from IGEL devices? Interestingly, this doesn’t appear to be a concern on Windows devices. Any insights or suggestions would be appreciated.

It is indeed expected. We saw the Same at a Customer with a large IGEL fleet couple of years ago. Back then we introduced a NetScaler loadbalanced DNS (LB) to „work around“ the issue. AFAIR we also raised a ticket with Citrix support which was closed with „Works as designed“.