I am currently experiencing trouble with the name resolution of tau.mcafee.com(for GAM update). Since sensor doesn't have nslookup or any related command, I only use my laptop to check for the NS resolution of tau.mcafee.com which then returns the image below.
When I use "tau.mcafee.com." in my laptop the query goes smoothly but when I add a dot (.) on the DNS suffix of the sensor, it still can't resolve the URL. Is there any way to further check this issue?
We were currently working on the automatic updating of GAM in the sensors but they keep getting "Sending update request failed". After isolating the proxy connectivity, we have observed the issue above when performing nslookups. I think it is affecting the way the sensor performs name resolution so I added a DNS Suffix dot (.) but still it the same error occurs.
What Manager version / Sensor model / Sensor software are you using?
On your NSM if you go to Devices > <Sensor_Name> Setup > Name Resolution, does it show Name Resolution as enabled?
Does the McAfee.com domain resolve if you use the test connection option?
Have you tried manually updating GAM and did it work?
Where are you seeing the error, is it in the UI or the log files?
Do you have a firewall rule to allow the sensor to connect to McAfee.com?
The sensors use native DNS for name resolution. Do you have a DNS server/forwarder they can use? This will be required on networks with no external DNS resolution (i.e. for clients to access the internet, http/https requests go to the proxy that does the dns lookup for the client)