Hello Chris,

The following link might help you with your efforts to deploy a Quick Cloud 
using a single machine.
https://cwiki.apache.org/confluence/display/CLOUDSTACK/QuickCloud 

Thank you,
Chandan.

-----Original Message-----
From: chris snow [mailto:chsnow...@gmail.com] 
Sent: Tuesday, January 28, 2014 10:19 AM
To: users@cloudstack.apache.org
Subject: Re: Internal DNS confusion

Hi Shanker,

I'm trying to build a self contained cloudstack virtualbox virtualmachine 
similar to devcloud.

I'm thinking that the virtualmachine will need to run its own internal DNS 
server, but it probably only needs one entry, the hostname of the virtualbox 
virtualmachine.

Sorry if these questions are basic, but I haven't seen any topology examples 
that describe everything on a single node, so I'm confused what is required.

Many thanks,

Chris



On Tue, Jan 28, 2014 at 5:07 PM, Shanker Balan <shanker.ba...@shapeblue.com> 
wrote:
> Comments inline.
>
> On 28-Jan-2014, at 12:47 pm, chris snow <chsnow...@gmail.com> wrote:
>
>> Thanks for the answers Shanker. Some more questions ...
>
> Sure.
>
>
>> Are internal DNS lookups performed only by the system vms?
>
> Dont know.
>
>> If no, what other parts of cloudstack perform internal DNS lookups?
>
> Dunno. Never had a requirement/reason to worry about it as my DNS 
> servers are configured to resolve my RFC1918 assigned LAN devices and public 
> records.
>
>>  For example, does Management Server perform internal DNS lookups?
>
> The management server uses whichever nameservers you have configured 
> in /etc/resolv.conf.
>
> I am not sure why you are digging deep into the DNS settings... its a 
> very simple step while adding a new Zone. Just specify the same DNS 
> settings as used by other devices in your network.
>
> I am however aware that there are MANY networks which still use IP 
> addresses instead of hostnames. If your networks happens to rely on IP 
> addresses, now would be a good time to create a DNS system :)
>
>
>> I'm trying to figure out 'when' I need to add new records to the 
>> internal DNS server.
>
> If you plan to use hostnames instead of IP addresses for resources 
> like hypervisors, storage devices etc, then you need to create DNS records.
>
> Alternatively, you can also add /etc/hosts entries.
>
> Depending on your DNS topology, you might have private internal DNS 
> servers or public hosted DNS services (or both).
>
>
>> I guess one way for me to understand when I need to add a host record 
>> to the internal DNS is by knowing what which parts of the Cloudstack 
>> admin interface have fields that require a corresponding internal DNS 
>> record.  For example:
>>
>>   Network > Add Guest Network > Network Domain
>>   Domains > Add Domain > Network Domain
>>
>> Does each network domain above require an entry to be added into the 
>> internal DNS?  Are there any other places in the admin UI that 
>> require records to be added to the internal DNS server?
>
>
> I believe Sanjeev already replied to this one. "network domains" are 
> handled internally by CloudStack virtual routers.
>
> Regards.
> @shankerbalan
>
>>
>> On Tue, Jan 28, 2014 at 3:52 AM, Shanker Balan 
>> <shanker.ba...@shapeblue.com> wrote:
>>> Comments inline.
>>>
>>> On 28-Jan-2014, at 1:21 am, chris snow <chsnow...@gmail.com> wrote:
>>>
>>>> When creating a new zone, I have to enter the address for Internal 
>>>> DNS Servers.  Extract from the Cloudstack installation manual:
>>>>
>>>> "Internal DNS 1 and Internal DNS 2. These are DNS servers for use 
>>>> by system VMs in the zone (these are VMs used by CloudStack itself, 
>>>> such as virtual routers, console proxies, and Secondary Storage VMs.)."
>>>
>>> The internal DNS server is usually the corporate DNS servers that 
>>> provide "internal" DNS services for your LAN. Usually, these are 
>>> RFC1918 IPs which is why its hosted "internally".
>>>
>>>
>>>> Question 1: Who manages the Internal DNS? Is an Internal DNS server 
>>>> setup and managed by me, or is it setup and managed by Cloudstack?
>>>
>>> You (or your IT team).
>>>
>>>
>>>> Question 2: If Internal DNS is setup and managed by me, how should it be 
>>>> setup?
>>>
>>> set it up any way you look. As long as the internal DNS server can 
>>> resolve the hostname to IP addresses, you should be fine.
>>>
>>>
>>>> Question 3: If it is setup and managed by Cloudstack, when did it 
>>>> get setup, and  how can I find out what address Cloudstack is using 
>>>> for this server?
>>>
>>> Its not managed by cloudstack. Most of the time, your internal and 
>>> external DNS settings would be your corporate DNS server.
>>>
>>> If a public DNS server can resolve IP addresses for hosts in your 
>>> LAN, you can use any public DNS server as your internal and external DNS 
>>> resolver.
>>>
>>> Hope that makes sense.
>>>
>>>
>>> --
>>> @shankerbalan
>>>
>>> M: +91 98860 60539 | O: +91 (80) 67935867 
>>> shanker.ba...@shapeblue.com | www.shapeblue.com | Twitter:@shapeblue 
>>> ShapeBlue Services India LLP, 22nd floor, Unit 2201A, World Trade 
>>> Centre, Bangalore - 560 055
>>>
>>> Need Enterprise Grade Support for Apache CloudStack?
>>> Our CloudStack Infrastructure 
>>> Support<http://shapeblue.com/cloudstack-infrastructure-support/> offers the 
>>> best 24/7 SLA for CloudStack Environments.
>>>
>>> Apache CloudStack Bootcamp training courses
>>>
>>> **NEW!** CloudStack 4.2.1 
>>> training<http://shapeblue.com/cloudstack-training/>
>>> 18th-19th February 2014, Brazil. 
>>> Classroom<http://shapeblue.com/cloudstack-training/>
>>> 17th-23rd March 2014, Region A. Instructor led, 
>>> On-line<http://shapeblue.com/cloudstack-training/>
>>> 24th-28th March 2014, Region B. Instructor led, 
>>> On-line<http://shapeblue.com/cloudstack-training/>
>>> 16th-20th June 2014, Region A. Instructor led, 
>>> On-line<http://shapeblue.com/cloudstack-training/>
>>> 23rd-27th June 2014, Region B. Instructor led, 
>>> On-line<http://shapeblue.com/cloudstack-training/>
>>>
>>> This email and any attachments to it may be confidential and are intended 
>>> solely for the use of the individual to whom it is addressed. Any views or 
>>> opinions expressed are solely those of the author and do not necessarily 
>>> represent those of Shape Blue Ltd or related companies. If you are not the 
>>> intended recipient of this email, you must neither take any action based 
>>> upon its contents, nor copy or show it to anyone. Please contact the sender 
>>> if you believe you have received this email in error. Shape Blue Ltd is a 
>>> company incorporated in England & Wales. ShapeBlue Services India LLP is a 
>>> company incorporated in India and is operated under license from Shape Blue 
>>> Ltd. Shape Blue Brasil Consultoria Ltda is a company incorporated in Brasil 
>>> and is operated under license from Shape Blue Ltd. ShapeBlue is a 
>>> registered trademark.
>>
>>
>>
>> --
>> Check out my professional profile and connect with me on LinkedIn.
>> http://lnkd.in/cw5k69
>
> --
> @shankerbalan
>
> M: +91 98860 60539 | O: +91 (80) 67935867 shanker.ba...@shapeblue.com 
> | www.shapeblue.com | Twitter:@shapeblue ShapeBlue Services India LLP, 
> 22nd floor, Unit 2201A, World Trade Centre, Bangalore - 560 055
>
> This email and any attachments to it may be confidential and are intended 
> solely for the use of the individual to whom it is addressed. Any views or 
> opinions expressed are solely those of the author and do not necessarily 
> represent those of Shape Blue Ltd or related companies. If you are not the 
> intended recipient of this email, you must neither take any action based upon 
> its contents, nor copy or show it to anyone. Please contact the sender if you 
> believe you have received this email in error. Shape Blue Ltd is a company 
> incorporated in England & Wales. ShapeBlue Services India LLP is a company 
> incorporated in India and is operated under license from Shape Blue Ltd. 
> Shape Blue Brasil Consultoria Ltda is a company incorporated in Brasil and is 
> operated under license from Shape Blue Ltd. ShapeBlue is a registered 
> trademark.



--
Check out my professional profile and connect with me on LinkedIn.
http://lnkd.in/cw5k69

Reply via email to