Explains how Cisco IOS XR resolves hostnames and addresses through static and dynamic cache entries, configured domain names, and DNS servers, and provides a task for configuring and verifying the resolver.
Domain name services are BSD-compatible resolver functions that
-
maintain static and dynamic hostname-to-address cache entries
-
complete unqualified hostnames with a default domain or domain list, and
-
query configured DNS servers when the local cache does not contain a requested mapping.
Applications such as Telnet and commands such as ping and traceroute request hostname or address resolution through a remote procedure call.
The domain service checks the local cache first, which reduces the time required to resolve previously stored mappings. If no entry exists, the domain service sends a DNS query to a name server and stores the response as a dynamic entry.
DNS name servers maintain distributed hostname-to-address mappings. You can configure one or more name servers for the resolver.
Cache and domain settings
The resolver uses these entry and configuration types.
-
Static entry: Created with a domain ipv4 host or domain ipv6 host command.
-
Dynamic entry: Received from a configured name server.
-
Name server: Configured with the domain name-server command. You can configure one or more name servers.
-
Default domain: Configured with the domain name command. The resolver appends this domain to an unqualified hostname before adding the completed hostname to the host table.
-
Domain list: Configured with the domain list command. The list supplies candidate domains for an unqualified hostname.