XG Firewall v18 MR-5: Feedback and experiences

Finally got round to applying MR5 Build586  on Hyper-V,

First thing I noticed after rebooting, was that the fqdnd service was dead, so I had to manually start that.

However,  all authenticated web proxy users could not get internet access and were getting a "Blocked Site" error page
All clientless devices, or devices that didn't use the proxy were fine. If I did a Policy test, all was good for the blocked users.

Using a Home Subscription, but with a Home Lab setup so I use AD to authenticate. Rebooting the DCs had no effect, nor did rebooting XG

Only solution was to roll back to MR4.. 

Finally got round to applying MR5 Build586  on Hyper-V,

First thing I noticed after rebooting, was that the fqdnd service was dead, so I had to manually start that.

However,  all authenticated web proxy users could not get internet access and were getting a "Blocked Site" error page
All clientless devices, or devices that didn't use the proxy were fine. If I did a Policy test, all was good for the blocked users.

Using a Home Subscription, but with a Home Lab setup so I use AD to authenticate. Rebooting the DCs had no effect, nor did rebooting XG

Only solution was to roll back to MR4..