On Wed, Nov 16, 2005 at 09:23:05AM +, Simon Kelley wrote:
You need to provide a dhcp-range for the 10.x.x.x network in order for
DHCP to work. Since you don't want to allocate any addresses dynamically
on that network, the approriate incantation is
dhcp-range=10.0.0.6,static
(and
Hi,
I get occasional REFUSED responses from dnsmasq on a specific network, though
the query is actually successful. I am able to reproduce the error with
dnsmasq 2.22 on Debian Sarge and 2.23 on Debian Etch in this network.
However, i could not reproduce it with 2.23 on a different network. My
Holger Schletz wrote:
Hi,
I get occasional REFUSED responses from dnsmasq on a specific network, though
the query is actually successful. I am able to reproduce the error with
dnsmasq 2.22 on Debian Sarge and 2.23 on Debian Etch in this network.
However, i could not reproduce it with 2.23 on
Anssi Saari wrote:
On Wed, Nov 16, 2005 at 09:23:05AM +, Simon Kelley wrote:
You need to provide a dhcp-range for the 10.x.x.x network in order for
DHCP to work. Since you don't want to allocate any addresses dynamically
on that network, the approriate incantation is
Hi,
The reason why it happens like this is partly just history and inertia,
partly because I didn't want to risk the original requestor getting no
response at all, (and suffering a long timeout) when upstream servers
are returning error codes. However, this isn't the first time this has
Holger Schletz wrote:
Hi,
The reason why it happens like this is partly just history and inertia,
partly because I didn't want to risk the original requestor getting no
response at all, (and suffering a long timeout) when upstream servers
are returning error codes. However, this isn't the
Sorin Panca wrote:
Hello! I'm sorry about the delay.
Another test:
I did this:
A. rm /etc/hosts
B. zefir sorin # cat /etc/dnsmasq.conf
domain-needed
bogus-priv
no-resolv
filterwin2k
resolv-file=/etc/resolver
strict-order
address=/no.net/127.0.0.1
interface=eth1
interface=eth2
