, if not using separate
processes (or machines) altogether.
IWFM, and I'm happy with it.
--
Offlist mail to this address is discarded unless
/dev/rob0 or not-spam is in Subject: header
is your
problem. Although I have it on good authority that 2.6.19 is perfect,
and any problems with it are your own %*^$*! fault. Linus said so. :)
--
Offlist mail to this address is discarded unless
/dev/rob0 or not-spam is in Subject: header
a different niche. I think it should stay that way.
[1] With apologies to Chuck Barris and his horrible/wonderful The Gong
Show. Apologies also to anyone [un]fortunate enough to remember it. :)
--
Offlist mail to this address is discarded unless
/dev/rob0 or not-spam is in Subject
?
--
Offlist mail to this address is discarded unless
/dev/rob0 or not-spam is in Subject: header
-getopt no-ISC-leasefile no-DBus I18N TFTP
and DiG 9.4.1-P1 soa google.com. works for me.
--
Offlist mail to this address is discarded unless
/dev/rob0 or not-spam is in Subject: header
complexity, because the whole point of using dnsmasq in the
first place was for simplicity. :)
--
Offlist mail to this address is discarded unless
/dev/rob0 or not-spam is in Subject: header
own named backend for recursion. It
binds on port 35, which is used as such in dnsmasq.conf :
server=127.0.0.1#35
--
Offlist mail to this address is discarded unless
/dev/rob0 or not-spam is in Subject: header
inside your RFC 1918
netblocks, I would suggest a physical approach: pull the plug on it.
--
Offlist mail to this address is discarded unless
/dev/rob0 or not-spam is in Subject: header
, but it's in the Google cache.
(Dynamic IP, I think it will be back later.)
--
Offlist mail to this address is discarded unless
/dev/rob0 or not-spam is in Subject: header
a x86_64
version.
--
Offlist mail to this address is discarded unless
/dev/rob0 or not-spam is in Subject: header
to drop nslookup.
** server can't find xxx.x: NXDOMAIN
when i look at the dnsmasq log, and the dnsmasq.leases file,
everything seems to be ok...
You looked, and at the time, xxx was in the lease file? I bet it
wasn't.
--
Offlist mail to this address is discarded unless
/dev/rob0
unless
/dev/rob0 or not-spam is in Subject: header
/dev/rob0 or not-spam is in Subject: header
upstream servers.
On Tuesday 04 May 2010 01:43 PM, /dev/rob0 wrote:
Show what Kerberos is actually looking up. Is it as you said,
_kerberos-master.udp.EXAMPLE.COM, or is is perhaps as per the
documented LDAP example, _kerberos-master._udp.EXAMPLE.COM?
I do not understand the difference
to this address is discarded unless
/dev/rob0 or not-spam is in Subject: header
/dev/rob0 or not-spam is in Subject: header
On Thu, Jun 24, 2010 at 09:32:01PM +0200, clemens fischer wrote:
/dev/rob0 wrote:
On Thu, Jun 24, 2010 at 09:51:57AM +0100, Alberto Cuesta-Canada wrote:
are there any plans of implementing Dynamic DNS for dnsmasq?
There is a perl script that adds that functionality here:
http
the interfaces IP
address as used). What happens to the dhcp-range that does not
include one of the interfaces ip addresses?
I don't know, but I would expect it to be logged as an error.
--
Offlist mail to this address is discarded unless
/dev/rob0 or not-spam is in Subject: header
information would be required, to help you.
--
Offlist mail to this address is discarded unless
/dev/rob0 or not-spam is in Subject: header
subject to DHCP
leases.
I don't know how multiple hosts listings for the same IP address are
handled by dnsmasq, but I'll bet it's in the [very] fine manual. :)
--
Offlist mail to this address is discarded unless
/dev/rob0 or not-spam is in Subject: header
On Wed, Apr 13, 2011 at 10:25:55PM +0530, Mohit Chawla wrote:
On Wed, Apr 13, 2011 at 9:25 PM, /dev/rob0 r...@gmx.co.uk wrote:
The hosts(5) file format is far simpler than a DNS zone file or a
dnsmasq(8) config file. IP.add.re.ss name [alias ...]. dnsmasq
assumes that the presence
, and no forwarding
will be done. So if no IP is specified, they are NXDOMAIN.
--
Offlist mail to this address is discarded unless
/dev/rob0 or not-spam is in Subject: header
to a MAC.
Sure, someone can look it up and find out what kind of NIC or
embedded device you bought. But no, I don't see a serious privacy
concern here. Am I missing something, or are you?
--
Offlist mail to this address is discarded unless
/dev/rob0 or not-spam is in Subject: header
relevant?
I think resolvconf is a Debian-specific package. It is not a
part of dnsmasq, and thus this list is not the best place from
which to seek support for it.
I would suggest Google and Ubuntu help forums.
--
Offlist mail to this address is discarded unless
/dev/rob0 or not-spam
/as/
was helpful in my project back in '05 or so. OpenDNS implements a
domain blocking feature as well. http://www.malwaredomains.com/ may
also be of interest.
--
Offlist mail to this address is discarded unless
/dev/rob0 or not-spam is in Subject: header
, perhaps this warrants a major
release, i.e., 3.0? :)
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if /dev/rob0 is in the Subject:
___
Dnsmasq-discuss mailing list
Dnsmasq-discuss
IPs per PTR.
You CAN have as many PTR records as you want on any name. However,
it's unlikely to do anything useful.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if /dev/rob0 is in the Subject
On Thu, Mar 15, 2012 at 03:14:08PM -0500,
richardvo...@gmail.com wrote:
On Thu, Mar 15, 2012 at 2:34 PM, /dev/rob0 r...@gmx.co.uk wrote:
On Thu, Mar 15, 2012 at 10:24:44AM -0700, Rob Zwissler wrote:
Yah, seems to me it would make more sense to key off the IP
address (or have
://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if /dev/rob0 is in the Subject:
___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq
://sqlite.org/
I'm not sure how/if this would help with the goal of failover, but
I think it might be worth considering if there is to be external
database/storage for dnsmasq.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if /dev/rob0
and consulting
Offlist GMX mail is seen only if /dev/rob0 is in the Subject:
___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
and consulting
Offlist GMX mail is seen only if /dev/rob0 is in the Subject:
___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
the
request came from.
What's the proper way to setup this up?
See -y, --localise-queries in the dnsmasq(8) manual.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if /dev/rob0 is in the Subject
page.
in /etc/dnsmasq.conf :
dhcp=host=00:11:22:33:44:55,myhost
address=/myhost/1.2.3.4
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if /dev/rob0 is in the Subject:
___
Dnsmasq-discuss mailing list
. dnscache does not support DNSSEC
signature verification, does it? Is anybody hacking on it since its
abandonment?
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if /dev/rob0 is in the Subject
not be a good choice
for your internal domain. That said, it was chosen to be easy to
block, because many sites will want to do that.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if /dev/rob0 is in the Subject
On Thu, Aug 23, 2012 at 11:41:17AM -0400, Gene Czarcinski wrote:
On 08/23/2012 10:44 AM, /dev/rob0 wrote:
On Thu, Aug 23, 2012 at 10:26:25AM -0400, Gene Czarcinski wrote:
I checked my dnsmasq.conf and I have local=/xxx/, domain xxx,
XXX is a valid top-level domain, so it might not be a good
offers.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if /dev/rob0 is in the Subject:
___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
http://lists.thekelleys.org.uk/mailman
On Tue, Oct 23, 2012 at 06:49:19AM -0600, dnsm...@ailsby.net wrote:
On 12-10-22 10:32 PM, /dev/rob0 wrote:
On Mon, Oct 22, 2012 at 09:24:34PM -0600, dnsm...@ailsby.net wrote:
I am trying to setup dnsmasq so that I can use the OpenDNS
servers for my younger children, and then have all other
administration and consulting
Offlist GMX mail is seen only if /dev/rob0 is in the Subject:
___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
On 10/11/2012 15:54, /dev/rob0 wrote:
Seems to me that dnsmasq is a better nscd replacement, and
it has a place in mobile computing.
# we use this dnsmasq as this system's own resolver
no-resolv
On Sat, Nov 10, 2012 at 05:46:10PM -0600,
richardvo...@gmail.com wrote:
no-resolv is doing
On Tue, Nov 13, 2012 at 12:13:07PM +0100, s...@sltosis.org wrote:
On Mon, Nov 12, 2012 at 06:11:43PM -0600, richardvo...@gmail.com
wrote:
On Sun, Nov 11, 2012 at 5:05 PM, /dev/rob0 r...@gmx.co.uk
wrote:
On 10/11/2012 15:54, /dev/rob0 wrote:
Seems to me that dnsmasq is a better nscd
On Tue, Nov 13, 2012 at 09:42:34PM +, Ed W wrote:
On 13/11/2012 15:03, /dev/rob0 wrote:
And dhcpcd(8) is writing domain_name_servers to
/var/lib/dhcpcd/resolv.conf.
How do you remove servers from that file when the link goes down?
Why would I care? If I have no connection, nothing
is something
similar to this:
server=/example.dht/127.0.0.1#1053
This uses 127.0.0.1:1053 for names under and including only
example.dht.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if /dev/rob0 is in the Subject
to a remote server for those names:
server=/certain.sites.example/2001:db8::1ce:c01d
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if /dev/rob0 is in the Subject:
___
Dnsmasq-discuss mailing list
:
server=/github.example.com/192.168.0.2
Do this in addition to server=192.168.0.2 if 192.168.0.2 should
also be providing resolver service for you.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if /dev/rob0 is in the Subject
.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if /dev/rob0 is in the Subject:
___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
http://lists.thekelleys.org.uk/mailman/listinfo
/udp closedsqlnet
67/udp open|filtered dhcps
68/udp closeddhcpc
Nmap done: 1 IP address (1 host up) scanned in 1.36 seconds
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if /dev/rob0 is in the Subject
prominent warning if the
dangerous combination is configured.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if /dev/rob0 is in the Subject:
___
Dnsmasq-discuss mailing list
Dnsmasq-discuss
. But it is a convenience for some small,
internal-only sites, where that might override security concerns.)
Just for interest.
--
http://rob0.nodns4.us/
Offlist GMX mail is seen only if /dev/rob0 is in the Subject:
___
Dnsmasq-discuss mailing
considered these concerns.
--
http://rob0.nodns4.us/
Offlist GMX mail is seen only if /dev/rob0 is in the Subject:
___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
BIND them.
:)
--
http://rob0.nodns4.us/
Offlist GMX mail is seen only if /dev/rob0 is in the Subject:
___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
only
point out what I, as a user, think about it. I'll trust Simon's
judgment, but I hope he has considered these concerns.
--
http://rob0.nodns4.us/
Offlist GMX mail is seen only if /dev/rob0 is in the Subject:
___
Dnsmasq-discuss mailing list
to get it right
there, either. I would look at -m recent and maybe also -m set to
begin with.
--
http://rob0.nodns4.us/
Offlist GMX mail is seen only if /dev/rob0 is in the Subject:
___
Dnsmasq-discuss mailing list
Dnsmasq-discuss
not technically
possible, even with the features I described. (Well, the DNS
hijacking might come close, but a malicious rulebreaker could use
IP addresses.)
--
http://rob0.nodns4.us/
Offlist GMX mail is seen only if /dev/rob0 is in the Subject
. If it could, it
wouldn't be so simple to use. :)
Don't be afraid of BIND. While it is very powerful, it's also
straightforward, well documented, and well supported.
--
http://rob0.nodns4.us/
Offlist GMX mail is seen only if /dev/rob0 is in the Subject
/
Offlist GMX mail is seen only if /dev/rob0 is in the Subject:
___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
, that's what
dnsmasq will tell the client.
So, will the Dnsmasq reply to the client's request from cache if
none of the external servers replied?
No, it wasn't cached.
--
http://rob0.nodns4.us/
Offlist GMX mail is seen only if /dev/rob0 is in the Subject
forwarders { 8.8.8.8; };
};
view four {
match-clients { four; };
forwarders { 8.8.4.4; };
};
--
http://rob0.nodns4.us/
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
___
Dnsmasq-discuss mailing list
Dnsmasq
S packaging system.
Consult Ubuntu documentation for help with these issues.
--
http://rob0.nodns4.us/
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
t;; };
...
};
...
...where the "in-addr.arpa" zone file has only SOA and NS with no
other records such as PTR.
--
http://rob0.nodns4.us/
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
__
y to turn this response into an NXDOMAIN instead of returning the
> synthesized A record?
>
> I'm using dnsmasq verision 2.66 on a Centos 7 machine.
--
http://rob0.nodns4.us/
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
_
ith
another possible point of failure: mysql or PostgreSQL.)
--
http://rob0.nodns4.us/
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
http://lists.the
on port:
>
> $ dig -p 1234 192.168.0.1
> ...
> ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 61710
> ...
Here without the -x the query is for an A record for "192.168.0.1."
in the "1" top-level domain.
--
http://rob0.nodns4.us/
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
e
better off just using 8.8.8.8 and dumping the broken one?
I've said before what I do ... I have *both* dnsmasq and named
running; dnsmasq on port 53 and named on 127.0.0.1:1035. The named
is doing recursion only. Yes, I'm hard core. :)
--
http://rob0.nodns4.us/
Offl
already have it
fixed, my version is not current.)
--
http://rob0.nodns4.us/
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
gt;
> You're welcome. :)
And a very good job on your part for trying to help. Unfortunately
this matter feels very much like an "XY" problem: "I want to do X, I
think Y would do it for me, so I am asking how to do Y." As is
common in such cases, "Y" makes littl
monitoring the service for spikes
and other attack indicators.
Dnsmasq is a wonderful piece of software which does a very nice job
at meeting the needs of most small, simple sites. I do not think
it's well suited for ISP use, and especially not for use as an open
resolver.
ress to only one client.
But wait and see what Simon says. :)
--
http://rob0.nodns4.us/
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
is fixed by accepting /32 and /0 CIDR
> prefixes as valid values. Any other value will still be
> considered the same as /16.
A /0 zone is very strange and likely to break most reverse address
resolution, but a /32 zone is not unusual at all; I run 8 /32
in-addr.arpa zones for my /29 net
ave is when one of the actual upstream
recursive servers replies for "domain.example" with incorrect data.
(Side note: simple is good; listing more recursive servers will
generally not improve performance. If some of the servers you're
lis
on why you might want to consider
these ISP nameservers unreliable.
> does anybody knows the reason for this?
See --all-servers and --server in the manual.
--
http://rob0.nodns4.us/
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
exists. Some resolvers are fooled and will go along
with it, but apparently dnsmasq can't do that while checking DNSSEC.
If you are paying them, complain.
--
http://rob0.nodns4.us/
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
unctionality is not currently readily
> available within OpenWRT, but could be made available by extending
> Dnsmasq, any of you on the list would be keen to implement that
> functionality (Simon Kelley, maybe?), or to donate funds towards
> such an effort.
--
http://rob0.nodns4.us/
t thing for dnsmasq to do on SERVFAIL is to
attempt the query with other upstream servers, if possible. But an
answer needs to be provided to the client before its own timeout
value.
--
http://rob0.nodns4.us/
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
ce, I'm able
> to get the EDNS0 option in a dns query but when I compiled from the
> source and ran it, the same thing doesn't happen.
--
http://rob0.nodns4.us/
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
___
Dnsmas
it.
ISC dhcpd uses raw sockets, and those are (like tcpdump) seen before
the netfilter subsystem.
But note, a complete DHCP exchange is "DORA": Discover by the client;
Offer by the server; Request by the client; and Ack by the server.
With dhcpd only DO are not blockable. RA certai
ache-size=0
> --conf-file=/dev/null
> --proxy-dnssec
> --enable-dbus=org.freedesktop.NetworkManager.dnsmasq
> --conf-dir=/etc/NetworkManager/dnsmasq.d
Did you ever show us the contents of this --conf-dir? It could have
a file with "query-port".
--
o
have local name resolution and to have one central cache for external
names.
Yes, there is an option you can use in dnsmasq.conf to change the
nameserver[s] given to DHCP clients, but why do you want that? See
the dnsmasq(8) manual for details.
--
http://r
ept. In fact
you can keep it simple as in my howto, with static entries for the
various remote sites. If one of the sites is unreachable via the
VPN, no problem if those names fail to resolve.
--
http://rob0.nodns4.us/
Offlist GMX mail is seen only if &q
80 matches
Mail list logo
