Name resolution on client machine - how to get to work?

SliTaz Forum » English Support » Packages

Name resolution on client machine - how to get to work?

(11 posts) (3 voices)

Started 11 years ago by vboxer
Latest reply from vboxer
This topic is not a support question

Tags:

No tags yet.

vboxer

offline
Member

Hello everyone.

I have two SliTaz virtual machines configured exactly as described here:
http://forum.slitaz.org/topic/internet-connection-sharing/page/2#post-1335 , which makes things simpler to explain ;)

Don't think, their being virtual changes anything. Let's call them 'server' (the one w/ two adapters) and 'client'.

So, I set up IP forwarding on the server just as described in the post above and it kind of works, but something's still missing from the setup, b/c (I'm talking about the client machine here!) I can only ping internet hosts by IP address, but can't use their names. On the server everything works as intended - I mean, I can browse the web, ping the client etc. etc.

What gives?

Posted 11 years ago #
ernia

offline
Member

from the client can you ping 8.8.8.8 and 8.8.4.4 ?

Posted 11 years ago #
vboxer

offline
Member

Yes on both counts.

Posted 11 years ago #
mojo

offline
Key Master

If the client get's no response from a ping to http://www.slitaz.org you didn't setup udhcpcd for dynamic i.p. assignment on the server lan adapter the clients are connected to or your using static i.p. and didn't configure the clients adapter with DNS address.

tux@slitaz:~$ cat /etc/resolv.conf
nameserver 8.8.8.8
nameserver 8.8.4.4

Posted 11 years ago #
vboxer

offline
Member

Indeed, there was "nameserver 192.168.0.1", and when I replaced that with 8.8...., everything worked like a charm. But one problem remains - the change doesn't stick, and after reboot, I still get 192.168.0.1 in that config file.

Posted 11 years ago #
ernia

offline
Member
are you on rolling or 4.0?
as Mojo said you probably are not getting your client address from dhcp.
recently rolling has been modified to default to a fixed address if a dhcp lease has not been obtained, so if your network is 192.168.0.0/24 your client ip has defaulted to 192.168.0.6 and all seems to work well, except for the wrong dns entry in /etc/resolv.conf.
check if server's udhcpcd is listening on the right eth interface, if you want to be sure to obtain an address olny trough dhcp change /etc/network.conf
```
# Set IP address and netmask for a static IP.
IP="192.168.0.6"
NETMASK="255.255.255.0"
```
to an ip that does not belong to your network.
Posted 11 years ago #
mojo

offline
Key Master

# leafpad /etc/network.conf
DNS_SERVER="8.8.8.8 8.8.4.4"
File Save File Quit
# /etc/init.d/network.sh restart

Posted 11 years ago #
ernia

offline
Member

i was wrong with rolling mods, sorry. you probably are not using dhcp on client or server is misconfigured.
too much linux lately...

Posted 11 years ago #
vboxer

offline
Member

Well, I did the 'network.conf' fix on the client - with mixed results.
I do see "nameserver 8.8.8.8.8.8.4.4" in /etc/resolv.conf after reboot, but DNS still isn't working properly. Should I split "8.8.8.8.8.8.4.4" into two addresses as in resolv.conf?

So, ernia's suggestions apply to the server, right? "An ip that does not belong to my network" - which one? the 10 or the 192?

Posted 11 years ago #
mojo

offline
Key Master

Yes,it is two separate addresses with an empty space between them, 8.8.8.8 and 8.8.4.4:
/etc/network.conf
DNS_SERVER="8.8.8.8 8.8.4.4"

Posted 11 years ago #
vboxer

offline
Member

Yes!
Everything works as it should now.
Thank you very much guys for your patience, and apologies for my mix of network illiteracy and blindness.

Posted 11 years ago #

RSS feed for this topic

Reply

You must log in to post.