From: David Nesbitt (nospam_at_charlecote.org.uk)
Date: Sun, 13 Mar 2005 22:11:11 +0000
In article <baCdnckrqbPOOqnfRVn-qQ@comcast.com>,
Steve Magoon <firstname.lastname@example.org> wrote:
>"David Nesbitt" <email@example.com> wrote in message
>> If I recall correctly, your original symptom was that your internal
>> machines could not resolve domain names, but that they could ping public
>> IP addresses. You have not, AIUI, described any problem with using the
>> "internet" from your Suse box.
>I can ping, telnet, and do a traceroute from my internal machines using an
>ip address. But I cannot "browse" from any of them. The SuSE box can browse,
>ping, etc., just fine.
>> Have you double-checked (a) that your internal machines have the
>> appropriate DNS server settings, and (b) that they get replies to DNS
>> requests? I'm beginning to suspect that you will need to set up a DNS
>> server in your Suse box on 192.168.0.1, for the benefit of your internal
>Ohhh. I have set my internal machines' DNS server settings to the static ip
>address of my SuSE box, 192.168.0.1. Should I instead set them to the DNS
>server addresses of my cable internet company?
Yes. Configure your internal machines manually to use your cable
company's DNS server addresses and, in most circumstances, that you
should "just work".
>Or should I set up a DNS
>server on the SuSE box?
From what you've said, your internal machines are trying to resolve DNS
through 192.168.0.1 which is not apparently running either a DNS server
or a DNS proxy. I suggest that you should not try to set up your own
DNS server, except as a last resort if nothing else works. I feel
confident, however, that using your cable company's DNS servers will
work for you now.
-- David Nesbitt N.B. Email sent to "nospam" will be rejected. Please use Reply-To address.