@Martin: If ping <any name> fails, I wonder if the DNS redirection opt- out has somehow effectively "opted out" of *all* DNS resolution? That could explain why ping yahoo.com (for example) now fails. Can you still browse the web, deal with email, etc as normal once "opted out" from the DNS redirection? If you can, then at least some names are resolving OK.
Did you mean that ping <any local machine name> now fails, but remote DNS registered hostnames/domains (like ping yahoo.com ) still work fine? If it is just local machine names that are failing to resolve, then I suspect you can either: (a) add the machine names and their IPs manually to your hosts file(s) or to the DNS zonefile for your local (internal) DNS domain, or into WINS if there is a WINS server in the picture and/or (more work up front, but probably better and less maintenance once set up) (b) arrange for the DHCP server to dynamically update your local DNS server, so that the name and IP of each Windows machine that receives a DHCP-provided IP address appears as a hostname there. If the DHCP server and DNS server are a Windows 2003 server, this is essentially "automatic"; if you are using Ubuntu for these services, you'll have to do some configuration work to get it to behave this way, as far as I know. One more thought: If "ping server" fails but "ping server.mydomain.local" works, then the default DNS resolver search probably needs changing to include your domain name (search mydomain.local in my example). You can edit this in /etc/resolv.conf . Getting rid of your DNS redirection was a big step in the right direction. -- cannot browse samba shares without editing smb.conf https://bugs.launchpad.net/bugs/375593 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
