nslookup reported "can't resolve '(null)': Name does not resolve" though it successfully resolved the DNS names
This is a bug/oddity in nslookup. The "can't resolve" message is actually about the DNS server in use, not the site you are trying to look up.
For example this query (which tells nslookup to lookup google.com using the 8.8.8.8 DNS server) has no error message:
nslookup google.com 8.8.8.8Server: 8.8.8.8Address 1: 8.8.8.8 dns.googleName: google.comAddress 1: 172.217.164.110 sfo03s18-in-f14.1e100.netAddress 2: 2607:f8b0:4005:80b::200e sfo03s18-in-x0e.1e100.netBut this query (in which the DNS server is "null") does show the "error":
UAP-AC-LR1-BZ.v4.0.42# nslookup google.comnslookup: can't resolve '(null)': Name does not resolveName: google.comAddress 1: 172.217.164.110 sfo03s18-in-f14.1e100.netAddress 2: 2607:f8b0:4005:80b::200e sfo03s18-in-x0e.1e100.netAdmittedly this is misleading/confusing, and really should be fixed in nslookup.