- The cause of this issue is that the DNS does not allow the resolution addresses including ANY type. We can adjust the DNS resolution policy to resolve this issue.
- For BIND (Berkeley Internet Name Domain) servers, you need to enable ANY type of record in the configuration file (usually named.conf). This usually involves adding an allow-query directive to the options section to allow queries on records of ANY type.
- In your zone file (such as db.example.com), you can add ANY type records for each subdomain. This is usually a * symbol followed by a space, followed by the record value. For example:
*.cdn.npmmirror.com. IN ANY A 192.0.2.1
*.cdn.npmmirror.com. IN ANY MX 10 mail.cdn.npmmirror.com.
*.cdn.npmmirror.com. IN ANY TXT "example text"
- Alternatively, we can edit the /etc/resolv.conf file in the system and annotate the DNS nameserver, then configure the domain name for the request address to be resolved in the /etc/hosts file.
- Edit the /etc/resolv.conf file to comment on the nameserver
- Use the dig tool to query the IP addresses of source registry domain names and cdn domain names and add It in the /etc/hosts file.
# Run the dig command to test
dig cdn.npmmirror.com
# the result:
; <<>> DiG 9.11.4-P2-RedHat-9.11.4-26.P2.el7_9.15 <<>> cdn.npmmirror.com
......
;; ANSWER SECTION:
cdn.npmmirror.com. 55 IN CNAME cdn.npmmirror.com.w.cdngslb.com.
cdn.npmmirror.com.w.cdngslb.com. 55 IN A 111.32.208.176
cdn.npmmirror.com.w.cdngslb.com. 55 IN A 111.32.208.178
......
# add the ip addr to the /etc/hosts
111.32.208.176 cdn.npmmirror.com