On Sun,07.Feb.10, 19:25:41, Adam Hardy wrote: [big snip] > OK here's my nslookup experiment - here's my resolv.conf which > contains 4.2.2.1 because I modified my dhcp3/dhclient.conf to append > 4.2.2.1 after the BT nameserver (this is a gateway machine): > > adam@isengard:~$ cat /etc/resolv.conf > domain localdomain > search localdomain > nameserver 127.0.0.1 > nameserver 194.74.65.68 > nameserver 4.2.2.1 > > > adam@isengard:~$ nslookup www.trade2win.com > Server: 127.0.0.1 > Address: 127.0.0.1#53 > > Non-authoritative answer: > www.trade2win.com canonical name = panna-229.trade2win.com. > Name: panna-229.trade2win.com > Address: 208.43.120.229 > > adam@isengard:~$ nslookup www.trade2win.com - 194.74.65.68 > Server: 194.74.65.68 > Address: 194.74.65.68#53 > > ** server can't find www.trade2win.com: NXDOMAIN So your ISP's nameserver fails. > adam@isengard:~$ nslookup www.trade2win.com - 4.2.2.1 > Server: 4.2.2.1 > Address: 4.2.2.1#53 > > Non-authoritative answer: > www.trade2win.com canonical name = panna-229.trade2win.com. > Name: panna-229.trade2win.com > Address: 208.43.120.229 > > > Is this incontrovertible evidence that it's not me causing the problem? If you can reproduce it then yes, it shows that the ISP's nameserver is buggy. Regards, Andrei -- Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic
Attachment:
signature.asc
Description: Digital signature