search

jdppettit / space-personal

A virtualization control panel written in Python
4 stars 5 forks source link

DNS #24

Open jdppettit opened 9 years ago

jdppettit commented 9 years ago

If we want this to be as full featured as possible we should have some sort of DNS service either baked in, or supported via third party API's.

@levlaz Would you like to see support for all providers (and let the user decide), a local DNS server, or all of the above?

Implementing the API calls to use the providers we support would probably be the easiest and likely he most robust (given users cannot host their own stuff with a single name server anyway).

levlaz commented 9 years ago

I think it would be easiest to have our own DNS services. Especially from a troubleshooting perspective. I feel like we have the resources to make this happen. :)

Sent from my iPhone

On Feb 14, 2015, at 11:14 PM, Joe Pettit notifications@github.com wrote:

If we want this to be as full featured as possible we should have some sort of DNS service either baked in, or supported via third party API's.

@levlaz Would you like to see support for all providers (and let the user decide), a local DNS server, or all of the above?

Implementing the API calls to use the providers we support would probably be the easiest and likely he most robust (given users cannot host their own stuff with a single name server anyway).

— Reply to this email directly or view it on GitHub.

jdppettit commented 9 years ago

Do you mean a DNS service we run ourselves (on our infra) or one that runs on the host Space is running on (the users infra)?

levlaz commented 9 years ago

I was suggesting we host DNS ourselves. I think we have the resources to accomplish this, and it would be useful for our own stuff in the future as well.

jdppettit commented 9 years ago

@levlaz So for this, should we not implement any provider's DNS API's?