If it were not what you reported in post #2, I would suspect a hardware problem. But what you reported is
exactly what a DNS problem looks like.
At this point (updates aside) do you have a functioning system? If I were in you shoes, if the system was functioning I would try to get some more data from it, or I would boot from a live CD like Damn Small Linux (DSL) and try to get some data that way.
After my first response to you, I checked a DSL system I have to see what kind of reporting it does when it does a DHCP request. If you have enabled system logging (which is off by default on DSL) with the commands
syslogd and
klogd, it will log details about the DHCP response, including what DNS addresses (if any) are supplied. This sort of info would be useful in diagnosing your problem.
You should also be able to create this same reporting in your Debian system if it is running (minus Internet of course). I am on a public computer right now and don't have access to my Linux stuff, so I might get some details wrong here, but I should be close enough you can figure it out by consulting the
man pages.
What you need to do is add a line to your /etc/syslog.conf file something like:
Code:
daemon.* /var/log/whatever_you _want_for_logfile_name
This should cause all info concerning the DHCP transaction to be logged. You then need to restart you network interface (first making sure it is set up for DHCP).
If you want to try Damn Small Linux and have a computer with CD burner and Internet access, it is only a 50 MB download.