In this case the DNS server is my master website. So let's take three example sites that I'm working with. These are all valid domain names so you can test them.
www.myathleticresume.com is the master website with MultiSites installed. I've set this site up as a name server with my registrar (ns1.myathleticresume.com, ns2.myathleticresume.com) rather than using my host's default nameserver, in the hope that I would be able to avoid setting up domain aliases for each multisites site. The name servers for this site are set to itself (ns1.myathleticresume.com, ns2.myathleticresume.com), and work properly. nslookup on this domain returns the correct IP.
slave1.myathleticresume.com is a multisites client site. Since it's a subdomain of the master site, I would expect it to work without a problem, but nslookup returns "server can't find.... :REFUSED"
www.myacademicresume.com is another multisites client site. It's name servers (at GoDaddy) are set to the master: ns1.myathleticresume.com, ns2.myathleticresume.com. The nslookup on this site returns the same error as the subdomain above.
www.juangamboa.com is another site on the same server, but it's a separate install, not a multisites client. It's name servers are set to ns1.myathleticresume.com and ns2.myathleticresume.com. nslookup returns the correct IP and the site works properly.
So why don't the multisites clients work? I could understand if the external domain (myacademicresume.com) didn't work, but the fact that subdomains don't work either makes me think there's something else going on here.
This is a linux server running plesk.