can you post the output of your ping to www.yahoo.com while /etc/resolv.conf has nameserver=24.30.200.3.

Hmm well scratch that last post I made. In my staring at the screen for hours and hours today, I was one number off on the dns1.rr.com ip address (24.30.300.3 instead of 24.30.200.3 - stupid me).

24.30.200.3 pinged fine.
'A dig www.yahoo.com @24.30.200.3' seemed to work too. It returned a bunch of answers relating to the www.yahoo.com address. Question section, answer section, authority section, etc... It seems to be working.

So 24.30.200.3 is working with the dig function, I can ping 24.30.200.3, and it's in my resolv.conf file. Still no internet.

now can you ping www.yahoo.com or dns1.rr.com by their names?

In the console, I pinged www.yahoo.com, but it said unknown host.

When I ping dns1.rr.com it returns fine. Isn't that because the dns1.rr.com address is identified in my /etc/resolv.conf?

Ok when I ping yahoo.com without the 'www' then it pings fine.

Still no internet.

By no internet, do you mean you are not able to browse?

You could try turning everything off, plug your network card directly into the modem, turn on the modem then turn the computer on and see if the same problem persists when you are directly connected to the modem with nothing inbetween.

ppuru - yes, that means I can't browse through Konqueror.

Looking_Lost - I'll try that and see, but if it works, how does that solve my router issue?

---edit---
I tried pinging some other addresses (google.com, etc) and got no response. Maybe I only got a ping off yahoo.com because I ran the dig command?

It doesn't but it eliminates it one way or the other


If it works directly connected to the modem it's probably something to do with the router

If it's exactly the same then, well it isn't your router

Just eleminating things.

As you are able to ping to the internet, this does not seem a router issue anymore.

does your router have some kind of firewalling?

Check the settings on your Konquererer.

If you have lynx or links (text based browsers) installed, you can try browsing through that just to troubleshoot.

I'm only able to ping to the internet with IP addresses or a DNS after I run the dig command on a particular DNS address. It remains that I still cannot ping DNS addresses from scratch.

My router doesn't have any firewall besides what is default in the router itself being a firewall. I can open all the ports if you think that will make a difference.

I looked through Konquerer and could not find any settings that should be influencing my ability to browse the internet.

I used Links and it could not find www.yahoo.com. It did find help.rr.com however (Konquerer could not find help.rr.com). I couldn't find any random with Links though. I also tried connecting to Google's direct IP address (216.239.39.99), but the browser just hangs (I can ping that address fine).

Pinging yahoo.com again, there is no response now. It returns "unknown host". Now I'm becoming far more confused. Pinging the rr.com addresses return fine.

Well in redhat theres a GUI configuring utility for the network and if I give myself a static IP instead of a dynamic IP i need to specify the DNS address. I guess that it doesn't apply to you. Oh well.

nateinabox

Does your router have some filtering/firewalling feature?

I am not sure whether this will work but...

Try giving the IP address of your router as the ProxyServer in Konquerer configuration and try browsing.

There are no additional filtering features that are turned on, and there is no firmware firewall features besides that of the router itself acting like a router should.

I tried using the router as the ProxyServer. It didn't do anything. It just times out basically.

Here's more for you to chew on though. I DMZ'd the router, and I can access help.rr.com through Konquerer (without the proxy router trick), but nothing else. I tried accessing pages from their IP addresses (like Google), but it just hangs, not finding anything.

It seems there's a combined problem with my router and my DNS routing.

I'd still do what I suggested before - connecting directly to the modem and getting all your settings as normal via dhcp.

If that works then you know for definite you have a fully functional dhcp enabled client

Then look at the routers internal settings, sometimes just turning them off for a minute helps clear up problems.