The answer is to configure the correct DNS server IP under global configuration with the command `ip name-server 203.0.113.10` and ensure the DNS server hosts an A record mapping www.example.com to 203.0.113.100. This resolves the DNS resolution troubleshooting scenario because the router was previously pointing to a non-functional name-server (10.0.0.2), causing the server failure response during nslookup. Even though the DNS server was reachable via ping, the router could not query it for name resolution due to the misconfigured address. On the CCNA 200-301 v2 exam, this tests your ability to diagnose layer 3 connectivity versus application-layer DNS configuration—a common trap is assuming reachability equals proper resolution. Remember that `ip name-server` must match the actual DNS server, and without a valid A record, forward lookups will fail. For reverse lookups, a corresponding PTR record is also required. Memory tip: "Name the server correctly, or your lookup will be wrecked."
CCNA Network Services and Security Practice Question
This 200-301 practice question tests your understanding of network services and security. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
Network Topology
You are connected to R1 via the console. The network has a DNS server at 203.0.113.10 that should resolve www.example.com to 203.0.113.100. However, when you ping www.example.com, it fails. Diagnose and resolve the DNS resolution issue. The DNS server is reachable via ping, but nslookup from R1 returns a server failure. Configure R1 so that it can successfully resolve www.example.com. Additionally, verify that the DNS server is correctly configured for forward and reverse lookups.
R1# show running-config | section ip domain
ip domain lookup
ip name-server 10.0.0.2
ip domain timeout 3
ip domain retry 2
!
R1# ping 203.0.113.10
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 203.0.113.10, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/2/4 ms
R1# nslookup www.example.com
Server: 10.0.0.2
Address: 10.0.0.2#53
** server can't find www.example.com: SERVFAIL
R1# dig www.example.com @203.0.113.10
; <<>> DiG 9.11.3 <<>> www.example.com @203.0.113.10
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 12345
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;www.example.com. IN A
;; Query time: 2 msec
;; SERVER: 203.0.113.10#53(203.0.113.10)
;; WHEN: Mon Jan 01 00:00:00 UTC 2024
;; MSG SIZE rcvd: 45
R1# show ip interface brief
Interface IP-Address OK? Method Status Protocol
GigabitEthernet0/0 10.0.0.1 YES NVRAM up up
GigabitEthernet0/1 203.0.113.2 YES NVRAM up up
Loopback0 192.0.2.1 YES NVRAM up up
A
Configure 'ip name-server 203.0.113.10' under global configuration and ensure the DNS server has an A record for www.example.com pointing to 203.0.113.100.
This is correct because the router's DNS resolver must be pointed to the correct DNS server IP. The 'ip name-server' command specifies the DNS server to use. Additionally, the DNS server must have the proper A record for the hostname to be resolved.
B
Configure 'ip domain-lookup' and 'ip name-server 10.0.0.2' under global configuration, then verify with ping www.example.com.
Why wrong: This is incorrect because the DNS server IP 10.0.0.2 is not the actual DNS server (203.0.113.10). Even if domain-lookup is enabled, the router will query the wrong server, causing resolution failure.
C
Configure 'ip domain-lookup' and 'ip host www.example.com 203.0.113.100' under global configuration, then verify with ping www.example.com.
Why wrong: This is incorrect because using a static host entry bypasses DNS resolution entirely. While it would make ping succeed, it does not resolve the DNS issue; the router would not query the DNS server, and nslookup would still fail.
D
Configure 'ip dns server' under global configuration to make R1 act as a DNS server, then add an A record for www.example.com.
Why wrong: This is incorrect because making R1 a DNS server is unnecessary and does not fix the issue. The problem is that R1 is not querying the correct DNS server; enabling DNS server functionality on R1 would require additional configuration and is not the intended solution.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Configure 'ip name-server 203.0.113.10' under global configuration and ensure the DNS server has an A record for www.example.com pointing to 203.0.113.100.
The issue is that the DNS server IP address configured under 'ip name-server' is incorrect (10.0.0.2) instead of the actual DNS server (203.0.113.10). Additionally, the DNS server itself is not configured with the proper A record for www.example.com. The fix involves correcting the name-server address and ensuring the DNS server has the correct forward mapping. After correcting the name-server, nslookup and dig should return the IP address 203.0.113.100. For reverse lookup, a PTR record for 203.0.113.100 pointing to www.example.com must exist on the DNS server.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✓
Configure 'ip name-server 203.0.113.10' under global configuration and ensure the DNS server has an A record for www.example.com pointing to 203.0.113.100.
Why this is correct
This is correct because the router's DNS resolver must be pointed to the correct DNS server IP. The 'ip name-server' command specifies the DNS server to use. Additionally, the DNS server must have the proper A record for the hostname to be resolved.
Related concept
Read the scenario before looking for a memorised answer.
✗
Configure 'ip domain-lookup' and 'ip name-server 10.0.0.2' under global configuration, then verify with ping www.example.com.
Why it's wrong here
This is incorrect because the DNS server IP 10.0.0.2 is not the actual DNS server (203.0.113.10). Even if domain-lookup is enabled, the router will query the wrong server, causing resolution failure.
✗
Configure 'ip domain-lookup' and 'ip host www.example.com 203.0.113.100' under global configuration, then verify with ping www.example.com.
Why it's wrong here
This is incorrect because using a static host entry bypasses DNS resolution entirely. While it would make ping succeed, it does not resolve the DNS issue; the router would not query the DNS server, and nslookup would still fail.
✗
Configure 'ip dns server' under global configuration to make R1 act as a DNS server, then add an A record for www.example.com.
Why it's wrong here
This is incorrect because making R1 a DNS server is unnecessary and does not fix the issue. The problem is that R1 is not querying the correct DNS server; enabling DNS server functionality on R1 would require additional configuration and is not the intended solution.
Option-by-option analysis
Why each answer is right or wrong
Understanding why wrong answers are wrong — and when they would be correct — is what separates a 750 score from a 900. The 200-301 exam frequently reuses these exact scenarios with slightly different constraints.
✓Configure 'ip name-server 203.0.113.10' under global configuration and ensure the DNS server has an A record for www.example.com pointing to 203.0.113.100.Correct answer▾
Why this is correct
This is correct because the router's DNS resolver must be pointed to the correct DNS server IP. The 'ip name-server' command specifies the DNS server to use. Additionally, the DNS server must have the proper A record for the hostname to be resolved.
✗Configure 'ip domain-lookup' and 'ip name-server 10.0.0.2' under global configuration, then verify with ping www.example.com.Wrong answer — click to see why▾
Why this is wrong here
The specific factual error: The name-server address must match the actual DNS server; using 10.0.0.2 will not resolve the hostname.
Why candidates choose this
Candidates might think that enabling domain-lookup is sufficient and that any DNS server will work, or they may confuse the IP addresses.
✗Configure 'ip domain-lookup' and 'ip host www.example.com 203.0.113.100' under global configuration, then verify with ping www.example.com.Wrong answer — click to see why▾
Why this is wrong here
The specific factual error: The 'ip host' command creates a static mapping, not a DNS resolution. The question requires DNS resolution to work, not a static override.
Why candidates choose this
Candidates might think that creating a static host entry is a valid fix for DNS problems, but it does not address the underlying DNS configuration.
✗Configure 'ip dns server' under global configuration to make R1 act as a DNS server, then add an A record for www.example.com.Wrong answer — click to see why▾
Why this is wrong here
The specific factual error: The 'ip dns server' command enables DNS server services on the router, but the router is not meant to be a DNS server in this scenario. The fix is to point to the existing DNS server.
Why candidates choose this
Candidates might confuse the client-side DNS resolver with the server-side DNS service, thinking that enabling DNS server on R1 will resolve the issue.
Analysis generated from the official 200-301blueprint and verified against question context. The “when correct” sections are what AI assistants cite when candidates ask “what’s the difference between these options?”
Common exam traps
Common exam trap: answer the scenario, not the keyword
Many certification questions include familiar terms but test a specific constraint. Read the exact wording before choosing an answer that is generally true but wrong for this case.
Detailed technical explanation
How to think about this question
This question should be treated as a scenario, not a definition check. Identify the problem, the constraint and the best action. Then compare each option against those facts.
KKey Concepts to Remember
Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.
Use explanations to understand the rule behind the answer.
TExam Day Tips
→Underline the problem statement mentally.
→Watch for words such as best, first, most likely and least administrative effort.
→Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A practitioner preparing for the 200-301 exam encounters this exact type of scenario on the job. The correct answer here is not the most general option — it is the best answer for the specific constraint described. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Real exam questions reward reading the full scenario before eliminating options, because the constraint defines which answer fits.
Related glossary terms
Concepts from this question explained
These glossary pages explain the core terms tested in this 200-301 question in full detail.
Identify which 200-301 exam domain this question belongs to, then review the specific concept being tested. Practise related questions in that domain and focus on understanding why each wrong answer is tempting — not just why the correct answer is right.
Network Services and Security — This question tests Network Services and Security — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Configure 'ip name-server 203.0.113.10' under global configuration and ensure the DNS server has an A record for www.example.com pointing to 203.0.113.100. — The issue is that the DNS server IP address configured under 'ip name-server' is incorrect (10.0.0.2) instead of the actual DNS server (203.0.113.10). Additionally, the DNS server itself is not configured with the proper A record for www.example.com. The fix involves correcting the name-server address and ensuring the DNS server has the correct forward mapping. After correcting the name-server, nslookup and dig should return the IP address 203.0.113.100. For reverse lookup, a PTR record for 203.0.113.100 pointing to www.example.com must exist on the DNS server.
What should I do if I get this 200-301 question wrong?
Identify which 200-301 exam domain this question belongs to, then review the specific concept being tested. Practise related questions in that domain and focus on understanding why each wrong answer is tempting — not just why the correct answer is right.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. You are connected to R1. The network uses DNS to resolve hostnames for remote device management. Currently, R1 cannot resolve the hostname 'ServerA' via DNS. Using the nslookup and dig commands, you have gathered the following outputs:
nslookup ServerA
Server: 203.0.113.1
Address: 203.0.113.1#53
Name: ServerA.example.com
Address: 203.0.113.10
dig ServerA
...
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: ...
...
The show running-config command shows that 'ip domain-lookup' is enabled, the name-server is 203.0.113.1, and no static host entries are configured. Diagnose and fix the DNS resolution failure. Ensure that R1 can successfully resolve 'ServerA' to its intended IP address 198.51.100.10.
hard
✓ A.Add a static host entry: 'ip host ServerA 198.51.100.10'
B.Change the DNS server to 8.8.8.8 using 'ip name-server 8.8.8.8'
C.Enable 'ip domain lookup' with 'ip domain-lookup' command
D.Configure the correct domain name using 'ip domain-name example.com'
Why A: The nslookup output misleadingly shows a response with IP 203.0.113.10, but the dig output reveals NXDOMAIN, indicating the DNS server has no valid A record for ServerA. The returned address is a default domain record that does not point to the correct device. Since the external DNS server cannot be modified, the quickest and valid fix is to add a static host entry on R1 using 'ip host ServerA 198.51.100.10', which overrides DNS and ensures correct resolution. Option B is incorrect because changing to 8.8.8.8 would still depend on a remote server having the correct record, which is not guaranteed. Option C is wrong because 'ip domain-lookup' is already enabled, so disabling/enabling it has no effect. Option D is wrong because modifying the domain name only affects how FQDN is built but does not fix the missing A record or wrong IP issue.
Last reviewed: Jun 6, 2026
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
This 200-301 practice question is part of Courseiva's free Cisco certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the 200-301 exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.