--- title: "DNS connectivity and reputation issues" slug: "dns-connectivity-and-reputation-issues" tags: ["Product Usage", "IPS 10.1.10"] updated: 2026-10-05T15:40:13Z published: 2026-10-05T15:40:13Z canonical: "docs.trellix.com/dns-connectivity-and-reputation-issues" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.trellix.com/llms.txt > Use this file to discover all available pages before exploring further. # DNS connectivity and reputation issues **DNS connectivity** DNS connectivity to the Sensor sometimes has issues due to incorrect configuration or incorrect DNS server IP address. You can view the DNS connectivity fault on the **Faults** tab page in the Manager. The **Device DNS server connectivity status** faults are generated by the Sensor whenever there is an issue in DNS connectivity. DNS server connectivity warning fault ![](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/GUID-37F7F118-46BC-4EC2-9451-D6F3380D7470-low.png?sv=2026-02-06&spr=https&st=2026-11-22T12%3A52%3A57Z&se=2026-11-22T13%3A52%3A57Z&sr=c&sp=r&sig=CFVlkLPjyTjexhl0AttQaWzdJQO9bmkdq7rn6PFKer4%3D) You can perform the following high-level troubleshooting steps to solve the connectivity problem: 1. Check the **Devices** → **** → **Global** → **Common Device Settings** → **Name Resolution** for the global level setting in the Manager to see if the parent domain has the primary and secondary DNS server information entered correctly. Global level DNS server setting ![](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/GUID-83684496-E5EB-4BED-B4C0-DE43C85FDC36-low.png?sv=2026-02-06&spr=https&st=2026-11-22T12%3A52%3A57Z&se=2026-11-22T13%3A52%3A57Z&sr=c&sp=r&sig=CFVlkLPjyTjexhl0AttQaWzdJQO9bmkdq7rn6PFKer4%3D) 2. If the global setting has the correct information, check the **Devices** → **** → **Devices** → **** → **Setup** → **Name Resolution** device level setting to see if it inherits the global settings. Make sure that the **Inherit Settings?** is selected and also check if the inherited information is correct. Device level DNS server setting ![](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/GUID-DF94CE65-7C75-44A5-A97E-C473F23E79A5-low.png?sv=2026-02-06&spr=https&st=2026-11-22T12%3A52%3A57Z&se=2026-11-22T13%3A52%3A57Z&sr=c&sp=r&sig=CFVlkLPjyTjexhl0AttQaWzdJQO9bmkdq7rn6PFKer4%3D) If the connectivity problem still persists contact Trellix Support for further assistance. **GTI file reputation** In case of any errors for file reputation analysis, you can perform the following high-level troubleshooting steps: 1. Check if the malware detection is enabled in **Policy** → **** → **Intrusion Prevention** → **Policy Types** → **Advanced Malware Policies**. 2. In case of file reputation, the request is sent for bad file reputation. The file is sent as an MD5 checksum in DNS requests. If there is no response from the DNS, check the DNS connectivity. If the DNS connectivity has any issues, perform the high-level steps mentioned under **DNS connectivity** to solve the problem. If the DNS connectivity is working correctly, there will be a response for the file reputation request. Confirm the connectivity by executing and checking the output of show malwareenginestats CLI command. Check the output of malware statistics for GTI file reputation engine. The Number of files sent and Number of response Received should show an increase in comparison with the number of files sent/received before sending the reputation request. Malware Statistics for GTI File Reputation Engine Number of files sent: 11132 Number of response Received: 9377 Number of files ignored: 1755 Number of files with malware score clean: 0 Number of alerts with malware score very low: 37 Number of alerts with malware score low: 0 Number of alerts with malware score medium: 0 Number of alerts with malware score high: 0 Number of alerts with malware score very high: 1233 Number of alerts with malware score unknown: 8051 Total number of alerts sent: 1233 Total number of attacks blocked: 1233 Total number of TCP resets sent: 1233 If the connectivity problem still persists contact Trellix Support for further assistance. **GTI IP reputation** When a syn packet is seen, the Sensor checks to see if IP reputation is enabled for that port/protocol. When enabled, the Sensor sends a query to the management process. The first flow is always allowed to pass through since the reputation score is not available. After a reputation score is assigned to the packet, the score is updated to the Sensor. The subsequent flows from the same IP address is marked with the reputation score in the header for lookup in datapath processor. Source IP is checked for inbound flows, and destination IP is checked for outbound flows, even though the entire 5-tuple is passed in the query. The **Sensor connectivity status with GTI server** critical fault is generated by the Sensor in the Manager whenever the GTI server has connectivity issues to the Sensor. You can perform the following high-level troubleshooting steps to solve the connectivity problem: 1. Check if proxy configuration is required. If the organization has a firewall/proxy between the Sensor management port and the cloud, the proxy has to be configured with username/password, if required. You can configure the proxy server under **Manager** → **** → **Setup** → **Proxy Server**. 2. Port 443 should not be blocked on the management port network. 3. Check the **Devices** → **** → **Global** → **Common Device Settings** → **Name Resolution** for the global level setting in the Manager to see if the parent domain has the primary and secondary DNS server information entered correctly. If the connectivity problem still persists, contact Trellix Support for further assistance.