Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have a PC with two NICs, one is connected to a LAN (eth0, static IP, another to a DSL modem in DMZ mode (eth1, receives public IP from modem).

Yesterday, it suddenly stopped working for accessing the Internet.

I've narrowed down the problem to this (or maybe this is just a side-effect, I'm not sure):

$ route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface     *          U     1      0        0 eth0
link-local      *          U     1000   0        0 eth0
default         <public_ip>         UG    0      0        0 eth1

Edit: By public_ip I don't mean the actual public IP assigned to this machine, but another public IP, which I guess it's the one assigned to the modem.

With the default routes as above, I can ping to IPs but I cannot resolve domains, so it seems DNS is blocked somehow or maybe it's trying to use the DNS server from eth0.

If I delete route, then instead of the public_ip it shows the FQDN. And then I can resolve domains and access the Internet just fine.

If I assign another computer as the DMZ node in the modem, it works just fine, so it has to be something with this PC. I even tried another NIC for eth0, but no dice.

Any ideas?

share|improve this question
up vote 1 down vote accepted

Based on your additional answer:

This was happening because the address used by your modem is also within the address ranged used on your internal network.

As you had no specific routing table entry for 192.168.1/24 your PC used the best route it had - the one to 192.168/16.

share|improve this answer

Whats in your /etc/resolv.conf? Could it be trying resolve using something in

share|improve this answer
namserver – Ivan Sep 17 '09 at 18:41

I'm not sure why this problem arised, one moment it was working fine, the next...

Anyway, the problem seems to be that the modem had an IP address like (our internal network is, and it seems the machine was trying to find inside our LAN (whyyyy!?!?).

I didn't notice it before because of the public IP assigned to the machine (i.e., not 192.168.1.x).

So I changed the IP used by the modem, and it now works.

I'm still wondering what the hell happened here. The best explanation I can find is that our ISP updated the modem's firmware without our knowledge, and this somehow interfered with how it was working before.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.