[Dnsmasq-discuss] About 127.0.0.1 in resolv.conf [WAS: Web hang ups after repeated access to one site - dnsmasq related?]

[Hugo Heden]

On Tue, Feb 17, 2009 at 9:52 PM, Simon Kelley <simon at thekelleys.org.uk> wrote:
> Hugo Heden wrote:
>>
>> Good day all,
>>
>> On Fri, Feb 13, 2009 at 3:55 PM, Chris G <cl at isbd.net> wrote:
>> [snip]
>>>
>>> My /etc/dnsmasq.conf file has only the following lines (apart from
>>> comments):-
>>>
>>>   domain-needed
>>>   bogus-priv
>>>
>>>   expand-hosts
>>>   domain=isbd.net
>>>   dhcp-range=192.168.1.80,192.168.1.150,1h
>>>
>>>   dhcp-option=3,192.168.1.1
>>>
>>>
>>> /etc/resolv.conf is:-
>>>
>>>   nameserver 127.0.0.1
>>>   nameserver 195.74.113.58
>>>   nameserver 195.74.113.62
>>>
>>>
>>> That's about it, pretty standard dnsmaq installation.
>>>
>>
>> How is this supposed to work? Does not dnsmasq (by default) use the
>> nameserver-entries in /etc/resolv.conf as "upstream" nameservers, to
>> forward ("non-local") dns-queries to? But what happens if dnsmasq then
>> forwards a ("non-local") dns-query to 127.0.0.1, i.e to itself? Could
>> that not result in some kind of infinite loop weirdness?
>
> dnsmasq knows that it's listening on 127.0.0.1 so it's clever enough not  to
> forward requests there. (Check the logs, it will even tell you what it is
> doing.)
>

Ah. Thank you very much, Simon. This makes things even easier to set up then.

Best regards

Hugo Heden