client does not handle hostnames in config

If the servers are adjusted to use hostnames instead of IP addresses, the client will receive a hostname and will need to configure itself from that.

Bug reporter (on enyim, not on couchbase client) says there is an issue doing so however:

I'm running membase server on windows 2008 r2 on ec2. I've setup a cluster using the hostname's by updating the service_register bat file as
specified here:
http://www.couchbase.org/wiki/display/membase/Using+Membase+in+the+Cloud#UsingMembaseintheCloud-IPaddresses

The cluster has recognised the servers, i'm getting a response back from the endpoints (in json) etc, but i seem to keep getting this error when i'm trying to
access the cluster from my web app.

2011-10-16 16:25:26,845 [12] INFO Membase.MembasePool [(null)] - Received new configuration.
2011-10-16 16:25:26,845 [12] INFO Membase.MembasePool [(null)] - Received new configuration.
2011-10-16 16:25:26,845 [12] INFO Membase.MembasePool [(null)] - Has vbucket. Server count: 2
2011-10-16 16:25:26,845 [12] INFO Membase.MembasePool [(null)] - Has vbucket. Server count: 2
2011-10-16 16:25:26,846 [12] ERROR Membase.MembasePool [(null)] - Failed to initialize the pool.
System.FormatException: An invalid IP address was specified.
at System.Net.IPAddress.InternalParse(String ipString, Boolean tryParse)
at Membase.MembasePool.InitVBucket(ClusterConfig config, ISaslAuthenticationProvider auth) in d:\d\repo\EnyimMemcached\Membase\MembasePool.cs:line 207
at Membase.MembasePool.ReconfigurePool(ClusterConfig config) in d:\d\repo\EnyimMemcached\Membase\MembasePool.cs:line 139