[Pkg-samba-maint] Bug#591752: samba-common: please change the name resolv order
fabian at greffrath.com
Fri Aug 6 05:48:05 MDT 2010
Am 06.08.2010 12:03, schrieb Volker Lendecke:
> The reason why we do it this way is the additional timeout
> we would run into. More and more networks have DNS
> configured these days, and if we put broadcast before DNS,
> we would run into a timeout before we tried DNS every single
> time. A better way might be to do all the methods in
> parallel, but if *some* method gives a positive result, how
> do we judge if that is actually the result you desire?
That's a good question. How does Windows handle this, by the way?
> I know broken DNS redirects are very popular with home DSL
> connects, but there is probably not much that Samba can do
> about that.
It's just an idea, but would it be possible to make the name resolv
order changeable from the outside, i.e. as part of the public API?
Then gvfs/nautilus, when the first attempt to resolve the hostname
with the default order lead to a bogus IP from which it was impossible
to receive a share list, could try a second time with precedence on
"bcast" before they finally give up and show an error message.
> Another mis-configuration might be the fact that your local
> DNS queries are forwarded to the ISP at all. Why does that
> happen? This might be at best an information leak.
To be honest, I don't know. I do not even know if my router is able to
distinguish between local and non-local DNs queries. At least I have
not found any setting to change this behaviour in its preferences.
More information about the samba-technical