2016-01-12 - Re: dmasq problem

Header Data

From: tadzio skowroński <ta***3@gmail.com>
Message Hash: 7ddf23f8fa08445ed4af943c6b18c6839c6e42bad446032825edea0a7a1873c4
Message ID: <b8b8cbe1-42bd-4bcb-951f-383d22b0d89b@grasehotspot.org>
Reply To: <37204a3c-e358-493a-b453-a936a5f1a1aa@grasehotspot.org>
UTC Datetime: 2016-01-12 05:31:19 UTC
Raw Date: Tue, 12 Jan 2016 04:31:19 -0800

Raw message 

dnsmsq config file is being overwritten with cron so original problem is 
reccuring. 
i've tried leaving just one dns server in panel but this does not seems to 
work.

only working method is commenting out strictorder line and removing 
grase-conf-dnsmasq
from cron.

W dniu wtorek, 12 stycznia 2016 13:00:25 UTC+1 użytkownik tadzio skowroński 
napisał:
>
> okay for now it seems, that commenting out strict-order is a workaround 
> for this issue
>
> however i still do not know what is actually wrong with configs.
>
> W dniu wtorek, 12 stycznia 2016 12:31:45 UTC+1 użytkownik tadzio 
> skowroński napisał:
>>
>> hi, 
>>
>> i'm encountering problem with dns resolving probably due to dnsmasq
>> malfunction. 
>>
>> resolving names works only shortly after restarting dnsmasq service, and 
>> just after 
>> few seconds problem occures again - however strange part is that names 
>> are resolved but i takes time. 
>>
>> for instance simple ping of debian.org reaches IP only with 1500 timeout 
>> set. 
>>
>> however dig @localhost debian.org returns proper ip immediately
>>
>> any ideas how to troubleshot the issue? grase is installed on ubuntu 14.04
>> dnsmasq config:
>>
>> #chilli_lanip 10.1.0.1
>> #chilli_wanif p4p1
>> #chilli_lanif p1p1
>> #chilli_network 10.1.0.0
>> #chilli_netmask 255.255.255.0
>>
>> address=/grasehotspot.lan/10.1.0.1
>> address=/logout/1.0.0.0
>> address=/logoff/1.0.0.0
>>
>> no-resolv
>> strict-order
>>
>> expand-hosts
>> domain=hotspot.lan
>> server=8.8.8.8
>> server=8.8.4.4
>>
>>

Thread