05-DNS Configuration
Chapters Download (169.61 KB)
Dynamic Domain Name Resolution
Configuring the IPv4 DNS Client
Configuring Static Domain Name Resolution
Configuring Dynamic Domain Name Resolution
Displaying and Maintaining IPv4 DNS
IPv4 DNS Configuration Examples
Static Domain Name Resolution Configuration Example
Dynamic Domain Name Resolution Configuration Example
Troubleshooting IPv4 DNS Configuration
When configuring DNS, go to these sections for information you are interested in:
l Configuring the IPv4 DNS Client
l Displaying and Maintaining IPv4 DNS
l IPv4 DNS Configuration Examples
l Troubleshooting IPv4 DNS Configuration
Domain Name System (DNS) is a distributed database used by TCP/IP applications to translate domain names into corresponding IP addresses. With DNS, you can use easy-to-remember domain names in some applications and let the DNS server translate them into correct IP addresses.
There are two types of DNS services, static and dynamic. After a user specifies a name, the device checks the local static name resolution table for an IP address. If no IP address is available, it contacts the DNS server for dynamic name resolution, which takes more time than static name resolution. Therefore, some frequently queried name-to-IP address mappings are stored in the local static name resolution table to improve efficiency.
The static domain name resolution means setting up mappings between domain names and IP addresses. IP addresses of the corresponding domain names can be found in the static domain resolution table when you use applications such as Telnet.
Dynamic domain name resolution is implemented by querying the DNS server. The resolution procedure is as follows:
1) A user program sends a name query to the resolver of the DNS client.
2) The DNS resolver looks up the local domain name cache for a match. If a match is found, it sends the corresponding IP address back. If not, it sends a query to the DNS server.
3) The DNS server looks up the corresponding IP address of the domain name in its DNS database. If no match is found, it sends a query to a higher level DNS server. This process continues until a result, whether successful or not, is returned.
4) The DNS client returns the resolution result to the application after receiving a response from the DNS server.
Figure 1-1 Dynamic domain name resolution
Figure 1-1 shows the relationship between the user program, DNS client, and DNS server.
The resolver and cache comprise the DNS client. The user program and DNS client can run on the same device or different devices, while the DNS server and the DNS client usually run on different devices.
Dynamic domain name resolution allows the DNS client to store latest mappings between domain names and IP addresses in the dynamic domain name cache. There is no need to send a request to the DNS server for a repeated query next time. The aged mappings are removed from the cache after some time, and latest entries are required from the DNS server. The DNS server decides how long a mapping is valid, and the DNS client gets the aging information from DNS messages.
The DNS client normally holds a list of suffixes which can be defined by users. It is used when the name to be resolved is incomplete. The resolver can supply the missing part. For example, a user can configure com as the suffix for aabbcc.com. The user only needs to type aabbcc to get the IP address of aabbcc.com. The resolver can add the suffix and delimiter before passing the name to the DNS server.
l If there is no dot in the domain name (for example, aabbcc), the resolver will consider this a host name and add a DNS suffix before query. If no match is found after all the configured suffixes are used respectively, the original domain name (for example, aabbcc) is used for query.
l If there is a dot in the domain name (for example, www.aabbcc), the resolver will directly use this domain name for query. If the query fails, the resolver adds a DNS suffix for another query.
l If the dot is at the end of the domain name (for example, aabbcc.com.), the resolver will consider it a fully qualified domain name (FQDN) and return the query result, successful or failed. Hence, the dot (.) at the end of the domain name is called the terminating symbol.
Currently, the device supports static and dynamic DNS services.
If an alias is configured for a domain name on the DNS server, the device can resolve the alias into the IP address of the host.
Configuring static domain name resolution refers to specifying the mappings between host names and IPv4 addresses. Static domain name resolution allows applications such as Telnet to contact hosts by using host names instead of IPv4 addresses.
Follow these steps to configure static domain name resolution:
|
To do… |
Use the command… |
Remarks |
|
Enter system view |
system-view |
–– |
|
Configure a mapping between a host name and an IPv4 address |
ip host hostname ip-address |
Required Not configured by default. |
l The IPv4 address you last assign to the host name will overwrite the previous one if there is any.
l You may create up to 50 static mappings between domain names and IPv4 addresses.
To send DNS queries to a correct server for resolution, dynamic domain name resolution needs to be enabled and a DNS server needs to be configured.
In addition, you can configure a DNS suffix that the system will automatically add to the provided domain name for resolution.
Follow these steps to configure dynamic domain name resolution:
|
Use the command… |
Remarks |
|
|
Enter system view |
system-view |
— |
|
Enable dynamic domain name resolution |
dns resolve |
Required Disabled by default. |
|
Specify a DNS server |
dns server ip-address |
Required Not specified by default. |
|
Configure a DNS suffix |
dns domain domain-name |
Optional Not configured by default, that is, only the provided domain name is resolved. |
l You can configure up to six DNS servers.
l You can specify up to ten DNS suffixes.
|
To do… |
Use the command… |
Remarks |
|
Display the static IPv4 domain name resolution table |
display ip host |
Available in any view |
|
Display IPv4 DNS server information |
display dns server [ dynamic ] |
Available in any view |
|
Display DNS suffixes |
display dns domain [ dynamic ] |
Available in any view |
|
Display the information of the dynamic IPv4 domain name cache |
display dns dynamic-host |
Available in any view |
|
Clear the information of the dynamic IPv4 domain name cache |
reset dns dynamic-host |
Available in user view |
As shown in Figure 1-2, static domain name resolution is configured on the device and thus the device can use the domain name host.com to access the host whose IP address is 10.1.1.2.
Figure 1-2 Network diagram for static domain name resolution
# Configure a mapping between host name host.com and IP address 10.1.1.2.
<Sysname> system-view
[Sysname] ip host host.com 10.1.1.2
# Use the ping host.com command to verify that the device can use static domain name resolution to get the IP address 10.1.1.2 corresponding to host.com.
[Sysname] ping host.com
PING host.com (10.1.1.2):
56 data bytes, press CTRL_C to break
Reply from 10.1.1.2: bytes=56 Sequence=1 ttl=128 time=1 ms
Reply from 10.1.1.2: bytes=56 Sequence=2 ttl=128 time=4 ms
Reply from 10.1.1.2: bytes=56 Sequence=3 ttl=128 time=3 ms
Reply from 10.1.1.2: bytes=56 Sequence=4 ttl=128 time=2 ms
Reply from 10.1.1.2: bytes=56 Sequence=5 ttl=128 time=3 ms
--- host.com ping statistics ---
5 packet(s) transmitted
5 packet(s) received
0.00% packet loss
round-trip min/avg/max = 1/2/4 ms
As shown in Figure 1-3, the IP address of the DNS server is 2.1.1.2/16 and the name suffix is com. The mapping between domain name host and IP address 3.1.1.1/16 is stored in the com domain.
Dynamic domain name resolution and the domain name suffix are configured on the device that serves as a DNS client, and thus the device can use domain name host to access the host with the domain name host.com and the IP address 3.1.1.1/16.
Figure 1-3 Network diagram for dynamic domain name resolution
l Before performing the following configuration, make sure that the device and the host are accessible to each another via available routes, and the IP addresses of the interfaces are configured as shown Figure 1-3.
l This configuration may vary with different DNS servers. The following configuration is performed on a Windows server 2000 PC.
1) Configure the DNS server
# Enter the DNS server configuration page.
Select Start > Programs > Administrative Tools > DNS.
# Create zone com.
As shown in Figure 1-4, right click Forward Lookup Zones, select New zone, and then follow the instructions to create a new zone named com.
Figure 1-4 Create a zone
# Create a mapping between host name and IP address.
In Figure 1-5, right click zone com, and then select New Host to bring up a dialog box as shown in Figure 1-6. Enter host name host and IP address 3.1.1.1.
Figure 1-6 Add a mapping between domain name and IP address
2) Configure the DNS client
# Enable dynamic domain name resolution.
<Sysname> system-view
[Sysname] dns resolve
# Specify the DNS server 2.1.1.2.
[Sysname] dns server 2.1.1.2
# Configure com as the name suffix.
[Sysname] dns domain com
3) Configuration verification
# Use the ping host command on the device to verify that the communication between the device and the host is normal and that the corresponding destination IP address is 3.1.1.1.
[Sysname] ping host
Trying DNS resolve, press CTRL_C to break
Trying DNS server (2.1.1.2)
PING host.com (3.1.1.1):
56 data bytes, press CTRL_C to break
Reply from 3.1.1.1: bytes=56 Sequence=1 ttl=126 time=3 ms
Reply from 3.1.1.1: bytes=56 Sequence=2 ttl=126 time=1 ms
Reply from 3.1.1.1: bytes=56 Sequence=3 ttl=126 time=1 ms
Reply from 3.1.1.1: bytes=56 Sequence=4 ttl=126 time=1 ms
Reply from 3.1.1.1: bytes=56 Sequence=5 ttl=126 time=1 ms
--- host.com ping statistics ---
5 packet(s) transmitted
5 packet(s) received
0.00% packet loss
round-trip min/avg/max = 1/1/3 ms
After enabling the dynamic domain name resolution, the user cannot get the correct IP address.
l Use the display dns dynamic-host command to verify that the specified domain name is in the cache.
l If the specified domain name does not exist, check that dynamic domain name resolution is enabled and the DNS client can communicate with the DNS server.
l If the specified domain name is in the cache, but the IP address is incorrect, check that the DNS client has the correct IP address of the DNS server.
l Verify the mapping between the domain name and IP address is correct on the DNS server.
