If you want to run primary DNS from your own PC (and unless you have a fast 24x7, always-on internet connection, I wouldn't) then you'll need three things: great knowledge of bind (which is already part of Suse), someone to run secondary DNS service for you, and the patience of a saint.
You'll need to modify your test domain record to point the nameserver at your home PC. This in itself must be fully qualified, i.e. already have its own dedicated IP address, and dedicated domain name. The domain could reference itself, but this is considered bad practise from a failsafe point of view, although in this case I doubt it'll matter one bit.
bind is probably already running. Setting up a domain is simply a matter of modifying the name service records (which are plain text files) and you are away. Of course the domain won't actually DO anything other than resolve without you installing something else (web server, ftp, etc).
If you want to learn how to run a DNS server for real-world use, then O'Reilly publish an excellent book on bind that was my absolute bible several years ago. If you just want a domain to point to your home PC and don't care too much how it works, there are loads of dynamic DNS servers out there (no-ip.com, etc)
"Bite my shiny metal ass" (Futurama)
"Don't ping my cheese with your bandwidth" (Dilbert)