FastDNSResolver error on 0.7.2 branch

[Frank Scholten <fr...@frankscholten.nl>]

Hi all,

I was running the integration tests on the 0.7.2 branch and I got an
error on FastDNSResolverTest. It had to do with the fact that reverse
DNS lookup failed on the hostname of my machine, where I run the tests
from.

Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.399
sec <<< FAILURE!

Results :

Failed tests:
testResolveAddress(org.apache.whirr.net.integration.FastDnsResolverTest):
InetAddress /192.168.1.103 on interface eth0 got none.local reverse
dns name which in return is an unknown host!

Maybe I am misunderstanding something but to me it seems quite right
that a reverse DNS lookup fails because it's my desktop machine at
home in a 192.168 subnet and there is obviously no DNS record for it.

Thoughts?

Cheers,

Frank

Re: FastDNSResolver error on 0.7.2 branch

[Karel Vervaeke <ka...@ngdata.com>]

I used to deal with this for locally hosted virtual machines by
running dnsmasq and adding a system property (I believe it was
-Ddns.server=127.0.0.1).

Karel

On Tue, Aug 7, 2012 at 10:25 PM, Frank Scholten <fr...@frankscholten.nl> wrote:
> Hi all,
>
> I was running the integration tests on the 0.7.2 branch and I got an
> error on FastDNSResolverTest. It had to do with the fact that reverse
> DNS lookup failed on the hostname of my machine, where I run the tests
> from.
>
> Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.399
> sec <<< FAILURE!
>
> Results :
>
> Failed tests:
> testResolveAddress(org.apache.whirr.net.integration.FastDnsResolverTest):
> InetAddress /192.168.1.103 on interface eth0 got none.local reverse
> dns name which in return is an unknown host!
>
> Maybe I am misunderstanding something but to me it seems quite right
> that a reverse DNS lookup fails because it's my desktop machine at
> home in a 192.168 subnet and there is obviously no DNS record for it.
>
> Thoughts?
>
> Cheers,
>
> Frank