🚀 go-pugleaf

d> you can test the server at http://www.dnsstuff.com 
d> then you can say more about it.  What a little snot.

I can say more about it right now, thank you.  Welcome to (amongst the other
newsgroups that you chose to multi-post in)
"microsoft.public.windows.server.dns" and "comp.protocols.tcp-ip.domains",
where you'll find quite a few people who are capable of diagnosing
misconfigured systems running broken softwares, like yours, directly, without
the need for armbands and floatation devices.

It's (alas!) all too consistent with your inept misconfiguration and your
choice of using broken server software that you point for supposed validation
at a suite of web utilities that aren't actually capable of testing a
(non-ICANN) "." content DNS server, such as you are claiming to be providing. 
So now we have yet further grounds for recommending that one _not_ change
one's "name server info" to 64.146.111.234, in addition to the reasons already
posted: Its administrator doesn't appear to have actually tested its "."
content DNS service, because he/she refers to testing it with tools that are
entirely unsuited for that purpose.

I strongly recommend that you obtain a DNS diagnosis tool such as "dnsqry",
"dnsq", "dig", "dnsquery", or "askmara", learn how to operate it and what its
output means, and use it to look at the misfunctional mess of your DNS
service.

d> what would you do to fix these "issues" 

I'd do at least these:

* Fix the egregiously broken DNS server software, that treats the RD bit
eccentrically and that cannot decide whether domain names exist; either by
complaining to its author (whoever that is) and thereby getting it fixed, or
by simply throwing it away and using a different software ("djbdns",
Microsoft's DNS server, ISC's BIND, or whatever) that can at least provide
content DNS service that works in these respects.

* Follow PacificRoot's instructions, for replicating its DNS data in order to
provide a mirror of its root, _correctly_.

* Configure the content HTTP server so that virtual hosting was actually
working, so that the rest of Internet would see something _other_ than error
pages everywhere.