[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13743553#comment-13743553
 ] 

ASF subversion and git services commented on CLOUDSTACK-4132:
-------------------------------------------------------------

Commit 66d76150657cd0e8d44e5be8307b8c59327b686d in branch refs/heads/master 
from [~bharat.kumar]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=66d7615 ]

CLOUDSTACK-4132 current dnsmasq config does not allow guest virtual 
machines(clients) to update its hostnames with a DNS server

Introducing the option dhcp-client-update fails if the dnsmasq version is less 
than 2.6 (like in older templates).
Added a check for the version in cloud-early-config. will add 
dhcp-client-update option in the config file only
if the dnsmasq version is 2.6 and above.

Signed-off-by: Jayapal <jaya...@apache.org>

                
> current dnsmasq config does not allow guest virtual machines(clients) to 
> update its hostnames with a  DNS server
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-4132
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4132
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the 
> default.) 
>          Components: Virtual Router
>    Affects Versions: 4.2.0
>            Reporter: Ram Ganesh
>            Assignee: Bharat Kumar
>            Priority: Critical
>             Fix For: 4.2.0
>
>
> Current dnsmasq.conf does not have "dhcp-client-update" flag enabled thereby 
> preventing say Windows clients to update AD servers with its hostname. We 
> should enhance the config file to support this. More information about this 
> parameter can be found here - 
> http://www.thekelleys.org.uk/dnsmasq/docs/dnsmasq-man.html

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to