PHWinfo - Afficher un message - Proxy proof website? Can't load it through any proxy.

19/05/2007, 08h51

On Fri, 18 May 2007 21:59:26 -0400, Barry Margolin
<barmar@alum.mit.edu> wrote:

>In article <f2lc1d$2a0$3@aioe.org>, nospamatall <nospamatall@iol.ie>
>wrote:
>>
>> Not sure what you mean, aweb.com resolves fine, so either the subdomains
>> don't exist or are set not to respond. But I suspect that isn't what you
>> mean.
>
>That's exactly what he means. The names "aweb.com" and "www.aweb.com"
>resolve fine, but the OP said that his problem was with
>"this.site.com.aweb.com", and that name doesn't resolve.
>
>What's strange is that the OP claims to be able to access the site when
>he's not using a proxy. My browser doesn't use a proxy, and I tried to
>go to the URL he gave and it failed because the server name doesn't
>exist.
>That's exactly what he means. The names "aweb.com" and "www.aweb.com"
>resolve fine, but the OP said that his problem was with
>"this.site.com.aweb.com", and that name doesn't resolve.

>What's strange is that the OP claims to be able to access the site when
>he's not using a proxy. My browser doesn't use a proxy, and I tried to
>go to the URL he gave and it failed because the server name doesn't
>exist.

>--
>Barry Margolin, barmar@alum.mit.edu
>Arlington, MA
>*** PLEASE don't copy me on replies, I'll read them in the group ***

hmm, didn't catch that Barry, I just scanned his OP quickly & looked
for the obvious error in it

if what you say about his OP is true, I'd say he might've been posting
from the aweb.com domain, & there was (possibly) a web server
configured on that domain with support from a local DNS server
(serving the aweb.com domain) that was able to resolve the
'this.site.com.aweb.com' domain name... it is doable if one is hosting
their own DNS server & not fully playing by the DNS rules (the '.com'
domain hierarchy is not supposed to be in a domain name as part of the
'.com' level domain, as in 'this.site.com' being in the 'aweb.com'
domain.. hmm)

but this is doable, not supposed to be done & not good DNS practice &
likely to be flagged as DNS abuse if on the www, but for a local DNS
server hosting a private LAN domain (a DNS server not open to the www
that is), perfectly doable

maybe this is what was going on, why it worked for OP but nobody else?
*shrugs -jg

19/05/2007, 08h51	#8
joeyg Messages: n/a Hébergeur:	Re: Proxy proof website? Can't load it through any proxy. On Fri, 18 May 2007 21:59:26 -0400, Barry Margolin <barmar@alum.mit.edu> wrote: >In article <f2lc1d$2a0$3@aioe.org>, nospamatall <nospamatall@iol.ie> >wrote: >> >> Not sure what you mean, aweb.com resolves fine, so either the subdomains >> don't exist or are set not to respond. But I suspect that isn't what you >> mean. > >That's exactly what he means. The names "aweb.com" and "www.aweb.com" >resolve fine, but the OP said that his problem was with >"this.site.com.aweb.com", and that name doesn't resolve. > >What's strange is that the OP claims to be able to access the site when >he's not using a proxy. My browser doesn't use a proxy, and I tried to >go to the URL he gave and it failed because the server name doesn't >exist. >That's exactly what he means. The names "aweb.com" and "www.aweb.com" >resolve fine, but the OP said that his problem was with >"this.site.com.aweb.com", and that name doesn't resolve. >What's strange is that the OP claims to be able to access the site when >he's not using a proxy. My browser doesn't use a proxy, and I tried to >go to the URL he gave and it failed because the server name doesn't >exist. >-- >Barry Margolin, barmar@alum.mit.edu >Arlington, MA >* PLEASE don't copy me on replies, I'll read them in the group * hmm, didn't catch that Barry, I just scanned his OP quickly & looked for the obvious error in it if what you say about his OP is true, I'd say he might've been posting from the aweb.com domain, & there was (possibly) a web server configured on that domain with support from a local DNS server (serving the aweb.com domain) that was able to resolve the 'this.site.com.aweb.com' domain name... it is doable if one is hosting their own DNS server & not fully playing by the DNS rules (the '.com' domain hierarchy is not supposed to be in a domain name as part of the '.com' level domain, as in 'this.site.com' being in the 'aweb.com' domain.. hmm) but this is doable, not supposed to be done & not good DNS practice & likely to be flagged as DNS abuse if on the www, but for a local DNS server hosting a private LAN domain (a DNS server not open to the www that is), perfectly doable maybe this is what was going on, why it worked for OP but nobody else? *shrugs -jg