[Dnsmasq-discuss] local domain added when forwarding to upstream DNS servers

[Tom Metro]

Lixus Zoran wrote:
>> And that isn't followed by a query for www.cnn.com?
> 
> Sorry, I do not understand this question. 

My expectation would be to see a query for host.search-domain, which 
would fail, followed by a query for just host (where in this case 
host=www.cnn.com).


> mydesktop:~# nslookup lists.thekelleys.org.uk
> Server:         127.0.0.1
> ** server can't find lists.thekelleys.org.uk: REFUSED
> 
> mydesktop:~# tshark -i br0 port 53
> Capturing on br0
> -> no outgoing DNS querie captured
> 
> That is surprising me, this querie not even gets forwarded to the upsteam server.

Yes, puzzling. Try adding 'log-queries' to your /etc/dnsmasq.conf and 
see what gets logged when you repeat this.


> 4) checking for lists.thekelleys.org.uk. with a dot at the end
> ** server can't find lists.thekelleys.org.uk: REFUSED

Something has gotten more broken since your prior tests. Aside from 
removing the search line, what else did you change? Dnsmasq seems to be 
behaving as if it doesn't know about the upstream public servers. The 
REFUSED response might be an indication of that as well (instead of 
NXDOMAIN).


> 1) checking for a hostname in my domain without domainname
> ===========================================================
> mydesktop:~# nslookup myfileserver
> ** server can't find myfileserver: REFUSED
> 
> Of course this did not work since i removed the "search mydomain.tld"
> from /etc/resolve.conf and the host is not listed in /etc/hosts

This was a suggested test to see if it would resolve lookups of fully 
qualified non-local hosts. It's expected that it will break lookups of 
unqualified local hosts.


> mydesktop:~# /etc/init.d/nscd stop

Isn't a name service cache daemon redundant on a machine using Dnsmasq 
for local resolution?

  -Tom

-- 
Tom Metro
Venture Logic, Newton, MA, USA
"Enterprise solutions through open source."
Professional Profile: http://tmetro.venturelogic.com/