[chef] Re: Re: Re: Re: Re: Re: Hostname Naming Strategies

[Adam Jacob < >]

New hostname.

Adam

On Thu, Aug 26, 2010 at 2:48 PM, Ryan Chavez 
<
 >
 wrote:
> Ahh, so I didn't realize that.  Quite a nifty feature.  :)  Thanks for that
> tip.
> So, back to the system reboot, if you get a new DHCP lease, and the hostname
> is something along the lines of
> ec2-123-123-123-123.compute-1.amazon.aws.com, and you reboot, get a new IP
> address, and that address is now 124.124.124.124, I presume the hostname
> will still remain ec2-123-123-123-123.compute-1.amazonaws.com, right?  Or
> will that instance now get a new hostname of ec2-124-124-124-124?
> Ryan
> On Thu, Aug 26, 2010 at 5:34 PM, Adam Jacob 
> <
 >
>  wrote:
>>
>> On Thu, Aug 26, 2010 at 11:06 AM, Ryan Chavez 
>> <
 >
>>  wrote:
>> > Sorry to resurrect an old thread, but I've jumped back into the
>> > DNS/hostname
>> > stuff again, and wanted to ask whether the IP address changes on the AWS
>> > side frequently?  Why wouldn't you just map i-177734b7c.example.com to
>> > the
>> > IP address on the interface?
>>
>> It can change any time the system reboots and gets a new DHCP lease -
>> so it could change at any time.
>>
>> > Also, do you do a similar mapping for your internal host names?  e.g.
>> > would
>> > you map i-177734b7c.int.example.com
>> > to domU-12-84-39-3C-72-B2.compute-1.internal as well?
>>
>> We don't, because if you are inside AWS, their own internal split
>> horizon gets you the right address from resolving the public hostname.
>>
>> Adam
>>
>> --
>> Opscode, Inc.
>> Adam Jacob, CTO
>> T: (206) 508-7449 E: 
>> 
 
>
>



-- 
Opscode, Inc.
Adam Jacob, CTO
T: (206) 508-7449 E: