[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: one website gives "address not found" from LAN



Adam Hardy on 31/01/10 12:27, wrote:
Florian Kulzer on 31/01/10 10:04, wrote:
On Sun, Jan 31, 2010 at 01:16:13 +0000, Adam Hardy wrote:
Klistvud on 30/01/10 23:48, wrote:
Dne, 30. 01. 2010 14:35:12 je Adam Hardy napisal(a):

Hi Folks
thanks for the advice - I do know the website is running fine
out there - I just can't access it from my LAN. From my mobile
phone, fine. But not from my lan.

[...]

Try if you can resolve the name using another nameserver, for example:

  host www.trade2win.com 4.2.2.1

If that works then you have a problem with your standard nameserver and
we need to see the contents of your /etc/resolv.conf.

Well it looks like it half works:

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)

and
adam@isengard:~$ traceroute trade2win.com
traceroute to trade2win.com (208.43.120.229), 30 hops max, 40 byte packets
 1  * * *
 2  * * *
 3  * * *
 4  * * *
 5  * 213.120.176.58 (213.120.176.58)  26.944 ms  27.281 ms
 6  213.120.176.182 (213.120.176.182)  29.258 ms  6.146 ms  6.785 ms
 7  213.120.176.137 (213.120.176.137)  6.625 ms  6.876 ms  8.158 ms
8 core1-gig10-0-0.faraday.ukcore.bt.net (62.172.102.133) 7.173 ms 8.175 ms 7.016 ms
 9  62.172.103.25 (62.172.103.25)  9.638 ms  8.809 ms  8.657 ms
10 transit1-xe0-0-0.ealing.ukcore.bt.net (62.6.200.106) 7.697 ms 7.985 ms 8.941 ms 11 t2c1-ge14-0-0.uk-eal.eu.bt.net (166.49.168.25) 7.954 ms 8.859 ms 9.212 ms 12 t2c1-p4-0-0.us-ash.eu.bt.net (166.49.164.225) 89.994 ms 90.042 ms 89.894 ms 13 te1-2.cer01.wdc01.washingtondc-datacenter.com (206.223.115.185) 82.921 ms 83.143 ms 83.012 ms 14 po1.fcr01.wdc01.washingtondc-datacenter.com (208.43.118.134) 90.961 ms 91.040 ms 91.260 ms
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *


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

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?

Thanks
Adam


Reply to: