How to resolve the issue where some second-level/third-level domain name resolutions do not take effect in wildcard resolution

```html

Wildcard resolution is also called “wildcard domain resolution”. It means using the wildcard * (asterisk) as a subdomain to make all subdomains point to the same IP address (alias CNAME).

　　For example, if your domain is west.cn:

    Create an A record for the subdomain *.west.cn pointing to 111.111.111.111/alias.

    Then after it takes effect, no matter whether a visitor enters “123.west.cn” or “wds.123.west.cn”, or even “!@#.$%$.12345.ww.a.west.cn”

    Any such characters can point to the IP address 111.111.111.111/alias.

      

Setting up DNS records is not limited to wildcard resolution; in the actual process of using a domain, other second-level domain records or verification records may also be added.

For example, the txt/cname, etc. of _acme-challenge.wewe/dnsauth.www are used to apply for an SSL certificate for wewe/www.

After adding the above records, it was found that the resolution corresponding to wewe/www in the wildcard resolution should itself, according to the wildcard resolution, point to 111.111.111.111/alias, but now all of them have become invalid.

The reason for this problem is that wildcard resolution has the lowest priority in DNS resolution. The solution is also the simplest: just add a separate record for wewe/www that points to the same target as the wildcard resolution. As shown below.

If your separate third-level domain resolution does not take effect, please add a separate third-level domain record. For example, if the 123.wewe record is not the same as the wildcard resolution, just add a 123.wewe record pointing to the same target as the wildcard resolution.

```