Perhaps this should also involve Network Manager (if in a Desktop context) to warn about it when this setting is detected.
Use case 1: Matt want to use OpenDNS. He follows easy instruction to set it up. Later the same week he browses his network in nautilus. Nautilus makes a DNS request that should return an error, the DNS request doesn't fail, meaning the DNS server is configured in a way that requires changing resolve order in /etc/samba/smb.conf. A warning is presented asking to confirm the change, and explaining why it's needed, or asking to contact the system admin. Matt enters his password, the directive is changed, the samba service is restarted and expected functionality is restored. Use case 2: Matt want to use OpenDNS. He follows easy instruction to set it up. Nautilus (or else) opens immediately and makes a DNS request that should return an error, the DNS request doesn't fail, meaning the DNS server is configured in a way that requires changing resolve order in /etc/samba/smb.conf. A warning is presented asking to confirm the change, and explaining why it's needed, or asking to contact the system admin. Does that sound crazy ? I am told such DNS setups can be checked, I only use the "make request, if it doesn't fail it's breaking local DNS" analogy for illustration purposes. -- Unable to view Window shares because of the default resolve order https://bugs.launchpad.net/bugs/189168 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
