Martin: the domain suffix ends up in "search" field in resolv.conf or equivalent, and that's a purely client-side expansion. All that does is to append the domain or search suffix to all queries and try those first, before trying to resolve the query as given. It doesn't matter which resolver is contacted, the resolvers should all have the same domain tree starting with the root record.
Teej: The more I've thought about this, the more I end up wanting to run my own caching recursor locally. That might need some NetworkManager integration to always stick 127.0.0.1 first if there is a locally cahcing bind installed. I'm not sure this is a good default behaviour though, since it loads the common infrastructure on the internet more than using your providers caching servers... Just increasing MAXNS won't actually hurt anything (I think), unless you locally configure in more nameserver entries. I have a couple of server networks with a few hundred servers where this would really help reliability though. Especially those where I want to have both v4 and v6 nameservers listed. -- Resolver: MAXNS should be increased https://bugs.launchpad.net/bugs/118930 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
