On a Linux workstation, the route command takes a long time before printing out the routing table. Which of the following errors does that indicate?
On a Linux workstation, the route command takes a long time before printing out the routing table. Which of the following errors does that indicate?
When the route command takes a long time to print out the routing table on a Linux workstation, it likely indicates a problem with DNS resolution. By default, the route command attempts to resolve the names of routers and destinations to provide more readable output. If DNS resolution is not working properly, the command may experience timeouts while trying to lookup these names, leading to a delay in displaying the routing table. This can be bypassed by using the '-n' option with the route command, which tells it not to perform DNS lookups.
you may have a DNS resolution issue causing the slowdown
"The typical reason is that route tries to map the IP addresses in the table into their DNS names - and that can be quite slow because of the vagaries of the DNS system and your network." - https://serverfault.com/questions/397380/listing-the-routing-table-takes-long-time-to-complete
Correct: E "By default, this can be as long as 30 seconds! That means if a nameserver is not available, it will take a while before it tries the next one. And typically it won’t remind that this nameserver is down, so other DNS requests may have to experience the timeout as well." https://linux-audit.com/linux-dns-tuning-for-performance-and-resilience/
This doesn't seem correct, routing tables use ip instead of dns?
Ah or it does a resolve name from ip?
I think the correct is B. But I'm not sure.
E allora che scrivi
To bypass name resolution (that's default) you have to use "-n" options. Correct Answers D.
Sorry E.
I see this article said about DNS: https://serverfault.com/questions/397380/listing-the-routing-table-takes-long-time-to-complete