On Tue, 02 Feb 2010 23:06:30 +0000, Adam Hardy wrote:

> I'm getting well frustrated trying to work out what this means in terms
> of the failure at my DNS at 194.74.65.68 to discover
> panna-229.trade2win.com and the failure at 4.2.2.1 to find
> panna-229.trade2win.com - and the intermittent nature of the problem.
>
> Can I legitimately hassle my service provider about this? Or is it my
> fault? Could it be something to do with my firewall, like ICMP?

Your outputs are right.

If you cannot access to a particular website, test it with an online
proxy.

Greetings,

--
Camaleón


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Reposting with the issue recapped:

I cannot surf this particular public website from my LAN. Is it my DNS or my
what, I don't know.


75% of the time with my normal setup I get "address not found" when surfing it.

This is some diagnostics I was doing:

adam@isengard:~$ host www.trade2win.com
Host www.trade2win.com not found: 3(NXDOMAIN)

And then with another nameserver:

adam@isengard:~$ host www.trade2win.com 4.2.2.1
Using domain server:
Name: 4.2.2.1
Address: 4.2.2.1#53
Aliases:

www.trade2win.com is an alias for panna-229.trade2win.com.
panna-229.trade2win.com has address 208.43.120.229
Host panna-229.trade2win.com not found: 3(NXDOMAIN)
Host panna-229.trade2win.com not found: 3(NXDOMAIN)


I can surf the site from a proxy website like proxify.co.uk

The intermittent nature of the problem is puzzling me too. Can anyone say what
my course of action should be?



Thanks
Adam


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On Fri, 05 Feb 2010 18:42:09 +0000, Adam Hardy wrote:

> Reposting with the issue recapped:
>
> I cannot surf this particular public website from my LAN. Is it my DNS
> or my what, I don't know.

(...)

> The intermittent nature of the problem is puzzling me too. Can anyone
> say what my course of action should be?

It looks crystal clear to me: blame your ISP routing tables, any proxy or
service that it can be being used by them to filter Internet traffic or
just its DNS servers :-)

There is not much more you can do at your side, unless you contact your
ISP provider and explain them this issue. They are failing at some point.

Greetings,

--
Camaleón


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

2010/2/5 Joe:

(you forgot replying to the list)

> Camaleón wrote:

>> There is not much more you can do at your side, unless you contact your
>> ISP provider and explain them this issue. They are failing at some
point.
>>
>
> EDNS? It has caused a lot of this kind of thing with Windows, where the
> answer is to disable it. Possibly your ISP's DNS server is trying it,
and
> not all of the Internet infrastructure can deal with it yet.

Maybe, who knows... but I think EDNS will interfere with many other
sites, not just one :-?

OTOH, what the OP is experiencing I also have suffered from time to time.
Just changing the gateway to go out with another router (or switching
back to a dial-up modem :-P) solves the issue. It uses to be a temporaly
error.

> http://en.wikipedia.org/wiki/Extension_mechanisms_for_DNS
> https://lists.isc.org/pipermail/bind-users/2009-January/074921.html

Greetings,

--
Camaleón



--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Camaleón on 05/02/10 18:56, wrote:

On Fri, 05 Feb 2010 18:42:09 +0000, Adam Hardy wrote:


Reposting with the issue recapped:

I cannot surf this particular public website from my LAN. Is it my DNS
or my what, I don't know.


(...)


The intermittent nature of the problem is puzzling me too. Can anyone
say what my course of action should be?


It looks crystal clear to me: blame your ISP routing tables, any proxy or
service that it can be being used by them to filter Internet traffic or
just its DNS servers :-)


It's a British-audience website and my ISP is British Telecom, plus it's an
intermittent problem, so it's unlikely to be something like ISP routing tables,
which shouldn't change on an hour by hour basis.


I guess it's just not a debian problem at all. Thought it might have been
something in the way I set up my gateway server.


OK, I'll see if I can figure out a way of automatically inserting the nameserver
4.2.2.1 into my resolv.conf via the dhcp config.


Thanks anyway, and Florian thanks for the tip re: 4.2.2.1

Regards
Adam


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On Fri, 05 Feb 2010 20:40:01 +0000, Adam Hardy wrote:

> Camaleón on 05/02/10 18:56, wrote:

>> It looks crystal clear to me: blame your ISP routing tables, any proxy
>> or service that it can be being used by them to filter Internet traffic
>> or just its DNS servers :-)
>
> It's a British-audience website and my ISP is British Telecom, plus it's
> an intermittent problem, so it's unlikely to be something like ISP
> routing tables, which shouldn't change on an hour by hour basis.

What the tests you have performed are telling you is that your ISP *is*
the problem, whatever the problem is :-)

> I guess it's just not a debian problem at all. Thought it might have
> been something in the way I set up my gateway server.

Debian? I don't think so, but you can always discard that hypothesis by
loading any linux LiveCD available out there, just for testing purposes.

> OK, I'll see if I can figure out a way of automatically inserting the
> nameserver 4.2.2.1 into my resolv.conf via the dhcp config.

Can you "browse" that website by using another DNS server? :-?

If yes, the problem is even more clear: faulty dns servers from your ISP.

> Thanks anyway, and Florian thanks for the tip re: 4.2.2.1

Greetings,

--
Camaleón


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On Friday 05 February 2010 20:40:01 Adam Hardy wrote:
> It's a British-audience website and my ISP is British Telecom, .... so it's
unlikely to be something like ISP routing
> tables

s/likely/unlikely??? Or have you contact with a second firm called BT that I
don't know. ;-)

Lisi


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Lisi on 05/02/10 21:54, wrote:

On Friday 05 February 2010 20:40:01 Adam Hardy wrote:
It's a British-audience website and my ISP is British Telecom, .... so it's

unlikely to be something like ISP routing

tables


s/likely/unlikely??? Or have you contact with a second firm called BT that I
don't know. ;-)


Really? this is the first time in 10 years I've experienced this and I've never
heard of anyone experiencing it either.


I don't think BT are that great, and I am prone to jumping to conclusions, but
in this case I didn't because I really thought /unlikely/ - unless it is a new
phenomenon)


And with just one website? bizarre... but then it might be perfectly logical if
I knew more about DNS.



--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On Fri, 2010-02-05 at 18:56 +0000, Camaleón wrote:

> It looks crystal clear to me: blame your ISP routing tables, any proxy or
> service that it can be being used by them to filter Internet traffic or
> just its DNS servers :-)

I'm just an observer of this conversation, but can you clarify your
reasoning?

I'm curious as to the reason the name can be both resolved and not
found, but I get the same result here, from two machines with completely
different routing and dns (I think).

Richard



--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On Sun, Jan 31, 2010 at 4:27 AM, Adam Hardy <adam.ant@cyberspaceroad.com> wrote:
> and finally my resolv.conf (rewritten by dhcp.client when picking up IP
> address from the DSL modem):
>
> adam@isengard:~$ cat /etc/resolv.conf
> domain localdomain
> search localdomain
> nameserver 127.0.0.1
> nameserver 194.74.65.68

Your resolv.conf is pointing to 127.0.0.1 for your primary nameserver.
Are you running DNS services on your local host?


> adam@isengard:~$ host www.trade2win.com
> Host www.trade2win.com not found: 3(NXDOMAIN)

Here, you're querying your primary nameserver for the IP address of
www.trade2win.com. It's failing to resolve it.


> And then with another nameserver:


> adam@isengard:~$ host www.trade2win.com 4.2.2.1
> Using domain server:
> Name: 4.2.2.1
> Address: 4.2.2.1#53
> Aliases:

> www.trade2win.com is an alias for panna-229.trade2win.com.
> panna-229.trade2win.com has address 208.43.120.229
> Host panna-229.trade2win.com not found: 3(NXDOMAIN)
> Host panna-229.trade2win.com not found: 3(NXDOMAIN)

Now you're telling host to ask 4.2.2.1 to resolve www.trade2win.com
and it succeeds.

I'd recommend you check your local host to see if it's running DNS
services. If it is, you'd need to find out why it's failing to
resolve this host.


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org