dnsmasq caching

[Tubeta Taenang]

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

[Timothy White]

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

--
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 grase-hotspot+unsubscribe@grasehotspot.org.
To post to this group, send email to grase-...@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.

[Tubeta Taenang]

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

To view this discussion on the web visit https://groups.google.com/a/grasehotspot.org/d/msgid/grase-hotspot/CAESLx0LrBSXrnv5A5G1ByWNVg-Snd8E8Nc%2BLpb_U5xy7dh%2BYOQ%40mail.gmail.com.

[Timothy White]

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

To view this discussion on the web visit https://groups.google.com/a/grasehotspot.org/d/msgid/grase-hotspot/CAPYsbFaTqbkJJjwscRTQiDuqQGA0FxyyHJBbMqY%2BoX6JjHvjEw%40mail.gmail.com.

[Tubeta Taenang]

Hello Tim,

Thanks for your respond,

It is very interesting because according to the README file located within the /etc/dnsmasq.d/ folder, it says that the dnsmasq config files should be within the folder /etc/dnsmasq.d/, not the default /etc/dnsmasq.conf. So there is a bit confusion on my part.

And now you are telling me that the default dnsmasq.conf file should be the running config file. But this is very different in my case because every line of that file is commented out and I never though that this file was ever used at all.

On the other hand, /etc/dnsmasq.d/01.grasehotspot file get fed from the radmin web interface and it seems that those are the settings for dnsmasq.

Please correct me and explain further.

What about /etc/chilli/config file? And /etc/default/dnsmasq? Should I comment out the CONFIG_DIR directive within the /etc/default/dnsmasq file and use /etc/dnsmasq.conf file to configure dnsmasq?

I will need this clarifications from you before I will dive into it. Please help.

Thanks for your time and support.

Tubeta

To view this discussion on the web visit https://groups.google.com/a/grasehotspot.org/d/msgid/grase-hotspot/CAESLx0Jsftp-V5qTFjt-CMw5-xcfdY5Ebvn%3DRYtyVF2WyXtOOQ%40mail.gmail.com.

[Timothy White]

Hi Tubeta

Can you please collect support information (https://grasehotspot.org/support/collecting-support-information/) so I can get a better idea of your system, to ensure I give an accurate response. (Different versions do different things)

Regards

To view this discussion on the web visit https://groups.google.com/a/grasehotspot.org/d/msgid/grase-hotspot/CAPYsbFa0f7m0FBVQ31WN19CGrM5YH28C-tVLHzCbaPU9ykp8WQ%40mail.gmail.com.

[Tubeta Taenang]

Hello Tim,

Thanks for your help. This is what I have done:

1. I loggin into my grase via radmin admin account and get rid of all the reccursive dns ips and put the grase ip for my dns server. my client dns ip now becomes the grase dns ip and when i request pages from the internet, it works. So now I have verify that.

2. Second, I uncommended the /etc/chilli/ipup.sh iptable rule as you mentioned and let grase resolve dns queries. i don't know why they are commended out - those 2 iptables rules regarding dns queries.

So every thing works - just after you explained things to me.

So don't worry, if I have more difficulties, I will consult you and I know your time is very important for the all grase community.

I will leave it here and thank for the tips and explanations.

Have a great evening

Tubeta

To view this discussion on the web visit https://groups.google.com/a/grasehotspot.org/d/msgid/grase-hotspot/CAESLx0JT%2BKBrmfAZWwcMZ1ERji8vhO0RTrddhTbspx0RR2UjAA%40mail.gmail.com.