Your company's network frequently faces problems with clients being unable to access websites by name using the primary name resolution server, set to query other servers for this information if it doesn't already have it. What is the most likely cause of these connectivity problems?
You selected this option
The name resolution server can't reach external servers because of incorrect firewall configurations
You selected this option
Security protocols on domain querying were activated, blocking all external name requests
You selected this option
The connectivity issues stem from having the caching feature disabled on the name resolution server
You selected this option
The presence of a rogue configuration protocol server is disrupting name query processes
In situations where a server that provides name lookups is set to pass queries to other name servers, issues can arise if it cannot reach these external servers due to incorrect network configurations, such as improperly set firewall rules. These servers attempt to obtain name resolution from up-chain servers, and if isolated by network barriers, clients will experience domain lookup failures. Incorrect answers include: Disabling cache impacts performance by not storing lookup results, but doesn't inherently prevent lookups; issues caused by a rogue configuration protocol server affect network addressing, not name querying directly; enabling security extensions secures query responses and does not generally block outgoing queries unless misconfigured.
Ask Bash
Bash is our AI bot, trained to help you pass your exam. AI Generated Content may display inaccurate information, always double-check anything important.
What role do firewalls play in network communication?
Open an interactive chat with Bash
What is a name resolution server and how does it work?
Open an interactive chat with Bash
What is caching in the context of a name resolution server?