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

Header Data

From: Timothy White <ti***8@gmail.com>
Message Hash: 005e86c05c8ced80e1b318596533ac6ce8d79d03203a711ae699a33a1bf664c6
Message ID: <CAESLx0Jsftp-V5qTFjt-CMw5-xcfdY5Ebvn=RYtyVF2WyXtOOQ@mail.gmail.com>
Reply To: <CAPYsbFaTqbkJJjwscRTQiDuqQGA0FxyyHJBbMqY+oX6JjHvjEw@mail.gmail.com>
UTC Datetime: 2017-06-27 18:32:01 UTC
Raw Date: Wed, 28 Jun 2017 11:32:01 +1000

Raw message 

Hi Tubeta

You'll need to verify that a client that connects is given the hotspot IP
as it's DNS address. It should be assigned by DHCP.
Secondly, dnsmasq should be using the DNS server set in the Grase Hotspot
config, not your ISPs DNS server unless that is what you have set.

By default, dig on the Grase server will probably use your ISP DNS servers,
because the server itself isn't forced through dnsmasq. However all clients
should be using dnsmasq.

You may want to turn on log-queries in dnsmasq, to verify that client
requests are hitting dnsmasq.

Also, by default cache-size is 150, so if it's absent, it should be caching
up to 150 names, your change will make it cache up to 1000 names.

/etc/dnsmasq.d/01-grasehotspot is only for extra stuff we add. The rest is
a default dnsmasq config, which in a default install caches. Look
in /etc/dnsmasq.conf for other settings.

Regards

Tim

On Wed, Jun 28, 2017 at 8:38 AM, Tubeta Taenang <tu***g@gmail.com>
wrote:

> Hello Tim,
>
> Sadly that is not working for this box. All DNS queries are answered by my
> ISP DNS servers and I have verified that using dig. For your information I
> didn't set up this grase box and I am new to grase as well.
>
> So I need your help on this. My ISP (Speed Cast) reported that my traffic
> is congested mostly by DNS queries.
>
> Now what I want to do is to make grase to do caching. The reference script
> in /etc/dnsmasq.d/01-grasehotspot doesn't show me that it does caching. So
> I have added another script (02.grasehotspot-caching) in the same directory
> which contains only one line:
>
>           cache-size = 1000
>
> But I think it doesn't do anything at all.
>
> Can you tell me how can I verify that my grase is doing caching for all
> DNS queries and act as a local DNS server for my network?
>
> Please help
>
> Thanks
> Tubeta
>
> On Tue, Jun 27, 2017 at 6:41 PM, Timothy White <ti***8@gmail.com>
> wrote:
>
>> 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/gr
>>> asehotspot.org/group/grase-hotspot/.
>>> To view this discussion on the web visit https://groups.google.com/a/gr
>>> asehotspot.org/d/msgid/grase-hotspot/CAPYsbFamjPz2Dt%2B0zF5a
>>> jMenUcS7zWV6-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>
>>> .
>>>
>>
>> --
>> 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/gr
>> asehotspot.org/group/grase-hotspot/.
>> To view this discussion on the web visit https://groups.google.com/a/gr
>> asehotspot.org/d/msgid/grase-hotspot/CAESLx0LrBSXrnv5A5G1By
>> WNVg-Snd8E8Nc%2BLpb_U5xy7dh%2BYOQ%40mail.gmail.com
>> <https://groups.google.com/a/grasehotspot.org/d/msgid/grase-hotspot/CAESLx0LrBSXrnv5A5G1ByWNVg-Snd8E8Nc%2BLpb_U5xy7dh%2BYOQ%40mail.gmail.com?utm_medium=email&utm_source=footer>
>> .
>>
>
> --
> 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/CAPYsbFaTqbkJJjwscRTQiDuqQGA0F
> xyyHJBbMqY%2BoX6JjHvjEw%40mail.gmail.com
> <https://groups.google.com/a/grasehotspot.org/d/msgid/grase-hotspot/CAPYsbFaTqbkJJjwscRTQiDuqQGA0FxyyHJBbMqY%2BoX6JjHvjEw%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
>

Thread