Specified domain name using specified DNS resolution problem
Summary
I want to realize that the specified domain name uses the specified DNS resolution, and other domain names that do not match the domain name use another DNS resolution; but when the specified domain name has other aliases and this alias is not written into my specific domain name rules, it will use Another domain name for resolution
BIND version used
BIND 9.11.4
Steps to reproduce
Configuration example: forwarders{ 114.114.114.114; }; }; zone "pinterest.com" { type forward; forwarders { 8.8.8.8; }; };
Configure this configuration in named.conf,When I parsed the domain name with the suffix of pinterest.com, it used 8.8.8.8 to resolve it, and found that it has many aliases through dig www.pinterest.com, such as e6449.a.akamaiedge.net is one of its aliases, and then e6449 The domain name .a.akamaiedge.net is not in our specified domain name rules, then bind will use 114.114.114.114 to resolve it, and then return the resolved address of 114.114.114.114 to my requesting host
What is the current bug behavior?
When I requested to resolve the www.pinterest.com domain name, bind should use 8.8.8.8 to resolve and return the resolved address to me, but it did not, because www.pinterest.com has an alias, and the alias does not match pinterest. com domain name matching rules, this is that bind will use the 114.114.114.114 I set to resolve this address, and return the resolved address to me, but this is not what I want
What is the expected correct behavior?
(What you should see instead.)
Relevant configuration files
Some key configurations are as follows:
forwarders{
114.114.114.114;
};
}; zone "pinterest.com" { type forward; forwarders { 8.8.8.8; }; };
Relevant logs and/or screenshots
(Paste any relevant logs - please use code blocks (```) to format console output, logs, and code, as it's very hard to read otherwise.)
Possible fixes
(If you can, link to the line of code that might be responsible for the problem.)