That works, I had overridden the search field in the interface description.

Thanks again

Nick


On 6 Feb 2013, at 17:04, Anthony Xu <xuefei...@citrix.com> wrote:

> search pilot.cs.ha
> 
> hostname -f should work.
> 
> 
> Anthony
> 
>> -----Original Message-----
>> From: Anthony Xu
>> Sent: Wednesday, February 06, 2013 3:03 PM
>> To: cloudstack-users@incubator.apache.org
>> Subject: RE: Basic Zone DHCP Issues
>> 
>> There should be search entry in guest VM /etc/resolv.conf
>> search testing001.pilot
>> 
>> 
>> 
>> Anthony
>> 
>>> -----Original Message-----
>>> From: Nick Wales [mailto:n...@nickwales.co.uk]
>>> Sent: Wednesday, February 06, 2013 1:58 PM
>>> To: cloudstack-users@incubator.apache.org
>>> Subject: Re: Basic Zone DHCP Issues
>>> 
>>> Hi Anthony,
>>> 
>>> Thank you, that fix has indeed changed the offending line to: option
>>> domain-name "pilot.cs.ha";
>>> 
>>> The remaining issue is that the guests do not know their FQDN because
>>> the host-name offered is just a short name. From overriding that
>> value
>>> the dhcp response should be changed from,
>>> 
>>> option host-name "testing001";
>>> 
>>> to
>>> 
>>> option host-name "testing001.pilot.cs.ha";
>>> 
>>> for the guest to work properly.
>>> 
>>> 
>>> 
>>> On 6 Feb 2013, at 15:11, Anthony Xu <xuefei...@citrix.com> wrote:
>>> 
>>>> This is a bug, please file a bug for CS 4.1,
>>>> 
>>>> Try below workaround,
>>>> - in mysql CloudStack DB, find the network entry in networks table,
>>> the network entry has "guest_type" with Public
>>>> - set "network_domain" to "pilot.cs.ha" for this entry
>>>> - stop/start virtual router VM
>>>> - reboot user VM
>>>> 
>>>> 
>>>> Anthony
>>>> 
>>>> 
>>>>> -----Original Message-----
>>>>> From: Nick Wales [mailto:n...@nickwales.co.uk]
>>>>> Sent: Wednesday, February 06, 2013 12:41 PM
>>>>> To: cloudstack-users@incubator.apache.org
>>>>> Subject: Basic Zone DHCP Issues
>>>>> 
>>>>> I have a basic network with a VR providing DHCP and Userdata only.
>>> DNS
>>>>> is provided externally.
>>>>> 
>>>>> The zone has a network domain of "pilot.cs.ha" but the dhcp lease
>>> gives:
>>>>> 
>>>>> option domain-name "cloudnine.internal";
>>>>> 
>>>>> Should this not be appropriate for the zone? If not how would I
>>> expect
>>>>> the guest to know its domain?
>>>>> 
>>>>> Running 'hostname -f' returns "hostname: Unknown host" so the fqdn
>>> is
>>>>> not getting populated by DHCP.
>>>>> 
>>>>> What am I missing? All I want is for the guest to come up with its
>>> fqdn
>>>>> appropriate to the zone.
>>>>> 
>>>>> Thanks
>>>>> 
>>>>> Nick
> 

Reply via email to