thoughts, notes and mooo...
from the 'why-didn't-I-think-of-this-before' department:
To trace the resolution of a domain name, use:
dig +trace <domain name>
Thanks to my del.icio.us I found dnsreport.com and dnsstuff.com and immediately started testing n--tree.net, lentiform.org.
The DNS configuration for n--tree.net did have a few problems where the reported nameserver (ns.n--tree.net) was different from what I setup at my domain name registrar (output.n--tree.net).
Another problem turned out to be that I made output, mail and ns so called CNAME entries, pointing to n--tree.net.. And you're supposed to make these A entries.
A fix to get rid of all but one warning was adding an alias for abuse@n--tree.net.
The remaining warning for n--tree.net is something about an SPR record. I'll have to study this a bit more to see what I am supposed to to with that.
And now the DNS configuration for n--tree.net gets a "B+" (sometimes even an "A")! :-)
The lentiform.org suffered from most of the same issues. With one import difference being that the nameserver for this domain (ns.n--tree.net), is in another TLD. There's some mentioning of "glue" records that I could (should?) add.
A completely different issue for lentiform.org was reported through the dnsstuff.com tool. For some reason the DNS queries for this domain always get a cached response from ultradns.com.
I have no idea why...
