Ah, I think it’s slightly more complicated. In this case it’s a “special target” which doesn’t itself do anything. So when named starts up it causes the “nss-lookup” target to be triggered.
Hmm, personally I think this might be a misconfig; why would an authoritative server that’s not listed in resolv.conf (or elsewhere) cause this target to be triggered. I could see it for a device that uses itself (and systemd-resolved), but not in this case. Fortunately I think it’s harmless (it might impact rpc.statd startup).