I've just tagged 2.69test8, which has some significant fixes to the
DNSSEC code.
One thing to note: I've also completely changed the way the trust
anchors are specified, from DNSKEYS to DS records. If you're using the
trust-anchors.conf file I supply, this should be transparent, but if you
On 09/02/14 00:34, Elsie Buck wrote:
I just ran across
http://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2014q1/008009.html
which is exactly what I want to do at my home. Why you ask? Well, I have
5 computers (one for each room), 2 file servers, 2 media players and 2
laptops. Not real
One thing to note: I've also completely changed the way the trust
anchors are specified, from DNSKEYS to DS records.
Very nice and, yes, it works. :)
All that's left is to find a way to obtain those securely when dnsmasq
starts up, somewhat in the way unbound-anchor(1) from Unbound does.
On 08/02/14 17:42, Linux Luser wrote:
dhcp-ignore-clid might just work for the long-term. But I ended up
playing around a bit more and I've managed to isolate the part of my
config that I believe triggers the problem. Maybe this can be fixed
without a dhcp-ignore-clid option?
When I set a
On 11/02/14 12:10, Jan-Piet Mens wrote:
One thing to note: I've also completely changed the way the trust
anchors are specified, from DNSKEYS to DS records.
Very nice and, yes, it works. :)
All that's left
I wish, I wish. NSEC3 is still lurking.
is to find a way to obtain those securely
Is unbound-anchor fairly stand-alone? Maybe run unbound-anchor and
then covert the format of the resulting trust-anchors file would be
a viable solution?
Fairly, yes, but: if people can run unbound-anchor they have Unbound, so
what would be the point of dnsmasq as a validator? ;-)
-JP
I have a few entries in my dnsmasq.conf file to block some tracking
sites, as follows:-
address=/www.addthis.com/127.0.0.1
address=/googlesyndication.com/127.0.0.1
address=/google-analytics.com/127.0.0.1
address=/googleadservices.com/127.0.0.1
Is there any way to get additonal debugging information out of dnsmasq?
I'm running into an issue where I'm seeing 'DHCPDISCOVER(eth0) X Y no
address available', but it's not particularly clear to me why this is
happening. Is there a way to log the contents of the DISCOVER packet?
I know I
On 11/02/14 15:12, Brian Rak wrote:
Is there any way to get additonal debugging information out of dnsmasq?
I'm running into an issue where I'm seeing 'DHCPDISCOVER(eth0) X Y no
address available', but it's not particularly clear to me why this is
happening. Is there a way to log the contents
Sorry, should have mentioned that I already have that enabled.
That gives me some extra info:
Feb 11 11:14:07 x dnsmasq-dhcp[2278]: 3227716451 DHCPDISCOVER(eth0)
00:25:90:d6:ac:25 no address available
Feb 11 11:14:08 x dnsmasq-dhcp[2278]: 467005255 available DHCP range:
10.x.10 -- 10.x.250
That makes sense. I may just do that. Since /etc/ethers and
/etc/dnsmasq-hosts.d would both be reread upon a SIGHUP signal, it seems
that there wouldn't be much of a difference either way, other than, as you
say, one way is more confusing than another.
Thanks again!
On Feb 11, 2014 5:36 AM, Simon
On 11/02/14 22:21, B. Cook wrote:
It seems that as of 2.68 the proper way to do a cname entry is to have
the entry in the format of:
(man page..)
cname=cname,target
Is would seem that a target of ghs.googlehosted.com could not be
properly satisfied at this time.
From the man page
There
I haven't tried it, but maybe 127.0.0.2 will do the trick.
On Feb 11, 2014 4:40 PM, Chris Green c...@isbd.net wrote:
I have a few entries in my dnsmasq.conf file to block some tracking
sites, as follows:-
address=/www.addthis.com/127.0.0.1
address=/googlesyndication.com/127.0.0.1
13 matches
Mail list logo
