Why do I get an DNS resolver alert on boot up?

Available Languages

Updated:August 12, 2014
Document ID:118252

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

Introduction

This document describes an alert that might be receieved during startup of Cisco Email Security Appliance (ESA).

Background Information

When booting or rebooting an Cisco Content Security Appliance appliance the below DNS-related alerts may be sent:

---

The Critical message is:

Failed to bootstrap the DNS resolver. Unable to contact root servers.
Please check DNS configuration and/or firewall settings.

---

Receiving this alert during or soon after system boot-up is not cause for concern.

The AsyncOS alerting mechanism can sometimes activate before the basic OS DNS sub systems are completely on line, causing the system to send this warning. A future version of AsyncOS will suppress this alert until the system is fully booted. However, if you receive this alert from a machine that has been running for a while, or the alert continues to be sent after the boot cycle is complete, the alert may indicate an issue

The AsyncOS alerting mechanism can sometimes activate before the basic OS DNS sub systems are completely on line, causing the system to send r firewall settings.'

Revision History

Revision Publish Date Comments
1.0
12-Aug-2014
Initial Release
TAC Authored

Contributed by Cisco Engineers

  • Stephan Fiebrandt and Chris Haag
    Cisco TAC Engineers.

Was this Document Helpful?

FeedbackFeedback

Contact Cisco

This Document Applies to These Products