Virtual DNS questiona and reverse lookup table conflicts

[Bruno Wolff III]

On Mon, Dec 08, 2008 at 09:21:44 -0600,
  "Mikkel L. Ellertson" <mikkel at infinity-ltd.com> wrote:
> Having slave name server that is not on your machines is probably a
> good idea - that way, instead of getting a not found error, they
> would get a not available error. With the first case, people will
> probably think they have the wrong URL, but with the second case,
> they will think that the server is down.

Depends on who you expect to be using the service. The above case is for
http(s) users who know enough to distinguish between the two types of
errors but not smart enough to draw the correct conclusion.
There are costs to running slave servers, particularly ones not under
your direct control (which is probably the common case for hobbiests
having slaves in different locations).
I expect that the normal situation is that having a remote slave dns service
is not worth the costs for hobbiests.