I think I have figured out what is wrong, I tried removing the default search domain line, and it started working just fine. After looking further into the name resolution code, it appears that libc is adding the default search domain to all queries; it would appear that the criteria for doing so has changed to any domain name that isn't fully qualified. I threw together a small program to test this, and resolving 'us.v29.distributed.net' fails but 'us.v29.distributed.net.' succeeds. Both however succeed when the computer is connected to the modem instead of the router, I think this may have something to do with the router using '.local.' as the top level domain for the local network. As for why this only affects the distributed.net client and not anything else, I have no idea.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/983574 Title: DNS name resolution doesn't work on systems without a direct connection to the internet To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/distributed-net/+bug/983574/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
