Public bug reported: Ubuntu 8.04 New install. Packages apt: Installed: 0.7.9ubuntu17 Candidate: 0.7.9ubuntu17 firefox: Installed: 3.0~b5+nobinonly-0ubuntu3 Candidate: 3.0~b5+nobinonly-0ubuntu3
Tested this with both BIND9 and WinDNS for the back-end It seems that any domain that does not have a valid TLD will not resolve properly for apt and web browsers. However it will return proper results with dig and nslookup. ex. myserver.domain.local, myserver.domain.something, myserver.domain.coooom will all fail to resolve. However... if you add your domain to your search domains in resolv.conf (or network manager) it will resolve by just machine name instead of FQDN. This could be related to or the same as http://bugs.launchpad.net/ubuntu/+source/avahi/+bug/80900 ** Affects: ubuntu Importance: Undecided Status: New -- Internal FQDNs will not resolve for non-valid TLD domains https://bugs.launchpad.net/bugs/226403 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
