ISP causes winhttp test failures

[Stefan Dösinger]

Hi,
I get winhttp test failures on all my machines: http://test.winehq.org/data/780981bc7a2c8e173bea580a2d748fd7cb242468/wine_st...

I suspect my ISP is to blame. When try to resolve a nonexistant domain name I don't get an error, instead I get a search page: http://suche.upc.at/upcatassist/dnsassist/main/?domain=www.sreaverwdoc.moc

$ ping www.sreaverwdoc.moc
PING www.sreaverwdoc.moc (67.63.50.48): 56 data bytes
Request timeout for icmp_seq 0
...

Verisign was once ordered not to this. But that was in the US. What should we do about this error? I don't think there's any way I can get a DNS error back from my stupid provider :-/

Stefan

[Michael Stefaniuc]

On 04/18/2010 09:49 PM, Stefan Dösinger wrote:
> Hi,
> I get winhttp test failures on all my machines: http://test.winehq.org/data/780981bc7a2c8e173bea580a2d748fd7cb242468/wine_st...
>
> I suspect my ISP is to blame. When try to resolve a nonexistant domain name I don't get an error, instead I get a search page: http://suche.upc.at/upcatassist/dnsassist/main/?domain=www.sreaverwdoc.moc
>
> $ ping www.sreaverwdoc.moc
> PING www.sreaverwdoc.moc (67.63.50.48): 56 data bytes
> Request timeout for icmp_seq 0
> ...
>
> Verisign was once ordered not to this. But that was in the US. What should we do about this error? I don't think there's any way I can get a DNS error back from my stupid provider :-/

Don't use the DNS servers of your provider ...

bye
    michael

[Julius Schwartzenberg]

Stefan Dösinger wrote:
> I get winhttp test failures on all my machines: http://test.winehq.org/data/780981bc7a2c8e173bea580a2d748fd7cb242468/wine_st...
>
> I suspect my ISP is to blame. When try to resolve a nonexistant domain name I don't get an error, instead I get a search page: http://suche.upc.at/upcatassist/dnsassist/main/?domain=www.sreaverwdoc.moc

<>
> Verisign was once ordered not to this. But that was in the US. What should we do about this error? I don't think there's any way I can get a DNS error back from my stupid provider :-/

Maybe you could use Google's DNS servers for example:
http://code.google.com/speed/public-dns/

Regards,
Julius

[Marcus Meissner]

On Sun, Apr 18, 2010 at 09:49:35PM +0200, Stefan Dösinger wrote:
> Hi,
> I get winhttp test failures on all my machines: http://test.winehq.org/data/780981bc7a2c8e173bea580a2d748fd7cb242468/wine_st...
>
> I suspect my ISP is to blame. When try to resolve a nonexistant domain name I don't get an error, instead I get a search page: http://suche.upc.at/upcatassist/dnsassist/main/?domain=www.sreaverwdoc.moc
>
> $ ping www.sreaverwdoc.moc
> PING www.sreaverwdoc.moc (67.63.50.48): 56 data bytes
> Request timeout for icmp_seq 0
> ...
>
> Verisign was once ordered not to this. But that was in the US. What should we do about this error? I don't think there's any way I can get a DNS error back from my stupid provider :-/

Does

notexist.example.com  work?

Ciao, Marcus

[Stefan Dösinger]

Am 18.04.2010 um 22:15 schrieb Marcus Meissner:
> Does
>
> notexist.example.com  work?

$ ping notexist.example.com 
ping: unknown host notexist.example.com

Looks good. And beyond that, anything that doesn't start with www behaves properly too:

$ ping www.srevaewedoc.com
PING www.srevaewedoc.com (67.63.50.48) 56(84) bytes of data.
$ ping mail.srevaewedoc.com
ping: unknown host mail.srevaewedoc.com
$ ping blah.srevaewedoc.com
ping: unknown host blah.srevaewedoc.com

Fwiw, I don't think "use another DNS" is a good fix. I don't care about the winhttp test myself, but if other users have similar issues it will spam test.winehq.org with failures.

[Michael Stefaniuc]

Stefan Dösinger wrote:
> Am 18.04.2010 um 22:15 schrieb Marcus Meissner:
> > Does
> >
> > notexist.example.com  work?
>
> $ ping notexist.example.com 
> ping: unknown host notexist.example.com
>
> Looks good. And beyond that, anything that doesn't start with www behaves properly too:
>
> $ ping www.srevaewedoc.com
> PING www.srevaewedoc.com (67.63.50.48) 56(84) bytes of data.
> $ ping mail.srevaewedoc.com
> ping: unknown host mail.srevaewedoc.com
> $ ping blah.srevaewedoc.com
> ping: unknown host blah.srevaewedoc.com
>
> Fwiw, I don't think "use another DNS" is a good fix. I don't care about the winhttp test myself, but if other users have similar issues it will spam test.winehq.org with failures.

Well the "use another DNS" was for you and not a generic workaround for
the winetest. That's what I would do if the provider would mess with the
DNS.

bye
    michael

[Austin English]

On Mon, Apr 19, 2010 at 7:18 AM, Michael Stefaniuc  wrote:
> Stefan Dösinger wrote:
> > Am 18.04.2010 um 22:15 schrieb Marcus Meissner:
> > > Does
> > >
> > > notexist.example.com  work?
> >
> > $ ping notexist.example.com
> > ping: unknown host notexist.example.com
> >
> > Looks good. And beyond that, anything that doesn't start with www behaves properly too:
> >
> > $ ping www.srevaewedoc.com
> > PING www.srevaewedoc.com (67.63.50.48) 56(84) bytes of data.
> > $ ping mail.srevaewedoc.com
> > ping: unknown host mail.srevaewedoc.com
> > $ ping blah.srevaewedoc.com
> > ping: unknown host blah.srevaewedoc.com
> >
> > Fwiw, I don't think "use another DNS" is a good fix. I don't care about the winhttp test myself, but if other users have similar issues it will spam test.winehq.org with failures.
>
> Well the "use another DNS" was for you and not a generic workaround for
> the winetest. That's what I would do if the provider would mess with the
> DNS.

Have you complained to your ISP? The ones in this area have a webpage
that allows you to disable it.

[Stefan Dösinger]

Am 19.04.2010 um 17:50 schrieb Austin English:
> Have you complained to your ISP? The ones in this area have a webpage
> that allows you to disable it.

Indeed, there was a way. Well hidden, in the FAQ(Small gray-on-white font size 8 link at the bottom), in one of the many junk questions. But it seemed to work.

$ ping www.srevaewedoc.moc
ping: cannot resolve www.srevaewedoc.moc: Unknown host

[Hans Leidekker]

On Sun, 2010-04-18 at 21:49 +0200, Stefan Dösinger wrote:
> Verisign was once ordered not to this. But that was in the US. What should we do about this error?
> I don't think there's any way I can get a DNS error back from my stupid provider :-/

Perhaps a nonexistent local name will work. What happens if you remove
the dots from that domain name?