3com S7906E Manuel De Montage

 

2-8 

You can specify a domain name suffix in each DHCP address pool on the DHCP server to provide the 

clients with the domain name suffix. With this suffix assigned, the client only needs to input part of a 

domain name, and the system will add the domain name suffix for name resolution. For details about 

DNS, refer to DNS Configuration in the IP Services Volume. 

Follow these steps to configure a domain name suffix in the DHCP address pool: 

Enter system view 

— 

Enter DHCP address pool view 

dhcp server ip-pool pool-name 
[ extended ] 

— 

Specify a domain name suffix  

domain-name domain-name 

Required 

Not specified by default.

 

When a DHCP client wants to access a host on the Internet via the host name, it contacts a Domain 

Name System (DNS) server holding host name-to-IP address mappings to get the host IP address. You 

can specify up to eight DNS servers in the DHCP address pool. 

Follow these steps to configure DNS servers in the DHCP address pool: 

Enter system view 

— 

Enter DHCP address pool view 

dhcp server ip-pool 
pool-name [ extended ] 

— 

Specify DNS servers 

dns-list ip-address&<1-8> 

Required 

Not specified by default. 

 

A Microsoft DHCP client using NetBIOS protocol contacts a Windows Internet Naming Service (WINS) 

server for name resolution. Therefore, the DHCP server should assign a WINS server address when 

assigning an IP address to the client. 

You can specify up to eight WINS servers in a DHCP address pool. 

You need to specify in a DHCP address pool a NetBIOS node type for the client to approach name 

resolution. There are four NetBIOS node types: 

z 

b (broadcast)-node: The b-node client sends the destination name in a broadcast message. The 

destination returns its IP address to the client after receiving the message. 

z 

p (peer-to-peer)-node: The p-node client sends the destination name in a unicast message to the 

WINS server, and the WINS server returns the destination IP address. 

z 

m (mixed)-node: A combination of broadcast first and peer-to-peer second. The m-node client 

broadcasts the destination name, if no response is received, then unicasts the destination name to 

the WINS server to get the destination IP address.