It appears that this is not an issue related to DHCP, but rather related
to the case of domain name for the server.
When we create a node-agent name based on a hostname, what are we doing
regarding handling of the name?
- Do we take into account that host name are case-insenstive?
- Do we properly handle partially qualified names?
Tom
On 6/14/2010 10:59 PM, Ludovic Champenois wrote:
> On 6/14/10 6:36 PM, Carla Mott wrote:
>> Hi,
>>
>> I'm working on multiple hosts and I want to run create-local-instance
>> on my instance machine, bear.sfbay.sun.com and have the DAS running
>> on dhcp-usca14-133-205.sfbay.sun.com. When I run the
>> create-local-instance on bear and provide
>> --host=dhcp-usca14-133-205.SFBay.Sun.COM it actually creates the
>> instance on the local machine and sets the DAS to localhost. However
>> if I do --host=dhcp-usca14-133-205.sfbay.sun.com everything works as
>> expected.
>> Note that if I make decide to make bear the DAS machine instead the
>> entry in the domain.xml for the nodeagentref in server element is
>> "dhcp-usca14-133-205.SFBay.Sun.COM". In other words, I have to
>> specify using all lowercase even though the values in the domain.xml
>> are not stored that way.
> In general, setting up clusters and instances in a DHCP environment
> with dynamic hostnames is a recipe for disaster:-)
>
> Ludo
>>
>> carla
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: admin-unsubscribe_at_glassfish.dev.java.net
>> For additional commands, e-mail: admin-help_at_glassfish.dev.java.net
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: admin-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: admin-help_at_glassfish.dev.java.net
>