Well, there are a few pieces I think you are missing in the DNS puzzle. Here's the breakdown:
A. You have a domain name that is registered (hellbringer.com)
B. When you register a domain name, the domain name service wants to know what your NAME SERVER IP(s) is. A name server is a DNS server, but it holds all relevant info about your domain (and, sometimes, many others as in the case of TZO.com). A name server is like a traffic cop; somebody on the net asks where HELLBRINGER.COM is, and that goes to a DNS server. Then, the DNS server looks up your NAME SERVER which has HELLBRINGER.COM's IP on it (it would also have stuff like mail.hellbringer.com, ftp.hellbringer.com, etc. if you register sub-domains as well). The IP info goes back to the client, and then it can connect to your HELLBRINGER.COM server.
C. The average DNS server that you see is just a request hunter. It may not even know where microsoft.com is, but it can find the "traffic cop" (NAME SERVER) that does know and will bring the info back to you.
Now, what TZO does, is they host name servers that get updated all the time by these little clients. That way, when a DNS server somewhere on the net wants to know where HELLBRINGER.COM is, it gets the request, and looks up the last IP that it was sent by the client on your computer.
I hope this clears it up a little better.