Can't resolve hostnames
 

Hello again, linuxquestions.org users.

I'm back with another problem. I've installed a new router, but as soon as i did i lost the ability to resolve hostnames. (I've had to use windows to log into here!)

The new topography is:

(cloud)
|
82.69.9.203
(new router)
10.0.0.1
|
10.0.0.2
(old router)
192.168.1.1
|
(switching hub)
| | | |
(all my computers)

It used to work, i can't understand why it no longer does.
Anyone got any ideas?

Well, what does resolv.conf look like on your machine?

I've been playing about with that, trying to find a solution:

cat /etc/resolve.conf
nameserver 212.23.3.100
nameserver 10.0.0.1
nameserver 192.168.1.1

The first one is the DNS ip provided by my ISP.
I've tried these in various order, no effect.
At first i thought it was a routing issue, but all the other machines work fine. (they all use 10.0.0.1 for DNS).

Two things I would check here:

1. Make sure that the ethernet s plugged into the right ports on your routers.
2. See if you can ping these addresses.

Yeah, i can ping anything, by IP. All over the world! Just can't resolve hostnames. ***commences hair pulling***

Are you sure that your wiring is correct?

Yes, i just checked again. Absolutely correct. It's just as the diagram. The only difference, the Debian machine uses a static IP, 192.168.1.129, instead of DHCP like everything else.

As i write: Someone told me just now to type nslookup google.com, which i did and it reported this:
nslookup google.com
Server: 194.168.4.100
Address: 194.168.4.100#53

** server can't find google.com: REFUSED

That's the IP of my old DNS at my old ISP. Where's that coming from, since it's not mentioned in /etc/resolve.conf?

The diagram doesn't show what plugs into WAN and numbered ports, that was why I asked. here's a trick, this command will use yahoo's server as the DNS server. if you can hit that you can eliminate all outbound traffic from your broadband modem to your laptop. You may want to try this for your ISP's DNS server as well.

What does your "old router" have set as its DNS server IPs?

nslookup www.google.com ns1.yahoo.com
nslookup: Couldn't find server 'ns1.yahoo.com': Temporary failure in name resolution

This doesn't suprise me, since it won't be able to resolve the yahoo nameserver. But using the IP of ns1.yahoo.com does suprise me, because i would've thought that'd work.

nslookup www.google.com 66.218.71.63 Server: 66.218.71.63
Address: 66.218.71.63#53

Non-authoritative answer:
*** Can't find www.google.com: No answer

"Old Router" has this configuration:
Physical Address: 00-e0-98-4e-2f-43
IP Address: 10.0.0.2
Network Mask: 255.0.0.0
Default Gateway: 10.0.0.1
DNS IP Address: 10.0.0.1
DHCP Client: OFF

Does any of that help?
==========
STOP PRESS:
I just tried this:

nslookup www.google.com 10.0.0.1
Server: 10.0.0.1
Address: 10.0.0.1#53

Non-authoritative answer:
www.google.com canonical name = www.l.google.com.
Name: www.l.google.com
Address: 216.239.59.99
Name: www.l.google.com
Address: 216.239.59.103
Name: www.l.google.com
Address: 216.239.59.104
Name: www.l.google.com
Address: 216.239.59.147

That's an improvement. What i think i need to do is replace the 194.168.4.100 with 10.0.0.1, but i can't figure out where it's coming from.

Ahem, right, this is really embarrasing. I've been using /etc/resolve.conf, which i must've created by accident. I just noticed (at the bottom of this page) a similar thread which mentions /etc/resolv.conf. I must've created the one with an extra 'e' by mistake in all my hair pulling the other night.

*That's* where the 194.168.4.100 is coming from! I've changed that to 10.0.0.1 and am now resolving hostnames perfectly.

Sorry to have put you through this. I'm very new to linux. If someone hands me a gun i'll now go off and shoot myself. I think i just proved that thing about being blonde.

Thanks for all your help.

Good catch on the ns1.yahoo.com thing!!!



Happy surfing

Everyone seems to make that mistake once or twice. I have yet to figure out why libresolv is named such (and thus /etc/resolv.conf).

Would the 'E' really have killed the typing? :-P