Hello,
We are trying to move from dhcpd + bind to dnsmasq for our small company.
On the test server, the dhcp provided by dnsmasq works properly, as the
internal dns who works better than we want : it's possible to ping the
machine's name given in the dnsmasq.conf, but also the machine's name
Am 26.08.2011 10:44, schrieb Jérémie SYLVAND:
Hello,
We are trying to move from dhcpd + bind to dnsmasq for our small company.
On the test server, the dhcp provided by dnsmasq works properly, as the
internal dns who works better than we want : it's possible to ping the
machine's name given
Hallo, Jérémie,
Du meintest am 26.08.11:
In the file resolv.conf:
search city.domain.com
nameserver 127.0.0.1
nameserver ISP 1 IP address1
nameserver ISP 1 IP address2
nameserver ISP 2 IP address1
nameserver ISP 2 IP address2
nameserver 127.0.0.1 seems to be ok - I use such a line on
Hello
Thank you for your answers.
I have tried what you told me, in different thing :
using resolv.conf with only 127.0.0.1
with 127.0.0.1 and one of my ISP nameserver
Not using resolv.conf by the line no-resolve in the dnsmasq.conf :
with and without this line : server=127.0.0.1
and with all
Am 26.08.2011 17:15, schrieb Jérémie SYLVAND:
Hello
Thank you for your answers.
I have tried what you told me, in different thing :
using resolv.conf with only 127.0.0.1
with 127.0.0.1 and one of my ISP nameserver
Not using resolv.conf by the line no-resolve in the dnsmasq.conf :
with
from the fedoraserver machine try
ping 89.2.0.1
traceroute 89.2.0.1
telnet 89.2.0.1 53
this should tell you if you at least have conectivity;
repeat with each upstream dns server IP address.
If your (r)syslog log level is set higher than the log-queries then they
will not make it to the
Dnsmasq 2.58 is done, it's available from the usual place
http://www.thekelleys.org.uk/dnsmasq/dnsmasq-2.58.tar.gz
and final changelog looks like this.
version 2.58
Provide a definition of the SA_SIZE macro where it's
missing. Fixes build failure on openBSD.