Hostnames not being resolved - Hardware & Software

I've already exhausted [url=http://xkcd.com/627/]the flowchart[/url]. I'm using Ubunto 9.04. If I use DHCP, everything works fine except I don't have a static IP. If I use the network manager to set a static IP, the computer boots with the DHCP configuration. Since the computer has no monitor on it, it is painful to set it back to the configuration I want. Google'd the fuck out of it to no avail, apparently, you can't set the default connection type. So, I used the kludge involving /etc/network/interfaces: [code] auto lo iface lo inet loopback auto eth0 iface eth0 inet static address 192.168.1.38 netmask 255.255.255.0 network 192.168.100.1 broadcast 192.168.1.255 gateway 192.168.1.1 [/code] Side question: what the hell is network, I assumed modem IP? Now, internet works, static IP and everything, but no resolving of hostnames. So, I used the /etc/dhcp3/dhclient.conf prepend kludge [code] -snip- #prepend domain-name-servers 127.0.0.1; prepend domain-name-servers 68.111.16.30, 68.111.16.25, 68.1.208.30; -snip- [/code] Now resolv.conf looks like this [code] search com nameserver 68.111.16.30 nameserver 68.111.16.25 nameserver 68.1.208.30 [/code] ...but still, hostnames are not being resolved. [b]Update:[/b] Don't know what happened, but it is working now

Well [I]of course[/I] you aren't going to get a static ip with DHCP. What did you think DHCP did? I don't know what 'network' is, I've never had to set it. Try commenting it out and seeing what happens. You probably had to restart the interface in order for the nameservers to get loaded again. Usually, that is something that DHCP takes care of, but when you are not using that, you kind of need to specify a reliable nameserver. If all else fails, you can just use your gateway as the nameserver, since that will probably just inductively query its own internal list of nameservers.

I'm pretty sure you can just use DHCP and then lock a certain ip to your MAC address through your router. I do that at least, works fine.

That's called a DHCP reservation, but the IP is still assigned through the DHCP daemon.

That's all server-side, though.

And it wouldn't really make a difference, and is a whole lot easier if you have a decent router.

network is probably the network address. In your case it would be 192.168.1.0 if your IP is 192.168.1.38/24. It probably works since it discards the last part cause of your mask.

[QUOTE=Night-Eagle;16953659]I've already exhausted [url=http://xkcd.com/627/]the flowchart[/url].[/QUOTE] If you've exhausted the flowchart already, we can't help you at all. Ask someone else for help :(

In your kludged /etc/network/interfaces: [code]network 192.168.100.1[/code] I'm pretty sure that's meant to be [code]network 192.168.1.0[/code] Don't ask me why - it seems to be the opposite of the broadcast address. It seems to serve some purpose, though. I had to give a bunch of servers in a LAN static IPs and they worked fine once I'd set the right network. Just try it, see if it works. If it does, please explain to me why it does ;p 'cause I have no idea.

Depends on router, if that doesn't work try 192.168.0.1

[QUOTE=KrAzY_nikomo;17009995]Depends on router, if that doesn't work try 192.168.0.1[/QUOTE] That's not his network address.