Ha ha ha... Perhaps we should have an "Ask HN: Do You Host Your Own DNS?" thread ;)
Running BIND is very simple, and there're lots of how-tos and some excellent O'Reilly books, too.
You can run your own DNS on a VPS, on a machine on a static IP, or even on a residential address, if it doesn't change too often. If it does change, you can run your primary on your home and have a public machine be a secondary.
I do! tinydns and dnscache all the way (although considering alternatives that aren't BIND[1]); only problem I've had was the auto-SOA generation which the .is people didn't like (they want each NS to have the same SOA) but since I generate the data file with a script anyway, it was an easy tweak to make that SOA a known value.
[1] Historical issues with running at an ISP in the late 90s and the various security issues since.
Mail-in-a-box is seriously awesome. I was super impressed by how easy it maid emauk hosting for me after hear all the FUD about housing your own email.
My suggestion is to get a new domain and then try it with that. Once everything works, and your IP reputation is in the clear, you can port your other email domains as well.
Running BIND is very simple, and there're lots of how-tos and some excellent O'Reilly books, too.
You can run your own DNS on a VPS, on a machine on a static IP, or even on a residential address, if it doesn't change too often. If it does change, you can run your primary on your home and have a public machine be a secondary.
It opens up so many possibilities :D