-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 20/03/15 13:49, Adrian Lewis wrote:
> Forgive me if I've not understood how dnsmasq works (still
> investigating) or if my terminology isn't quite correct but...
>
> 1. If a client requests a lookup for a-record.domain1.tld, 2.
> dnsmasq forwards t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The trick here it to understand that dnsmasq works in two different
modes, depending on where queries come from (or actually where they're
sent to).
auth-server=hosting.example.com,10.10.111.11
means that queries sent to 10.10.111.11 will be regarded
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 20/03/15 16:28, F32 wrote:
> Hi everyone, I'm a Chinese user with Internet access polluted by
> the GFW (the Great Firewall of China). To visit, e.g., the sites
> of Google, I have to setup a proxy and then redirect related
> packets to the proxy se
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hmm, from the BUGS section of the manpage for realpath:
The POSIX.1-2001 standard version of this function is broken by design,
since it is impossible to determine a suitable size for the output buf?
fer, resolved_path. According to POSIX.1-2001
Il 20/03/2015 15:05, Roy Marples ha scritto:
While that may compile, it surely won't work.
If O_CLOEXEC doesn't exist, then you need to set FD_CLOEXEC via fnctl(2)
It is just undefined, but it works.
My msg was just to notice that on some old uClibc realpath() crashes if
its second parameter
Hi everyone,
I'm a Chinese user with Internet access polluted by the GFW (the Great
Firewall of China). To visit, e.g., the sites of Google, I have to setup a
proxy and then redirect related packets to the proxy server at 127.0.0.1.
Currently, I configure something like the follow
On 20/03/2015 12:49, Alfonso Ranieri wrote:
> Il 20/03/2015 00:42, Simon Kelley ha scritto:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> I want to start the release-process towards 2.73. There's a whole heap
>> of good stuff since 2.72, and good reasons to get it out there before
>> pr
Forgive me if I've not understood how dnsmasq works (still investigating)
or if my terminology isn't quite correct but...
1. If a client requests a lookup for a-record.domain1.tld,
2. dnsmasq forwards the lookup and receives a DNAME record as the answer
saying domain1.tld is a DNAME for domain2.tl
Il 20/03/2015 00:42, Simon Kelley ha scritto:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I want to start the release-process towards 2.73. There's a whole heap
of good stuff since 2.72, and good reasons to get it out there before
proceeding further with stuff that's in progress.
Please test
Hi folks,
Question: Can I use the same dnsmasq as an authoritative
DNServer as well as a forwarder for external queries?
No DHCP, but static tables in /etc/hosts and /etc/ethers.
dnsmasq is version 2.72
Here is my configuration:
domain-needed
bogus-priv
no-resolv
server=8.8.4.4
all-servers
aut
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
So, are you saying the a configuration which works with 2.52 fails
with 2.73test1. If that is trye, could you send a copy of the
configuration that fails. You can send it either to the list, or reply
to me directly.
Cheers,
Simon.
On 19/03/15 09:5
11 matches
Mail list logo
