https://bugzilla.novell.com/show_bug.cgi?id=446017
User sbrabec@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=446017#c14
--- Comment #14 from Stanislav Brabec 2008-12-03 05:27:17 MST ---
Confirming that stopping of avahi re-enables DNS queries for .local?
But I guess it is not as flexible as nssswitch.conf: Several packages complain,
if avahi is not running. For example use of DNS-SD inside DNS .local domain
will not be possible (e. g. use of DAAP inside AD)?
I have read the documentation, and found more possible settings:
Resolve .local exclusively via IPv4 MDNS, the rest exclusively via DNS:
hosts: files mdns4_minimal [NOTFOUND=return] dns
(the default)
Resolve .local exclusively via IPv4 MDNS, the rest via DNS, then MDNS:
hosts: files mdns4_minimal [NOTFOUND=return] dns mdns4
(another possible default, may cause obsolete DNS queries, but AD .local works
out of the box)
Try .local first via IPv4 MDNS, then try everything via DNS:
hosts: files mdns4_minimal dns
Try .local first via IPv4 MDNS, the rest first via DNS:
hosts: files mdns4_minimal dns mdns4
(Note: non-existing .local will cause 2 MDNS and 1 DNS queries.)
Try everything first via IPv4 MDNS, then with DNS:
hosts: files mdns4 dns
(useful for users of with Zeroconf ad-hoc network instead of DHCP)
One can combine IPv4 and IPv6 MDNS.
I am thinking about sysconfig, that will allow smart configuration:
MDNS_LOCAL=(exclusive|preferred|world)
default: currently "exclusive", but "preferred" may be an option
MDNS_WORLD=(exclusive|preferred|fallback|none)
default=currently "none", but better may be "fallback"
MDNS_IPv4=(none|local|world|both)
default: both
MDNS_IPv6=(none|local|world|both)
default: none
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.