Thanks for the tips on modifying a TKLVM to include DNS. I'll probably end-up following this route for now.
I want to reiterate that a DNS VM is a good idea. Here's why:
(1) There are entire companies devoted to creating DNS appliance products. For instance, Bluecat Networks makes several hardware-based solutions. I've never used their product, so I can't say whether it works well or not, but my point is, that people are beginning to see DNS as a building-block.
(2) Granted: DNS services are very simple and small so maybe an add-on seems easy enough - but admins are loving the bite-size building-block approach that TKLVM brings. Not making a VM because it's too small or too simple does not seem like a good argument.
(3) TKLVM DNS would help TKLVM users to coordinate using even more TKLVMs, as they run the DNS to point to other installations.
DNS is a commerically available Appliance
Thanks for the tips on modifying a TKLVM to include DNS. I'll probably end-up following this route for now.
I want to reiterate that a DNS VM is a good idea. Here's why:
(1) There are entire companies devoted to creating DNS appliance products. For instance, Bluecat Networks makes several hardware-based solutions. I've never used their product, so I can't say whether it works well or not, but my point is, that people are beginning to see DNS as a building-block.
(2) Granted: DNS services are very simple and small so maybe an add-on seems easy enough - but admins are loving the bite-size building-block approach that TKLVM brings. Not making a VM because it's too small or too simple does not seem like a good argument.
(3) TKLVM DNS would help TKLVM users to coordinate using even more TKLVMs, as they run the DNS to point to other installations.
Thanks for listening!