Trustwave and Cybereason Merge to Form Global MDR Powerhouse for Unparalleled Cybersecurity Value. Learn More

Trustwave and Cybereason Merge to Form Global MDR Powerhouse for Unparalleled Cybersecurity Value. Learn More

Services
Managed Detection & Response

Eliminate active threats with 24/7 threat detection, investigation, and response.

Co-Managed SOC (SIEM)

Maximize your SIEM investment, stop alert fatigue, and enhance your team with hybrid security operations support.

Advisory & Diagnostics

Advance your cybersecurity program and get expert guidance where you need it most.

Penetration Testing

Test your physical locations and IT infrastructure to shore up weaknesses before exploitation.

Database Security

Prevent unauthorized access and exceed compliance requirements.

Email Security

Stop email threats others miss and secure your organization against the #1 ransomware attack vector.

Digital Forensics & Incident Response

Prepare for the inevitable with 24/7 global breach response in-region and available on-site.

Firewall & Technology Management

Mitigate risk of a cyberattack with 24/7 incident and health monitoring and the latest threat intelligence.

Solutions
BY TOPIC
Microsoft Security
Unlock the full power of Microsoft Security
Offensive Security
Solutions to maximize your security ROI
Rapidly Secure New Environments
Security for rapid response situations
Securing the Cloud
Safely navigate and stay protected
Securing the IoT Landscape
Test, monitor and secure network objects
Why Trustwave
About Us
Awards and Accolades
Trustwave SpiderLabs Team
Trustwave Fusion Security Operations Platform
Trustwave Security Colony
Partners
Technology Alliance Partners
Key alliances who align and support our ecosystem of security offerings
Trustwave PartnerOne Program
Join forces with Trustwave to protect against the most advance cybersecurity threats
Loading...
Loading...

PRB: DNS alerts appear in the MailMarshal Console

Expand / Collapse


This article applies to:

  • Trustwave MailMarshal (SEG)

Symptoms:

  • DNS alerts display in the MailMarshal Console.
  • DNS alert: 'Unable to contact DNS Server'.
  • DNS alert: 'DNS Server is now reachable'.

Causes:

Generally, the DNS alerts seen in the MailMarshal Console are not critical, unless they are a result of a genuine delivery problem caused by failed domain resolution. There is no timeout value you can set for the DNS lookups; MailMarshal does, however, allow you to alter the number of successively failed DNS lookups that raise an alert.

Each attempt to resolve an address uses a multiple retry strategy that times out after 80 seconds, having tried both DNS servers with increasing wait times (5, 10, 20, and then 40 seconds).

Reply:

You may receive a large number of harmless DNS alerts in the MailMarshal Console due to successive resolution failures.  It is possible to reduce the number of alerts caused by DNS problems.

Note: This procedure only reduces the likelihood of raising an alertIf you have legitimate DNS resolution issues, this change will not correct the DNS problem itself.

Warning: Using the Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Trustwave cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Make sure that you backup your Registry prior to making any changes.

To reduce the number of alerts, add an Advanced Setting (8.X and below, a registry value):

10.0 and above: 

  1. In the Management Console, add an Advanced Setting as follows:
    • DNS.DNSAlertTriggerCount
    • Type: Integer
    • Value: 10
  2. Commit Configuration Changes.
  3. Restart MailMarshal services on the processing servers.

8.X and below:

  1. On the Array Manager, edit the Registry
  2. Navigate to the SEG DNS key:
    • In version 8.X: HKEY_LOCAL_MACHINE\SOFTWARE\Trustwave\Secure Email Gateway\Default\DNS
    • For full details of the location for each product version, see article Q10832.
  3. Add a value of type: DWORD (integer)
    Name: DNSAlertTriggerCount
    Data: 10
  4. Commit Configuration Changes.
  5. Restart MailMarshal services on the processing servers.

 

This article was previously published as:
NETIQKB42720

To contact Trustwave about this article or to request support:


Rate this Article:
     
Tags:

Add Your Comments


Comment submission is disabled for anonymous users.
Please send feedback to Trustwave Technical Support or the Webmaster
.