Hi Simon,
Can you tell me if `dhcp_release eth1 ip mac` is still needed after send
SIGHUP, or why `dhcp_release eth1 ip mac` can't release the binding without
send SIGHUP?
BTW, I am not using openstack. Sorry for the confusion.
Thanks,
Yongkang
On Mon, Feb 16, 2015 at 1:23 PM, Yongkang You
wro
On Mon, Feb 16, 2015 at 6:49 AM, Simon Kelley
wrote:
> The current code doesn't do anything when a file is deleted. To make
> that have an affect, you're back to sending SIGHUP to clean out the
> data and re-read the current set of files.
>
Okay.
>
> I'm pretty sure I mentioned that way back.
Thank you, Simon.
I see what you mean. As I mentioned earlier I have an internal network with two
DNS servers which ARE authoritative for the domain I use. It will be great if I
can make them recursive, but in this case their logs will be full of warnings
that they couldn't reach particular DNS
That makes perfect sense... So I added the tag:!vmware to the other range
and while it took several reboots and dhcp refreshes on the XP VM it did
finally take.
Thanks!
Matt
On Sun, Feb 15, 2015 at 4:59 PM, Simon Kelley
wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> The client
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 15/02/15 06:15, Yongkang You wrote:
> On Sun, Feb 15, 2015 at 4:11 AM, Simon Kelley
> wrote:
>
>> Got it. Do you have --no-hosts set? That would explain why it
>> was working for me and not for you.
>>
>> I just pushed the fix to git.
>>
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
The client is asking for 10.1.10.104 since it used it at sometime in
the past. Dnsmasq gives it what it asks for, since the unqualified
dhcp-range allows that address. If dnsmasq was allocating an address
from scratch, it would use the 10.1.10.50,10.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
The risk with this is if you forward a query to a non-recursive
nameserver that it _isn't_ authoritative for. In that case you'll get
a referal - ie a reply packet with an empty answer section, but one or
more DNS servers in the authority section.
R
I'm running dnsmasq 2.72 on my Gentoo box and I feel like I'm missing
something obvious.
I have the following lines in my dnsmasq.conf
dhcp-mac=set:vmware,00:0C:29:*:*:*
dhcp-range=10.1.10.100,10.1.10.139,255.255.255.0,6h
dhcp-range=tag:vmware,10.1.10.50,10.1.10.59,255.255.255.0,6h
And
This question is for maintainers of Dnsmasq
I want to consult you if the attached patch is safe.
I am trying to develop a workaround for this:
/* Don't put stuff from a truncated packet into the cache.
Don't cache replies from non-recursive nameservers, since we may get a
reply containing a CNAM
Thanks, I see.
On Sun, Feb 15, 2015 at 7:39 PM, Chen Wei wrote:
> On Sun, Feb 15, 2015 at 06:48:15PM +0800, zhiwei wrote:
>> I don't know how to set 'abc.com to 1.1.1.1'
>> and '*.abc.com to 1.1.1.2'.
>> (set address=/abc.com/1.1.1.1 and address=/.abc.com/1.1.1.2 in
>> configure file did not work
On Sun, Feb 15, 2015 at 06:48:15PM +0800, zhiwei wrote:
> I don't know how to set 'abc.com to 1.1.1.1'
> and '*.abc.com to 1.1.1.2'.
> (set address=/abc.com/1.1.1.1 and address=/.abc.com/1.1.1.2 in
> configure file did not work)
/abc.com/ is equal to /.abc.com/, at least it applies to --server,
--
Valgrind reports three leaks. Those unfreed pointers are only used during
loading.
---
src/dnsmasq.c |2 ++
src/option.c | 11 +--
2 files changed, 11 insertions(+), 2 deletions(-)
diff --git a/src/dnsmasq.c b/src/dnsmasq.c
index e903a24..e6dabbf 100644
--- a/src/dnsmasq.c
+++ b/s
Hi,
I used dnsmasq in recent days, it's great.
I came across an issue, I don't know how to set 'abc.com to 1.1.1.1'
and '*.abc.com to 1.1.1.2'.
(set address=/abc.com/1.1.1.1 and address=/.abc.com/1.1.1.2 in
configure file did not work)
Is dnsmasq support to configure this rule? Or can anyone tel
13 matches
Mail list logo
