2017-06-26 - Re: [GRASE-Hotspot] dnsmasq caching

Header Data

From: Timothy White <ti***8@gmail.com>
Message Hash: 0eb20b162ff22a3c390b2f5835536969304c943ed344e73ca20b07d600101a7d
Message ID: <CAESLx0LrBSXrnv5A5G1ByWNVg-Snd8E8Nc+Lpb_U5xy7dh+YOQ@mail.gmail.com>
Reply To: <CAPYsbFamjPz2Dt+0zF5ajMenUcS7zWV6-PXmY5GWnT2nU_zEdw@mail.gmail.com>
UTC Datetime: 2017-06-26 23:41:53 UTC
Raw Date: Tue, 27 Jun 2017 16:41:53 +1000

Raw message 

Hi Tubeta

What are you trying to achieve? By default, the Grase Hotspot uses dnsmasq
for all client DNS, partially to allow special logoff urls to work, and
also to filter some DNS responses. As a side effect, you should already
have dnsmasq caching requests for you.

Regards

Tim

On Tue, Jun 27, 2017 at 7:00 AM, Tubeta Taenang <tu***g@gmail.com>
wrote:

> Hello Tim and members,
>
> I am strugling on configuring DNSMasq for caching and I will need help
> from any one of you who has made this work. After reading many posts, I get
> the understanding that there is no need to install BIND as a local name
> server for caching as dnsmasq is also part of grase.
>
> I will appreciate if you can drop me with guidelines on this.
>
> This is quite urgent.
>
> Thanks in advance
>
> Tubeta
>
> --
> This mailing list is for the Grase Hotspot Project http://grasehotspot.org
> ---
> You received this message because you are subscribed to the Google Groups
> "Grase Hotspot" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to gr***e@grasehotspot.org.
> To post to this group, send email to gr***t@grasehotspot.org.
> Visit this group at https://groups.google.com/a/
> grasehotspot.org/group/grase-hotspot/.
> To view this discussion on the web visit https://groups.google.com/a/
> grasehotspot.org/d/msgid/grase-hotspot/CAPYsbFamjPz2Dt%
> 2B0zF5ajMenUcS7zWV6-PXmY5GWnT2nU_zEdw%40mail.gmail.com
> <https://groups.google.com/a/grasehotspot.org/d/msgid/grase-hotspot/CAPYsbFamjPz2Dt%2B0zF5ajMenUcS7zWV6-PXmY5GWnT2nU_zEdw%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
>

Thread