Table of contents
1. Description of the matter
I recently set up Ipv6 domain name resolution for my unit (see the previous article for details: ipv4 to ipv6 Shanshi Firewall Command (Education Network)_90 Wall Mount_Forwarder-CSDN Blog ), but when the website discovered the domain name through routing settings, it still didn't work. IPV6 access is achieved through the setting of WWW's AAAA domain name.
2. Problem analysis
After completing the relevant routing configuration, then set the website domain name. In order to allow all domain names to have IPV6 access, I specially set AAAA to * (all organization domain names are valid IPV6 addresses) as shown below:
However, the result was exactly the opposite. I suddenly found that the website prompted the following error interface:
Therefore, I have always suspected that it is an issue with nginx settings. After consulting various sources and documents, I found that all website domain names in WORDPRESS are under the main domain name, while secondary websites or web pages are all subordinate directories:
For example: www.baidu.com is the primary domain name, and when the secondary website or webpage is www.baidu.com/news/20211201/index.html
3. Solution
To sum up, you only need to set the www.baidu.com domain name to the IPV6 address and access it normally (provided that your computer must have an IPV6 address), and finally set the AAAA domain name of www. and point it to the IPV6 address.
