-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 04 Aug 2003 13:26:13 +0200, Jos Herni wrote:
That's my computer internal IP number as provided by my router and his[jos@xxxxxxxxxxx jos]$ cat /etc/resolv.conf
; generated by /sbin/dhclient-script
nameserver 192.168.1.1
nameserver 192.168.1.1
internal dhcp server. And this newbie didn't know he was running his own
nameserver ;-) All I did was configuring my router the way it should,
confirming to the website (the Netherlands btw).
So, do you run an own nameserver on 192.168.1.1 or not? It doesn't sound like you do, so the entries in /etc/resolv.conf don't make any sense. Your dhcp server should not give out 192.168.1.1 as being a DNS server.
An earlier reply showed the output from "host" correctly resolving ftp.mozilla.org -- that kinda suggests that DNS is working :-) The router looks as though it's one of those that does DNS caching and DHCP serving as well as routing -- could be one like mine in fact.
In fact, since this is a router cum firewall cum ADSL modem, no amount of configuring DSL connection properties on the RH machine is going to make any difference. It is definitely a good thing to use the routers own caching DNS server.
jch
-- Shrike-list mailing list Shrike-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/shrike-list
