Is it expected behavior for Linux to NOT do subsequent DNS requests to resolve to an IP?

My machine is **Debian 12**. Here is the result of nslookup lhtadmin@deb12-docker1:~$ nslookup nc.domain.com Server:172.16.100.4 Address:172.16.100.4#53 nc.domain.com canonical name = lb2.local.domain.com. lb2.local.domain.com canonical name = deb12-docker2.local.domain.com. When I tried to do curl nc.domain.com, I got the message "could not resolve". Here is the log from my DNS server (Pihole). Also, My Pihole is setup to forward zone .local.domain.com to 192.168.1.1 Oct 16 14:08:25: query[A] nc.domain.com from 172.16.100.20 Oct 16 14:08:25: config nc.domain.com is Oct 16 14:08:25: config lb2.local.domain.com is However, if I try the same curl command on a **macOS**, it will do another lookup for deb12-docker2.local.domain.com to resolve to an IP Oct 16 14:03:33: query[A] nc.domain.com from 172.16.110.251 Oct 16 14:03:33: config nc.domain.com is Oct 16 14:03:33: config lb2.local.domain.com is Oct 16 14:03:33: query[A] deb12-docker2.local.domain.com from 172.16.110.251 Oct 16 14:03:33: forwarded deb12-docker2.local.domain.com to 192.168.1.1 Oct 16 14:03:33: reply deb12-docker2.local.domain.com is 172.16.100.128 If I set my Pihole to have A record of deb12-docker2.local.domain.com (not forwarded), it will work. Is there a way to tell Linux to do another lookup for CNAME record that will need to be forwarded?