> 1. What does the default EC2 nameserver provide, since it alone cannot > resolve the scalr-generated internal names for our domain? Is this a > nameserver we can configure? Its a regular caching nameserver I guess. Resolv request being forwarded to autoritative nameservers that you have set in SOA record / your registrar (that appear in whois).
> 2. Why aren't the scalr nameserver's included in /etc/resolv.conf by > default instead of the EC2 nameserver? Its a security risk. Someone can create say, ubuntu.org and host a fake .deb packages repository. > > We are also working on configuring our external nameserver to set up > the DNS Zone transfer to the scalr nameservers to see if that allows > us to resolve the internal names without changing /etc/resolv.conf. > We still want to maintain backup DNS outside of the cloud. It should be easier to make a script that would re-generate /etc/hosts file from /etc/aws/hosts Let's see if we can come up with something like this. > > Thanks, > > -Michael > > On Dec 18, 10:43 am, Alex Kovalyov <[email protected]> wrote: > Because /etc/resolv.conf - a file that defines nameservers, >> contains EC2 namesrver, that is, for sure respectsDNShierarchy. >> This parent is your domain that you point to Scalr nameservers. > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "scalr-discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/scalr-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
