The PC connected to the DHCP server cannot obtain DNS information when the AR1220 serves as the PPPoE client


The AR used as the DHCP server cannot assign information about the DNS server obtained from the PPPoE server to DHCP clients.
1. Run the ppp ipcp dns admit-any command on the dialer interface to configure the AR to receive the IP address of the DNS server specified by the remote device. If the command is not configured, the AR cannot obtain DNS information.
2. DNS proxy is used to meet customers' requirements. Run the following commands in the system view:
dns resolve
dns proxy enable
In the IP pool view, dns-list is configured as the address of the AR.
In this way, the AR is equivalent to the DNS server for a PC. After receiving a DNS request, the AR sends it to the DNS server to complete domain name resolution.

Other related questions:
DHCP clients cannot obtain IP addresses. How do I solve this problem
Ensure that the DHCP configuration is correct, and reduce the IP address lease. If a long IP address lease is set, after all addresses in the address pool are allocated, addresses that are not required cannot be released immediately. As a result, other DHCP clients cannot obtain IP addresses.

The DHCP client cannot obtain DNS information on the AR
DPossible causes are as follows: 1. The route from the AR to the DHCP server is unreachable. 2. The DNS and DHCP configuration modes are different. When the DHCP server assigns an IP address and gateway address to a client, the DHCP server also sends the DNS server address to the client. Ensure that the DNS server address and DHCP server address are configured in the global address pool or on an interface so that the DHCP server can find the DNS server IP address and deliver it.

ARs configured with IPSec on two private networks cannot communicate with each other
The possible causes are as follows: 1. The public addresses of two IPSec-enabled ARs cannot be pinged. 2. There is an error in the data flow to be encapsulated with the IPSec header or both IPSec and NAT are performed for the same data flow. You can run the display acl all command to check ACL matching. If both IPSec and NAT are performed for the same data flow, use either of the following method to prevent data flow overlapping: -Ensure that the destination IP address denied in the ACL rule referenced by NAT is the destination IP address in the ACL rule referenced by IPSec. By doing so, the device does not perform NAT on the data flow protected by IPSec. -The ACL rule referenced by IPSec matches the NAT-translated IP address. 3. The AR incorrectly learns private routes. The outbound interface of the route to the destination private network is not the public network interface enabled with IPSec.

If you have more questions, you can seek help from following ways:
To iKnow To Live Chat
Scroll to top