Comment 1 for bug 1045537
Revision history for this message
| Salvatore Orlando (salvatore-orlando) wrote | #1 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
a60fb26
(Get the code!)
- dnsmasq-dns-server flag.
Frankly, I don't see any reason for exposing this information to the tenant. If the tenant is happy with whatever the provider gives for name resolution, knowing the address of the server if probably not making a lot of difference.
- /etc/resolv.conf
We already launch dnsmasq with --no-resolv. Isn't that enough?
Also, for internal hostnames (meaning the hosts on the quantum subnet) how do we resolve the hostnames? It seems that we are currently implying that either the customer provided dns_nameserver or the provider assigned one will do that.
Correct me if I'm wrong, but the dnsmasq instance should be able to do so; if that is right, would it be possible to always assign the dnsmasq address as dns server for instance and then configure the dhcp agent to use specified dns_nameservers as upstream servers.
I realize the above is slightly off-topic, and I am not requesting you to spend any time on it. Just some food for thought.