Thanks!
I guess that this occurs if the host is configured with a search
domain and that domain has a wildcard entry. That is not the most
common situation, but we may have users working in this kind of
environment. Therefore I will modify the tests so that they are
skipped dynamically if they are
On 21 December 2010 22:56, Andreas Veithen wrote:
> 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 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: builds@apache.org
>>> Subject: [Hudson] Strange DNS behavio
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
>>
>> All,
>>
>> Does anybody know why 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] Strange DNS behavior on ubuntu1
>
> All,
>
> Does anybody know why this.is.not.a.valid.hostname.at.all.no.way
> resolve
