Re: Suse 9.1 DNS problem

From: Juhan Leemet (juhan_at_logicognosis.com)
Date: 06/21/04


Date: Mon, 21 Jun 2004 04:07:32 -0200

On Sun, 20 Jun 2004 17:59:30 -0400, Arthur Hagen wrote:
> C.O.Jones <{c.o.jones}@blueDESPAMyonder.co.uk> wrote:
>> After using 9.0 for a while I've just done a fresh install using the
>> 9.1 Professional Update. The problem I have is with DNS - I connect
>> to my ISP via a switch to a Dlink router and then to a cable modem.
>> The router is set up as the default route 192.168.0.1 and I can ping
>> this and external sites by IP address. However pings to URLs return
>> "unknown hosts".
>>
>> After some googling I've tried disabling ipv6 which has often been
>> cited as a source of network problems but with no improvement.
>>
>> The pc is based on a CUSI-FX motherboard with built-in LAN which was
>> perfectly happy when I was running 9.0.
>>
>> Any ideas? I'm sure that 9.1 can't be this broken and that it must be
>> a configuration problem
>>
>> Thanks in advance
>
> What does your /etc/resolv.conf look like? Chances are that the Dlink
> router is blocking DNS and acting as a DNS server for the NAT LAN, in which
> case your /etc/resolv.conf probably should look like this:
>
> domain your.dom.ain
> nameserver 192.168.0.1

To get my LinkSys setup with Suse 8.2 (and prior) to work, I had to put in
my ISP DNS server IP addresses, not the IP address of the gateway. I guess
my firewall/router does not forward these lookups? I don't know if it
should, or if there is a setup option. I found these IP addresses by
connecting my web server to my gateway (admin login) and one of the panels
listed the DHCP address my ISP assigned to me (I don't need that for
anything, unless someone else wants to "find" me), and it also listed 2
DNS nameserver IP addresses. Try plugging those into /etc/resolv.conf

Oh, another thing, but pretty obvious. I notice you are using 192.168.0.x
for your subnet addressing (like I did). I had some trouble reprogramming
the LinkSys to use 192.168.0.1 instead of its default 192.168.1.1, and I
had to "fight with it a bit" (can't remember the exact details).

-- 
Juhan Leemet
Logicognosis, Inc.


Relevant Pages

  • RE: Need help with server internet connection
    ... Have you configured the 2Wire with the static IP address your ISP gave you ... Cannot get my server to connect to the internet and have exhausted ... Router: AT&T 2wire gateway - that's about all I know ...
    (microsoft.public.windows.server.sbs)
  • Re: Unable to access certain Web sites... FOLLOW UP....
    ... My ISP "stated" that a secondary DNS Server is not necessary and that I ... let your router to an "automatic" lookup BUT you should provide ... something to do with my routers built-in buggy DNS server and IPv6. ...
    (Fedora)
  • Re: Unable to access certain Web sites... FOLLOW UP....
    ... My ISP "stated" that a secondary DNS Server is not necessary and that I ... let your router to an "automatic" lookup BUT you should provide ... something to do with my routers built-in buggy DNS server and IPv6. ...
    (Fedora)
  • Re: Basic TCP/IP Config
    ... what is the issue with the gateway being the address of the router? ... And what is the benefit of having the client machines use the DNS Server address of the SBS Server? ... On the clients, I set the default gateway to be the Router, and the Primary DNS Server to be the SBS Server and an alternate to be the Router. ...
    (microsoft.public.windows.server.sbs)
  • Re: Setting up wireless in a passthru/bridge mode
    ... the router when the CEICW asks for the ISP DNS server IPs. ... DNS forwarding to the servers the ISP provides. ... faster speeds, etc.), I just change some router settings (e.g., add or remove ...
    (microsoft.public.windows.server.sbs)

Loading