dnsmasq and resolvconf
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ltsp (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
This is updated Ubuntu 12.04.
I use ltsp-server-
I have installed dnsmasq and followed this howtos:
https:/
http://
http://
Thin client boots very nicely, but there are no dns services:
root@lubuntu:~# cat /etc/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by
resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 127.0.0.1
I use one nic:
root@lubuntu:~# cat /etc/network/
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
auto eth0
iface eth0 inet static
address 192.168.100.10
netmask 255.255.255.0
network 192.168.100.0
broadcast 192.168.100.255
gateway 192.168.100.1
dns-nameservers 8.8.8.8 8.8.4.4
I can ping, but not with domain names:
root@lubuntu:~# ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_req=1 ttl=43 time=51.2 ms
root@lubuntu:~# ping google.com
ping: unknown host google.com
My base is filled:
root@lubuntu:~# cat /etc/resolvconf
nameserver 8.8.8.8
nameserver 8.8.4.4
How I make dns works in ltsp server with dnsmasq? I do not want go back
to use two nics and ltsp-server-
root@lubuntu:~# dpkg -l | grep dnsmasq
ii dnsmasq 2.59-4
Small caching DNS proxy and DHCP/TFTP server
ii dnsmasq-base 2.59-4
Small caching DNS proxy and DHCP/TFTP server
root@lubuntu:~# dpkg -l | grep resolvconf
ii resolvconf 1.63ubuntu9
name server information handler
Best Regards Asmo Koskinen.
Changed in ltsp (Ubuntu): | |
status: | New → Incomplete |
don't use base, that as far as I've understand is used only if nothing else is available. I've added my config in "tail" file.
dnsmasq hooks will at nameserver 127.0.0.1 "automagically" right after the content of the "head" file when creating /etc/resolv.conf, so you don't need to do it yourself (just restart dnsmasq everytime you want to regenerate /etc/resolv.conf for testing)