Domain Name System (DNS) is a distributed database used by TCP/IP applications to translate domain names into IP addresses. The domain name-to-IP address mapping is called a DNS entry.

DNS services can be static or dynamic. After a user specifies a name, the device checks the 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. To improve efficiency, you can put frequently queried name-to-IP address mappings in the local static name resolution table.

Static domain name resolution

Static domain name resolution means manually creating mappings between domain names and IP addresses. For example, you can create a static DNS mapping for a device so that you can Telnet to the device by using the domain name.

Dynamic domain name resolution

Resolution process

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 the resolver finds a match, 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, the server sends a query to other DNS servers. This process continues until a result, whether successful or not, is returned.

4. After receiving a response from the DNS server, the DNS client returns the resolution result to the user program.

Figure 1 shows the relationship between the user program, DNS client, and DNS server.

The DNS client includes the resolver and cache. The user program and DNS client can run on the same device or different devices. The DNS server and the DNS client usually run on different devices.

Figure 1 Dynamic domain name resolution

Dynamic domain name resolution allows the DNS client to store latest DNS entries in the dynamic domain name cache. The DNS client does not need to send a request to the DNS server for a repeated query within the aging time. To make sure the entries from the DNS server are up to date, a DNS entry is removed when its aging timer expires. The DNS server determines how long a mapping is valid, and the DNS client obtains the aging information from DNS responses.

DNS suffixes

You can configure a domain name suffix list so that the resolver can use the list to supply the missing part of an incomplete name.

For example, you can configure com as the suffix for aabbcc.com. The user only needs to enter aabbcc to obtain the IP address of aabbcc.com. The resolver adds the suffix and delimiter before passing the name to the DNS server.

The name resolver handles the queries based on the domain names that the user enters:

· If the user enters a domain name without a dot (.) (for example, aabbcc), the resolver considers the domain name as a host name. It adds a DNS suffix to the host name before performing the query operation. If no match is found for any host name and suffix combination, the resolver uses the user-entered domain name (for example, aabbcc) for the IP address query.

· If the user enters a domain name with a dot (.) among the letters (for example, www.aabbcc), the resolver directly uses this domain name for the query operation. If the query fails, the resolver adds a DNS suffix for another query operation.

· If the user enters a domain name with a dot (.) at the end (for example, aabbcc.com.), the resolver considers the domain name an FQDN and returns the successful or failed query result. The dot at the end of the domain name is considered a terminating symbol.

The device supports static and dynamic DNS client 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.

DNS proxy

As shown in Figure 2, the DNS proxy performs the following operations:

· Forwards the request from the DNS client to the designated DNS server.

· Conveys the reply from the DNS server to the client.

The DNS proxy simplifies network management. When the DNS server address is changed, you can change the configuration only on the DNS proxy instead of on each DNS client.

Figure 2 DNS proxy application

A DNS proxy operates as follows:

1. A DNS client considers the DNS proxy as the DNS server, and sends a DNS request to the DNS proxy. The destination address of the request is the IP address of the DNS proxy.

2. The DNS proxy searches the local static domain name resolution table and dynamic domain name resolution cache after receiving the request. If the requested information is found, the DNS proxy returns a DNS reply to the client.

3. If the requested information is not found, the DNS proxy sends the request to the designated DNS server for domain name resolution.

4. After receiving a reply from the DNS server, the DNS proxy records the IP address-to-domain name mapping and forwards the reply to the DNS client.

If no DNS server is designated or no route is available to the designated DNS server, the DNS proxy does not forward DNS requests.

DNS spoofing

DNS spoofing is applied to the dial-up network, as shown in Figure 3.

· The device connects to a PSTN/ISDN network through a dial-up interface. The device triggers the establishment of a dial-up connection only when packets are to be forwarded through the dial-up interface.

· The device acts as a DNS proxy and is specified as a DNS server on the hosts. After the dial-up connection is established, the device dynamically obtains the DNS server address through DHCP or another autoconfiguration mechanism.

Figure 3 DNS spoofing application

The DNS proxy does not have the DNS server address or cannot reach the DNS server after startup. A host accesses the HTTP server in the following steps:

1. The host sends a DNS request to the device to resolve the domain name of the HTTP server into an IP address.

2. Upon receiving the request, the device searches the local static and dynamic DNS entries for a match. Because no match is found, the device spoofs the host by replying a configured IP address. The device must have a route to the IP address with the dial-up interface as the output interface.

The IP address configured for DNS spoofing is not the actual IP address of the requested domain name. Therefore, the TTL field is set to 0 in the DNS reply. When the DNS client receives the reply, it creates a DNS entry and ages it out immediately.

3. Upon receiving the reply, the host sends an HTTP request to the replied IP address.

4. When forwarding the HTTP request through the dial-up interface, the device performs the following operations:

¡ Establishes a dial-up connection with the network.

¡ Dynamically obtains the DNS server address through DHCP or another autoconfiguration mechanism.

5. Because the DNS entry ages out immediately upon creation, the host sends another DNS request to the device to resolve the HTTP server domain name.

6. The device operates the same as a DNS proxy. For more information, see "DNS proxy."

7. After obtaining the IP address of the HTTP server, the host can access the HTTP server.

Without DNS spoofing, the device forwards the DNS requests from the host to the DNS server if it cannot find a matching local DNS entry. However, the device cannot obtain the DNS server address, because no dial-up connection is established. Therefore, the device cannot forward or answer the requests from the client. DNS resolution fails, and the client cannot access the HTTP server.

DNS configuration task list

Tasks at a glance
Perform one of the following tasks: · Configuring the IPv4 DNS client · Configuring the IPv6 DNS client
(Optional.) Configuring the DNS proxy
(Optional.) Configuring DNS spoofing
(Optional.) Specifying the source interface for DNS packets
(Optional.) Configuring the DNS trusted interface
(Optional.) Setting the DSCP value for outgoing DNS packets

Configuring the IPv4 DNS client

Configuring static domain name resolution

Static domain name resolution allows applications such as Telnet to contact hosts by using host names instead of IPv4 addresses.

Follow these guidelines when you configure static domain name resolution:

· Each host name maps to only one IPv4 address. The most recent configuration for a host name takes effect.

· You can configure a maximum of 1024 IPv4 DNS entries.

To configure static domain name resolution:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Configure a mapping between a host name and an IPv4 address.	ip host host-name ip-address	By default, no mapping between a host name and an IPv4 address is configured.

Configuring dynamic domain name resolution

To use dynamic domain name resolution, configure DNS servers so that DNS queries can be sent to a correct server for resolution. A DNS server manually configured takes precedence over the one dynamically obtained through DHCP, and a DNS server configured earlier takes precedence. A name query is first sent to the DNS server that has the highest priority. If no reply is received, it is sent to the DNS server that has the second highest priority, and so on.

In addition, you can configure a DNS suffix that the system automatically adds to the provided domain name for resolution. A DNS suffix manually configured takes precedence over the one dynamically obtained through DHCP, and a DNS suffix configured earlier takes precedence. The DNS resolver first uses the suffix that has the highest priority. If the name resolution fails, the DNS resolver uses the suffix that has the second highest priority, and so on.

Configuration guidelines

Follow these guidelines when you configure dynamic domain name resolution:

· You can specify a maximum of six DNS server IPv4 addresses.

· You can specify a maximum of six DNS server IPv6 addresses.

An IPv4 name query is first sent to the DNS server IPv4 addresses. If no reply is received, it is sent to the DNS server IPv6 addresses.

· You can specify a maximum of 16 DNS suffixes.

Configuration procedure

To configure dynamic domain name resolution:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Specify a DNS server.	· Specify a DNS server IPv4 address: dns server ip-address · Specify a DNS server IPv6 address: ipv6 dns server ipv6-address [ interface-type interface-number ]	By default, no DNS server is specified. You can specify both the IPv4 and IPv6 addresses.
3. (Optional.) Configure a DNS suffix.	dns domain domain-name	By default, no DNS suffix is configured and only the provided domain name is resolved.

Configuring the IPv6 DNS client

Configuring static domain name resolution

Static domain name resolution allows applications such as Telnet to contact hosts by using host names instead of IPv6 addresses.

Follow these guidelines when you configure static domain name resolution:

· Each host name maps to only one IPv6 address. The most recent configuration for a host name takes effect.

· You can configure a maximum of 1024 IPv6 DNS entries.

To configure static domain name resolution:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Configure a mapping between a host name and an IPv6 address.	ipv6 host host-name ipv6-address	By default, no mapping between a host name and an IPv6 address is configured.

Configuring dynamic domain name resolution

To send DNS queries to a correct server for resolution, you must enable dynamic domain name resolution and configure DNS servers. A DNS server manually configured takes precedence over the one dynamically obtained through DHCP, and a DNS server configured earlier takes precedence. A name query is first sent to the DNS server that has the highest priority. If no reply is received, it is sent to the DNS server that has the second highest priority, and so on.

Configuration guidelines

Follow these guidelines when you configure dynamic domain name resolution:

· You can specify a maximum of six DNS server IPv4 addresses.

· You can specify a maximum of six DNS server IPv6 addresses.

An IPv6 name query is first sent to the IPv6 DNS servers. If no reply is received, it is sent to the IPv4 DNS servers.

· You can specify a maximum of 16 DNS suffixes.

Configuration procedure

To configure dynamic domain name resolution:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Specify a DNS server.	· Specify a DNS server IPv4 address: dns server ip-address · Specify a DNS server IPv6 address: ipv6 dns server ipv6-address [ interface-type interface-number ]	By default, no DNS server is specified. You can specify both the IPv4 and IPv6 addresses.
3. (Optional.) Configure a DNS suffix.	dns domain domain-name	By default, no DNS suffix is configured. Only the provided domain name is resolved.

Configuring the DNS proxy

You can specify multiple DNS servers. The DNS proxy forwards a request to the DNS server that has the highest priority. If having not received a reply, it forwards the request to a DNS server that has the second highest priority, and so on.

A DNS proxy forwards an IPv4 name query first to IPv4 DNS servers. If no reply is received, it forwards the request to IPv6 DNS servers.

A DNS proxy forwards an IPv6 name query first to IPv6 DNS servers. If no reply is received, it forwards the request to IPv4 DNS servers.

To configure the DNS proxy:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enable DNS proxy.	dns proxy enable	By default, DNS proxy is disabled.
3. Specify a DNS server.	· Specify a DNS server IPv4 address: dns server ip-address · Specify a DNS server IPv6 address: ipv6 dns server ipv6-address [ interface-type interface-number ]	By default, no DNS server is specified. You can specify both the IPv4 and IPv6 DNS addresses.

Configuring DNS spoofing

DNS spoofing is effective only when:

· The DNS proxy is enabled on the device.

· No DNS server or route to any DNS server is specified on the device.

You can configure only one replied IPv4 address and one replied IPv6 address. If you use the command multiple times, the most recent configuration takes effect.

To configure DNS spoofing:

Step	Command	Remarks
4. Enter system view.	system-view	N/A
5. Enable DNS proxy.	dns proxy enable	By default, DNS proxy is disabled.
6. Enable DNS spoofing and specify the IP address used to spoof DNS requests.	· Specify an IPv4 address: dns spoofing ip-address · Specify an IPv6 address: ipv6 dns spoofing ipv6-address	By default, DNS spoofing is disabled. You can specify both an IPv4 address and an IPv6 address.

Specifying the source interface for DNS packets

This task enables the device to always use the primary IP address of the specified source interface as the source IP address of outgoing DNS packets. This feature applies to scenarios in which the DNS server responds only to DNS requests sourced from a specific IP address. If no IP address is configured on the source interface, no DNS packets can be sent out.

When sending an IPv6 DNS request, the device follows the method defined in RFC 3484 to select an IPv6 address of the source interface.

You can configure only one source interface.

To specify the source interface for DNS packets:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Specify the source interface for DNS packets.	dns source-interface interface-type interface-number	By default, no source interface for DNS packets is specified. If you execute the command multiple times, the most recent configuration takes effect.

Step

Command

Remarks

1. Enter system view.

system-view

N/A

2. Specify the source interface for DNS packets.

dns source-interface interface-type interface-number

By default, no source interface for DNS packets is specified.

If you execute the command multiple times, the most recent configuration takes effect.

Configuring the DNS trusted interface

This task enables the device to use only the DNS suffix and domain name server information obtained through the trusted interface. The device can then obtain the correct resolved IP address. This feature protects the device against attackers that act as the DHCP server to assign incorrect DNS suffix and domain name server address.

To configure the DNS trusted interface:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Specify the DNS trusted interface.	dns trust-interface interface-type interface-number	By default, no DNS trusted interface is specified. You can configure up to 128 DNS trusted interfaces.

Step

Command

Remarks

1. Enter system view.

system-view

N/A

2. Specify the DNS trusted interface.

dns trust-interface interface-type interface-number

By default, no DNS trusted interface is specified.

You can configure up to 128 DNS trusted interfaces.

Setting the DSCP value for outgoing DNS packets

The DSCP value of a packet specifies the priority level of the packet and affects the transmission priority of the packet. A bigger DSCP value represents a higher priority.

To set the DSCP value for outgoing DNS packets:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Set the DSCP value for outgoing DNS packets.	· DSCP value for IPv4 DNS packets: dns dscp dscp-value · DSCP value for IPv6 DNS packets: ipv6 dns dscp dscp-value	By default, the DSCP value for outgoing DNS packets is 0. The configuration is available on DNS clients and DNS proxy devices.

Step

Command

Remarks

1. Enter system view.

system-view

N/A

2. Set the DSCP value for outgoing DNS packets.

· DSCP value for IPv4 DNS packets:
dns dscp dscp-value

· DSCP value for IPv6 DNS packets:
ipv6 dns dscp dscp-value

By default, the DSCP value for outgoing DNS packets is 0.

The configuration is available on DNS clients and DNS proxy devices.

Displaying and maintaining DNS

Execute display commands in any view and reset commands in user view.

Task	Command
Display the domain name resolution table.	display dns host [ ip \| ipv6 ]
Display IPv4 DNS server information.	display dns server [ dynamic ]
Display IPv6 DNS server information.	display ipv6 dns server [ dynamic ]
Display DNS suffixes.	display dns domain [ dynamic ]
Clear information about the dynamic domain name cache.	reset dns host [ ip \| ipv6 ]

IPv4 DNS configuration examples

Static domain name resolution configuration example

Network requirements

As shown in Figure 4, the host at 10.1.1.2 has the domain name host.com. Configure static IPv4 DNS on the AC so that the client can use the easy-to-remember domain name rather than the IP address to access the host.

Figure 4 Network diagram

Configuration procedure

# Configure WLAN access on the AC. For more information about WLAN access configuration, see WLAN Configuration Guide. (Details not shown.)

# Configure a mapping between the host name host.com and the IP address 10.1.1.2.

<AC> system-view

[AC] ip host host.com 10.1.1.2

# Verify that the AC can use static domain name resolution to resolve the domain name host.com into the IP address 10.1.1.2.

[AC] ping host.com

Ping host.com (10.1.1.2): 56 data bytes, press CTRL_C to break

56 bytes from 10.1.1.2: icmp_seq=0 ttl=255 time=1.000 ms

56 bytes from 10.1.1.2: icmp_seq=1 ttl=255 time=1.000 ms

56 bytes from 10.1.1.2: icmp_seq=2 ttl=255 time=1.000 ms

56 bytes from 10.1.1.2: icmp_seq=3 ttl=255 time=1.000 ms

56 bytes from 10.1.1.2: icmp_seq=4 ttl=255 time=2.000 ms

--- Ping statistics for host.com ---

5 packet(s) transmitted, 5 packet(s) received, 0.0% packet loss

round-trip min/avg/max/std-dev = 1.000/1.200/2.000/0.400 ms

Dynamic domain name resolution configuration example

Network requirements

As shown in Figure 5, configure the DNS server to store the mapping between the host's domain name host and IPv4 address 3.1.1.1/16 in the com domain. Configure dynamic IPv4 DNS and the DNS suffix com on the AC so that the client can use the domain name host to access the host.

Figure 5 Network diagram

Configuration procedure

Before performing the following configuration, make sure the following requirements are met:

· The AC and the host can reach each other.

· The IP addresses of the interfaces are configured as shown in Figure 5.

1. Configure WLAN access on the AC. For more information about WLAN access configuration, see WLAN Configuration Guide. (Details not shown.)

2. Configure the DNS server:

The configuration might vary by DNS server. The following configuration is performed on a PC running Windows Server 2008 R2.

a. Select Start > Programs > Administrative Tools > DNS.

The DNS server configuration page appears, as shown in Figure 6.

b. Right-click Forward Lookup Zones, select New Zone, and then follow the wizard to create a new zone named com.

Figure 6 Creating a zone

c. On the DNS server configuration page, right-click zone com and select New Host.

Figure 7 Adding a host

d. On the page that appears, enter the host name host and the IP address 3.1.1.1.

e. Click Add Host.

The mapping between the IP address and host name is created.

Figure 8 Adding a mapping between domain name and IP address

3. Configure the DNS client:

# Specify the DNS server 2.1.1.2.

<AC> system-view

[AC] dns server 2.1.1.2

# Specify com as the name suffix.

[AC] dns domain com

Verifying the configuration

# Verify that the AC can use the dynamic domain name resolution to resolve the domain name host.com into the IP address 3.1.1.1.

[AC] ping host

Ping host.com (3.1.1.1): 56 data bytes, press CTRL_C to break

56 bytes from 3.1.1.1: icmp_seq=0 ttl=255 time=1.000 ms

56 bytes from 3.1.1.1: icmp_seq=1 ttl=255 time=1.000 ms

56 bytes from 3.1.1.1: icmp_seq=2 ttl=255 time=1.000 ms

56 bytes from 3.1.1.1: icmp_seq=3 ttl=255 time=1.000 ms

56 bytes from 3.1.1.1: icmp_seq=4 ttl=255 time=2.000 ms

--- Ping statistics for host ---

5 packet(s) transmitted, 5 packet(s) received, 0.0% packet loss

round-trip min/avg/max/std-dev = 1.000/1.200/2.000/0.400 ms

DNS proxy configuration example

Network requirements

As shown in Figure 9, configure the AC as the DNS proxy to forward DNS packets between DNS clients and the DNS server at 4.1.1.1.

Figure 9 Network diagram

Configuration procedure

Before performing the following configuration, make sure the following requirements are met:

· The AC, the DNS server, and the host can reach one another.

· The IP addresses of the interfaces are configured as shown in Figure 9.

1. Configure WLAN access on the AC. For more information about WLAN access configuration, see WLAN Configuration Guide. (Details not shown.)

2. Configure the DNS server:

The configuration might vary by DNS server. When a PC running Windows Server 2008 R2 acts as the DNS server, see "Dynamic domain name resolution configuration example" for configuration information.

3. Configure the DNS proxy:

# Specify the DNS server 4.1.1.1.

<AC> system-view

[AC] dns server 4.1.1.1

# Enable DNS proxy.

[AC] dns proxy enable

4. Configure DNS clients and specify the DNS server 2.1.1.2 for the clients. (Details not shown.)

Verifying the configuration

# Verify that DNS proxy on the AC functions.

C:\Users\ss> ping host.com

Ping host.com (3.1.1.1): 56 data bytes, press CTRL_C to break

56 bytes from 3.1.1.1: icmp_seq=0 ttl=255 time=1.000 ms

56 bytes from 3.1.1.1: icmp_seq=1 ttl=255 time=1.000 ms

56 bytes from 3.1.1.1: icmp_seq=2 ttl=255 time=1.000 ms

56 bytes from 3.1.1.1: icmp_seq=3 ttl=255 time=1.000 ms

56 bytes from 3.1.1.1: icmp_seq=4 ttl=255 time=2.000 ms

--- Ping statistics for host.com ---

5 packet(s) transmitted, 5 packet(s) received, 0.0% packet loss

round-trip min/avg/max/std-dev = 1.000/1.200/2.000/0.400 ms

IPv6 DNS configuration examples

Static domain name resolution configuration example

Network requirements

As shown in Figure 10, the host at 1::2 has the domain name host.com. Configure static IPv6 DNS on the AC so that the client can use the easy-to-remember domain name rather than the IPv6 address to access the host.

Figure 10 Network diagram

Configuration procedure

# Configure WLAN access on the AC. For more information about WLAN access configuration, see WLAN Configuration Guide. (Details not shown.)

# Configure a mapping between the host name host.com and the IPv6 address 1::2.

<AC> system-view

[AC] ipv6 host host.com 1::2

# Verify that the AC can use static domain name resolution to resolve the domain name host.com into the IPv6 address 1::2.

[AC] ping ipv6 host.com

Ping6(56 data bytes) 1::1 --> 1::2, press CTRL_C to break

56 bytes from 1::2, icmp_seq=0 hlim=128 time=1.000 ms

56 bytes from 1::2, icmp_seq=1 hlim=128 time=0.000 ms

56 bytes from 1::2, icmp_seq=2 hlim=128 time=1.000 ms

56 bytes from 1::2, icmp_seq=3 hlim=128 time=1.000 ms

56 bytes from 1::2, icmp_seq=4 hlim=128 time=0.000 ms

--- Ping6 statistics for host.com ---

5 packet(s) transmitted, 5 packet(s) received, 0.0% packet loss

round-trip min/avg/max/std-dev = 0.000/0.600/1.000/0.490 ms

Dynamic domain name resolution configuration example

Network requirements

As shown in Figure 11, configure the DNS server to store the mapping between the host's domain name host and IPv6 address 1::1/64 in the com domain. Configure dynamic IPv6 DNS and the DNS suffix com on the AC so that the client can use the domain name host to access the host.

Figure 11 Network diagram

Configuration procedure

Before performing the following configuration, make sure the following requirements are met:

· The AC and the host can reach each other.

· The IPv6 addresses of the interfaces are configured as shown in Figure 11.

1. Configure WLAN access on the AC. For more information about WLAN access configuration, see WLAN Configuration Guide. (Details not shown.)

2. Configure the DNS server:

The configuration might vary by DNS server. The following configuration is performed on a PC running Windows Server 2008 R2. Make sure the DNS server supports IPv6 DNS so that the server can process IPv6 DNS packets and its interfaces can forward IPv6 packets.

a. Select Start > Programs > Administrative Tools > DNS.

The DNS server configuration page appears, as shown in Figure 12.

b. Right-click Forward Lookup Zones, select New Zone, and then follow the wizard to create a new zone named com.

Figure 12 Creating a zone

c. On the DNS server configuration page, right-click zone com and select New Host.

Figure 13 Adding a host

d. On the page that appears, enter the host name host and the IPv6 address 1::1.

e. Click Add Host.

The mapping between the IPv6 address and host name is created.

Figure 14 Adding a mapping between domain name and IPv6 address

3. Configure the DNS client:

# Specify the DNS server 2::2.

<AC> system-view

[AC] ipv6 dns server 2::2

# Configure com as the DNS suffix.

[AC] dns domain com

Verifying the configuration

# Verify that the AC can use the dynamic domain name resolution to resolve the domain name host.com into the IP address 1::1.

[AC] ping ipv6 host

Ping6(56 data bytes) 3::1 --> 1::1, press CTRL_C to break

56 bytes from 1::1, icmp_seq=0 hlim=128 time=1.000 ms

56 bytes from 1::1, icmp_seq=1 hlim=128 time=0.000 ms

56 bytes from 1::1, icmp_seq=2 hlim=128 time=1.000 ms

56 bytes from 1::1, icmp_seq=3 hlim=128 time=1.000 ms

56 bytes from 1::1, icmp_seq=4 hlim=128 time=0.000 ms

--- Ping6 statistics for host ---

5 packet(s) transmitted, 5 packet(s) received, 0.0% packet loss

round-trip min/avg/max/std-dev = 0.000/0.600/1.000/0.490 ms

DNS proxy configuration example

Network requirements

As shown in Figure 15, configure the AC as the DNS proxy to forward DNS packets between DNS clients and the DNS server at 4000::1.

Figure 15 Network diagram

Configuration procedure

Before performing the following configuration, make sure the following requirements are met:

· The AC, the DNS server, and the host can reach to one another.

· The IPv6 addresses of the interfaces are configured as shown in Figure 15.

1. Configure WLAN access on the AC. For more information about WLAN access configuration, see WLAN Configuration Guide. (Details not shown.)

2. Configure the DNS server:

This configuration might vary by DNS server. When a PC running Windows Server 2008 R2 acts as the DNS server, see "Dynamic domain name resolution configuration example" for configuration information.

3. Configure the DNS proxy:

# Specify the DNS server 4000::1.

<AC> system-view

[AC] ipv6 dns server 4000::1

# Enable DNS proxy.

[AC] dns proxy enable

4. Configure DNS clients and specify the DNS server 2000::2 for the clients. (Details not shown.)

Verifying the configuration

# Verify that DNS proxy on the AC functions.

C:\Users\ss> ping host.com

Ping6(56 data bytes) 2000::1 --> 3000::1, press CTRL_C to break

56 bytes from 3000::1, icmp_seq=0 hlim=128 time=1.000 ms

56 bytes from 3000::1, icmp_seq=1 hlim=128 time=0.000 ms

56 bytes from 3000::1, icmp_seq=2 hlim=128 time=1.000 ms

56 bytes from 3000::1, icmp_seq=3 hlim=128 time=1.000 ms

56 bytes from 3000::1, icmp_seq=4 hlim=128 time=0.000 ms

--- Ping6 statistics for host.com ---

5 packet(s) transmitted, 5 packet(s) received, 0.0% packet loss

round-trip min/avg/max/std-dev = 0.000/0.600/1.000/0.490 ms

Troubleshooting IPv4 DNS configuration

Failure to resolve IPv4 addresses

Symptom

After enabling dynamic domain name resolution, the user cannot get the correct IP address.

Solution

To resolve the problem:

1. Use the display dns host ip command to verify that the specified domain name is in the cache.

2. If the specified domain name does not exist, check that the DNS client can communicate with the DNS server.

3. 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.

4. Verify that the mapping between the domain name and IP address is correct on the DNS server .

Troubleshooting IPv6 DNS configuration

Failure to resolve IPv6 addresses

Symptom

After enabling dynamic domain name resolution, the user cannot get the correct IPv6 address.

Solution

To resolve the problem:

1. Use the display dns host ipv6 command to verify that the specified domain name is in the cache.

2. If the specified domain name does not exist, check that dynamic domain name resolution is enabled, and that the DNS client can communicate with the DNS server.

3. If the specified domain name is in the cache, but the IPv6 address is incorrect, check that the DNS client has the correct IPv6 address of the DNS server.

4. Verify that the mapping between the domain name and IPv6 address is correct on the DNS server.

Configuring DDNS

Overview

DNS provides only the static mappings between domain names and IP addresses. When the IP address of a node changes, your access to the node fails.

Dynamic Domain Name System (DDNS) can dynamically update the mappings between domain names and IP addresses for DNS servers.

DDNS is supported only by IPv4 DNS, and it is used to update the mappings between domain names and IPv4 addresses.

DDNS application

As shown in Figure 16, DDNS works on the client-server model.

· DDNS client—A device that needs to update the mapping between its domain name and IP address dynamically on the DNS server when its IP address changes. An Internet user typically accesses an application layer server such as an HTTP server or an FTP server by using the server's domain name. When its IP address changes, the application layer server runs as a DDNS client. It sends a request to the DDNS server for updating the mapping between its domain name and its IP address.

· DDNS server—Informs the DNS server of latest mappings. When receiving the mapping update request from a DDNS client, the DDNS server tells the DNS server to re-map the domain name and the IP address of the DDNS client. Therefore, the Internet users can use the same domain name to access the DDNS client even if the IP address of the DDNS client has changed.

Figure 16 DDNS application

With the DDNS client configured, a device can dynamically update the latest mapping between its domain name and IP address on the DNS server through DDNS servers.

NOTE:

The DDNS update process does not have a unified standard but varies by DDNS server that the DDNS client contacts.

Feature and hardware compatibility

Hardware series	Model	DDNS compatibility
WX1800H series	WX1804H WX1810H WX1820H	Yes
WX2500H series	WX2510H WX2540H WX2560H	Yes
WX3000H series	WX3010H WX3010H-L WX3010H-X WX3024H WX3024H-L	Yes
WX3500H series	WX3508H WX3510H WX3520H WX3540H	No
WX5500E series	WX5510E WX5540E	No
WX5500H series	WX5540H WX5560H WX5580H	No
Access controller modules	EWPXM1MAC0F EWPXM1WCME0 EWPXM2WCMD0F LSQM1WCMX20 LSQM1WCMX40 LSUM1WCME0 LSUM1WCMX20RT LSUM1WCMX40RT	No

DDNS client configuration task list

Tasks at a glance
(Required.) Configuring a DDNS policy
(Required.) Applying the DDNS policy to an interface
(Optional.) Setting the DSCP value for outgoing DDNS packets

Configuring a DDNS policy

A DDNS policy contains the DDNS server address, port number, login ID, password, time interval, associated SSL client policy, and update time interval. After creating a DDNS policy, you can apply it to multiple interfaces to simplify DDNS configuration.

The URL addresses configured for update requests vary by DDNS server.

Table 1 Common URL addresses

DDNS server	URL addresses for DDNS update requests
www.3322.org	http://members.3322.org/dyndns/update?system=dyndns&hostname=<h>&myip=<a>
DYNDNS	http://members.dyndns.org/nic/update?system=dyndns&hostname=<h>&myip=<a>
DYNS	http://www.dyns.cx/postscript.php?host=<h>&ip=<a>
ZONEEDIT	http://dynamic.zoneedit.com/auth/dynamic.html?host=<h>&dnsto=<a>
TZO	http://cgi.tzo.com/webclient/signedon.html?TZOName=<h>IPAddress=<a>
EASYDNS	http://members.easydns.com/dyn/ez-ipupdate.php?action=edit&myip=<a>&host_id=<h>
HEIPV6TB	http://dyn.dns.he.net/nic/update?hostname=<h>&myip=<a>
CHANGE-IP	http://nic.changeip.com/nic/update?hostname=<h>&offline=1
NO-IP	http://dynupdate.no-ip.com/nic/update?hostname=<h>&myip=<a>
DHS	http://members.dhs.org/nic/hosts?domain=dyn.dhs.org&hostname=<h>&hostscmd=edit&hostscmdstage=2&type=1&ip=<a>
HP	https://server-name/nic/update?group=group-name&myip=<a>
ODS	ods://update.ods.org
GNUDIP	gnudip://server-name
PeanutHull	oray://phservice2.oray.net

By default, the URL address does not include a username or password. To configure the username and password, use the username command and the password command.

HP and GNUDIP are common DDNS update protocols. The server-name parameter is the domain name or IP address of the service provider's server using one of the update protocols.

The URL address for an update request can start with:

· http://—The HTTP-based DDNS server.

· https://—The HTTPS-based DDNS server.

· ods://—The TCP-based ODS server.

· gnudip://—The TCP-based GNUDIP server.

· oray://—The TCP-based DDNS server.

The domain names of DDNS servers are members.3322.org and phservice2.oray.net. The domain names of PeanutHull DDNS servers can be phservice2.oray.net, phddns60.oray.net, client.oray.net, ph031.oray.net, and so on. Determine the domain name in the URL according to the actual situation.

The port number in the URL address is optional. If no port is specified, the system uses the default port numbers: port 80 for HTTP, port 443 for HTTPS, and port 6060 for PeanutHull DDNS server.

The system automatically performs the following tasks:

· Fills <h> with the FQDN upon a DDNS policy application to the interface.

· Fills <a> with the primary IP address of the interface to which the DDNS policy is applied.

You can also manually specify an FQDN and an IP address in <h> and <a>. In this case, the FQDN specified upon the DDNS policy application does not take effect. You are not encouraged to manually change the <h> and <a> because your configuration might be incorrect. For more information about applying DDNS policies, see "Applying the DDNS policy to an interface."

No FQDN or IP address can be specified in the URL address for update requests sent to the PeanutHull DDNS server. You can specify the FQDN when applying the DDNS policy to an interface. The IP address is the primary IP address of the interface to which the DDNS policy is applied.

TIP:

The FQDN is the only identification of a node in the network. An FQDN consists of a local host name and a parent domain name and can be translated into an IP address.

Configuration prerequisites

Visit the website of a DDNS service provider, register an account, and apply for a domain name for the DDNS client. When the DDNS client updates the mapping between the domain name and the IP address through the DDNS server, the DDNS server checks the following:

· Whether the account information is correct.

· Whether the domain name to be updated belongs to the account.

Configuration procedure

To configure a DDNS policy:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Create a DDNS policy and enter its view.	ddns policy policy-name	By default, no DDNS policy is created.
3. Specify a URL address for DDNS update requests.	url request-url	By default, no URL address is specified for DDNS update requests.
4. Specify the username for logging in to the DDNS server.	username username	By default, no username is specified.
5. Specify the password for logging in to the DDNS server.	password { cipher \| simple } password	By default, no password is specified.
6. (Optional.) Specify the parameter transmission method for sending DDNS update requests to HTTP/HTTPS-based DDNS servers.	method { http-get \| http-post }	By default, http-get is used. Use the method http-post command to specify the POST method for DDNS update with a DHS server.
7. (Optional.) Associate an SSL client policy with the DDNS policy.	ssl-client-policy policy-name	By default, no SSL client policy is associated with the DDNS policy. This step is only effective and a must for HTTP-based DDNS update requests. For SSL client policy configuration, see Security Configuration Guide.
8. (Optional.) Specify the interval for sending update requests.	interval days [ hours [ minutes ] ]	By default, the time interval is one hour.

Applying the DDNS policy to an interface

After you apply the DDNS policy to an interface and specify the FQDN for update, the DDNS client sends requests to the DDNS server to update the mapping between the domain name and the primary IP address of the interface at the specified interval.

Before you apply a DDNS policy to an interface, complete the following tasks:

· Specify the primary IP address of the interface and make sure the DDNS server and the interface can reach each other.

· Configure static or dynamic domain name resolution to translate the domain name of the DDNS server into the IPv4 address. For more information, see "Configuring the IPv4 DNS client."

To apply the DDNS policy to an interface:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter interface view.	interface interface-type interface-number	N/A
3. Apply the DDNS policy to the interface to update the mapping between the specified FQDN and the primary IP address of the interface, and enable DDNS update.	ddns apply policy policy-name [ fqdn domain-name ]	By default, no DDNS policy is applied to the interface, no FQDN is specified for update, and DDNS update is disabled. The fqdn domain-name option must be specified for all DDNS servers except the PeanutHull DDNS server.

NOTE:

If no FQDN is specified for the PeanutHull DDNS server, the DDNS server updates all domain names of the DDNS client account. If an FQDN is specified, the DDNS server updates only the mapping between the specified FQDN and the primary IP address.

Setting the DSCP value for outgoing DDNS packets

The DSCP value of a packet specifies the priority level of the packet and affects the transmission priority of the packet. A bigger DSCP value represents a higher priority.

To set the DSCP value for outgoing DDNS packets:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Set the DSCP value for outgoing DDNS packets.	ddns dscp dscp-value	By default, the DSCP value for outgoing DDNS packets is 0.

Displaying DDNS

Execute display commands in any view.

Task	Command
Display information about the DDNS policy.	display ddns policy [ policy-name ]

06-Layer 3 - IP Services

Overview

Static domain name resolution

Dynamic domain name resolution

Resolution process

DNS suffixes

DNS proxy

Configuring dynamic domain name resolution

Configuration guidelines

Configuration procedure

Configuring the IPv6 DNS client

Configuration guidelines

Configuration procedure

Specifying the source interface for DNS packets

IPv4 DNS configuration examples

Network requirements

Configuration procedure

Network requirements

Configuration procedure

Verifying the configuration

Network requirements

Configuration procedure

Verifying the configuration

Network requirements

Configuration procedure

Dynamic domain name resolution configuration example

Network requirements

Configuration procedure

Verifying the configuration

Network requirements

Configuration procedure

Verifying the configuration

Symptom

Solution

Symptom

Solution

DDNS client configuration task list

Displaying DDNS

Intelligent Terminal Products

Product Support Services

Technical Service Solutions

Resource Center

Policy

Online Help

Become a Partner

Partner Policy & Program

Global Learning

Partner Sales Resources

Service Business

News & Events

Contact Us