hi Carl. Thanks for your reply. DNS redirection is our customer's needs. Customer has their own CDN. They want to save traffic in CDN so that they can cost less money. So they let us hijack some domain names. We used dnsmasq "--cname" option to satisfy their needs. So I think that maybe we can add "cnames" into subnet's attributes. BTW, I'm not quite understand about "--cname is limited to target names known by dnsmasq itself". Could you give me some explanation about it? Thanks Zhi Chang ------------------ Original ------------------ From: "Carl Baldwin"<carl at ecbaldwin.net>; Date: Wed, Feb 17, 2016 05:54 AM To: "OpenStack Development Mailing List (not for usage questions)"<openstack-dev at lists.openstack.org>; Subject: Re: [openstack-dev] [neutron][dnsmasq]DNS redirection by dnsmasq What would be the motivation for this? Could you give some examples of what you'd use it for? Keep in mind that --cname is limited to target names known by dnsmasq itself. Carl On Mon, Feb 15, 2016 at 2:13 AM, Zhi Chang <changzhi at unitedstack.com> wrote: > hi, guys. > Most of us know about DNS redirection. I think that we can implement > DNS redirection in Neutron. In dnsmasq, there is a option named > "--cname"(http://www.thekelleys.org.uk/dnsmasq/docs/dnsmasq-man.html), we > can use this option to implement this function. > > What about your idea? > > > Thanks > Zhi Chang > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160217/ddbc8e18/attachment.html>