t;
>>>>
>>>>> -Original Message-
>>>>> From: Andreas Veithen [mailto:andreas.veit...@gmail.com]
>>>>> Sent: Wednesday, 22 December 2010 6:39 AM
>>>>> To: builds@apache.org
>>>>> Subject: [Hudson] Str
;>>> Sent: Wednesday, 22 December 2010 6:39 AM
>>>> To: builds@apache.org
>>>> Subject: [Hudson] Strange DNS behavior on ubuntu1
>>>>
>>>> All,
>>>>
>>>> Does anybody know why this.is.not.a.valid.hostname.at.all.n
On Tue, Dec 21, 2010 at 23:40, sebb wrote:
> On 21 December 2010 21:48, Gav... wrote:
>>
>>
>>> -Original Message-
>>> From: Andreas Veithen [mailto:andreas.veit...@gmail.com]
>>> Sent: Wednesday, 22 December 2010 6:39 AM
>>> To:
On 21 December 2010 21:48, Gav... wrote:
>
>
>> -Original Message-
>> From: Andreas Veithen [mailto:andreas.veit...@gmail.com]
>> Sent: Wednesday, 22 December 2010 6:39 AM
>> To: builds@apache.org
>> Subject: [Hudson] Strange DNS behavior on ubuntu1
&g
> -Original Message-
> From: Andreas Veithen [mailto:andreas.veit...@gmail.com]
> Sent: Wednesday, 22 December 2010 6:39 AM
> To: builds@apache.org
> Subject: [Hudson] Strange DNS behavior on ubuntu1
>
> All,
>
> Does anybody know why this.is.not.a.v
All,
Does anybody know why this.is.not.a.valid.hostname.at.all.no.way
resolves to 98.137.132.14 (nx1.ycpi.vip.sp2.yahoo.net) on ubuntu1? We
(Axis2) have a couple of test cases that use this host name with an
assertion on the expected exception (UnknownHostException), but they
now all fail because
