LX0-104 · Question #56
On a regular users workstation the route command takes a long time before printing out the routing table. Which of the following errors does that indicate?
The correct answer is D. DNS resolution may not be working as route by default tries to resolve names of routers and. When the route command takes an extended time to display the routing table, it typically signifies an issue with DNS resolution. By default, route attempts to resolve the IP addresses of gateways and destinations to hostnames, causing delays if DNS is slow or unreachable.
Question
Options
- AThe local routing information may be corrupted and must be re-validated using a routing protocol.
- BOne of the routers in the routing table is not available which causes the automatic router failure
- CThere may accidentally be more than one default router in which case a default router election
- DDNS resolution may not be working as route by default tries to resolve names of routers and
How the community answered
(36 responses)- A6% (2)
- B3% (1)
- C8% (3)
- D83% (30)
Why each option
When the `route` command takes an extended time to display the routing table, it typically signifies an issue with DNS resolution. By default, `route` attempts to resolve the IP addresses of gateways and destinations to hostnames, causing delays if DNS is slow or unreachable.
Corrupted local routing information or issues with routing protocols might prevent the routing table from being displayed correctly, but wouldn't typically cause a long delay specifically while printing.
An unavailable router might affect traffic forwarding but does not directly cause the `route` command itself to delay its output while listing the table, as the table entries are local.
Multiple default routers or a default router election process would impact routing decisions but would not cause the `route` command to take a long time to display the existing kernel routing table.
The `route` command, by default, attempts to resolve IP addresses of gateways and destination networks into hostnames for a more human-readable output. If DNS resolution is slow, misconfigured, or unreachable, these name lookups will time out, causing a significant delay before the routing table is fully displayed.
Concept tested: Troubleshooting `route` command delays due to DNS
Topics
Community Discussion
No community discussion yet for this question.