On 2005-01-22 19:18:45 + (Sat, Jan), Steve wrote:
I've a small network with a WinXp PC, Gentoo PC and Dlink 504T ADSL
router/NAT/Firewall/Ethernet Switch box. The Dlink serves DHCP services
and DNS to my LAN - these DLink services have been verified as working
flawlessly from my WinXp
Thanks for the suggestions so far... even though I don't think the issue
is resolved... It has been useful that people have confirmed that I'm
not doing anything obviously dumb - but I still haven't got to the
bottom of this...
Chris suggested:
Why don't you put your ISP's DNS servers in
I emerged the bind-tools package and had a play with dig and nslookup.
To further add to the intrigue of this bizarre problem - I was surprised
to find that both dig and nslookup (like ping) correctly resolve
addresses - whereas wget and lynx still stubbornly insist that sites not
On Mon, 24 Jan 2005 15:55:55 +0100, Mariusz Pkala [EMAIL PROTECTED] wrote:
I emerged the bind-tools package and had a play with dig and nslookup.
To further add to the intrigue of this bizarre problem - I was surprised
to find that both dig and nslookup (like ping) correctly resolve
On Monday 24 January 2005 16:55, Mariusz Pkala wrote:
I emerged the bind-tools package and had a play with dig and nslookup.
To further add to the intrigue of this bizarre problem - I was surprised
to find that both dig and nslookup (like ping) correctly resolve
addresses - whereas wget
* my resolv.conf file has nameserver 192.168.1.1 - which looks
Why don't you put your ISP's DNS servers in /etc/resolv.conf instead of
your router.
Chris
--
gentoo-user@gentoo.org mailing list
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Your DLink is not a DNS server. If you look at the configuration of
the DLink you will find the DNS servers that it knows about. You then
need to add those address to your /etc/resolv.conf file.
I am behind a Linksys my /etc/resolv.conf file looks
