CCNA Network Services and Security Practice Question
Network Topology
You are connected to R1, a Cisco IOS-XE router that serves as the DNS resolver for the local network. The router can reach the DNS server at 198.51.100.53, but internal hosts cannot resolve the hostname 'fileserver.courseiva.com' (expected IP 203.0.113.10). Which configuration will resolve the issue?
⚠ Common exam trap
Candidates often attempt to change the DNS server IP or troubleshoot routing, but the core issue is the absence of a DNS record. The `ip host` command provides a simple, static solution without altering external DNS infrastructure.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Add a static host entry: ip host fileserver.courseiva.com 203.0.113.10
The DNS server is reachable but does not have an A record for fileserver.courseiva.com, so NXDOMAIN is returned. The router can resolve the name locally by adding a static host entry with `ip host`. This bypasses the external DNS and directly maps the hostname to the correct IP. Changing the DNS server to another unknown IP does not guarantee resolution, and static routes or external public DNS are irrelevant for this internal name.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Add a static host entry: ip host fileserver.courseiva.com 203.0.113.10
Why this is correct
This is the correct fix. The 'ip host' command populates the router's local DNS cache with a static mapping, so when the router queries 'fileserver.courseiva.com', it immediately returns 203.0.113.10 without sending a DNS request to the external server. Since the configured DNS server at 198.51.100.53 is reachable but lacks the necessary A record, a static entry bypasses the broken DNS resolution entirely. The command 'ip host fileserver.courseiva.com 203.0.113.10' is equivalent to adding an entry to the router's local hosts table, which takes precedence over DNS queries for that name.
- ✗
Change the DNS server to 203.0.113.53 using the command 'ip name-server 203.0.113.53'
Why it's wrong here
This is incorrect because the question states that the router can reach the DNS server at 198.51.100.53, but that server lacks the required records. Simply changing to a different DNS server (203.0.113.53) might work if that server has the correct records, but the question does not provide evidence that 203.0.113.53 is a valid DNS server. The correct fix is to add static entries on the router.
- ✗
Add a static route to 198.51.100.53 via the next-hop interface
Why it's wrong here
This is incorrect because the router can already reach the DNS server (198.51.100.53). The problem is not about reachability but about the DNS records on that server. Adding a static route does not affect DNS resolution.
- ✗
Configure the router to use the DNS server at 8.8.8.8 using 'ip name-server 8.8.8.8'
Why it's wrong here
This is incorrect because while 8.8.8.8 is a public DNS server, the question does not indicate that it has the required records for 'fileserver.courseiva.com'. Moreover, using a public DNS server may not be appropriate for internal hostnames, and the router may not have internet access. The correct solution is to add static entries.
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.
✓Add a static host entry: ip host fileserver.courseiva.com 203.0.113.10Correct answer▾
Why this is correct
This is the correct fix. The 'ip host' command populates the router's local DNS cache with a static mapping, so when the router queries 'fileserver.courseiva.com', it immediately returns 203.0.113.10 without sending a DNS request to the external server. Since the configured DNS server at 198.51.100.53 is reachable but lacks the necessary A record, a static entry bypasses the broken DNS resolution entirely. The command 'ip host fileserver.courseiva.com 203.0.113.10' is equivalent to adding an entry to the router's local hosts table, which takes precedence over DNS queries for that name.
✗Change the DNS server to 203.0.113.53 using the command 'ip name-server 203.0.113.53'Wrong answer — click to see why▾
Why this is wrong here
The current DNS server is reachable but lacks the record; simply changing the DNS server to an arbitrary IP would not guarantee resolution unless that server is known to hold the correct record, and there is no indication that 203.0.113.53 is a valid DNS server.
Why candidates choose this
Candidates pick this because they think the issue is with the DNS server IP, and they assume 203.0.113.53 might be a working DNS server, confusing the host IP with a DNS server address.
✗Add a static route to 198.51.100.53 via the next-hop interfaceWrong answer — click to see why▾
Why this is wrong here
DNS resolution failure is not due to routing: the router can already reach the DNS server. Adding a static route will not fix missing DNS records.
Why candidates choose this
Candidates pick this because they think the router cannot reach the DNS server, even though the question states it can. They may confuse DNS resolution issues with routing problems.
✗Configure the router to use the DNS server at 8.8.8.8 using 'ip name-server 8.8.8.8'Wrong answer — click to see why▾
Why this is wrong here
The Google public DNS server likely does not have an entry for the internal hostname fileserver.courseiva.com, so this will not enable resolution.
Why candidates choose this
Candidates pick this because 8.8.8.8 is a well-known DNS server, and they assume it will resolve any hostname. They overlook that the hostname is internal and not registered in public DNS.
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?”
Visual reference
Quick reference
Common DNS Record Types
| Record | Purpose | Example |
|---|---|---|
| A | IPv4 address mapping | example.com → 93.184.216.34 |
| AAAA | IPv6 address mapping | example.com → 2606:2800::1 |
| CNAME | Alias to another hostname | www → example.com |
| MX | Mail server for domain | example.com → mail.example.com (priority 10) |
| TXT | Text data (SPF, DKIM, verification) | v=spf1 include:_spf.example.com ~all |
| NS | Authoritative name servers | example.com NS ns1.example.com |
| PTR | Reverse DNS (IP → hostname) | 34.216.184.93.in-addr.arpa → example.com |
| SOA | Zone authority record | Primary NS, admin email, serial, TTL defaults |
Go deeper
Related to this question
Learn chapter
Diagnosing DNS Record Issues — A, AAAA, CNAME, MX, NS, and PTR Records
Key term
CAN
A CAN (Controller Area Network) is a robust vehicle bus standard designed to allow microcontrollers and devices to communicate with each other without a host computer.
Key term
Fully Qualified Domain Name
A Fully Qualified Domain Name is the complete and unambiguous website or server name that includes the host, domain, and top-level domain, leaving no room for guesswork.
About these practice questions
This 200-301 question is part of Courseiva's 1,389-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
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.