Context: I work for http://weave.works.

A user of our product reported an issue with reverse DNS at weaveworks/weave#2157 - Docker DNS is giving an answer which break's the user's Kerberos.

Weave provides a DNS server that has a few different features to Docker's DNS - it resolves the hostname for instance, and it allows the user to put containers in different DNS subdomains. For forward lookups we can ensure that Docker DNS doesn't answer by choosing a domain that doesn't match a network name.

For reverse lookups of container addresses, however, Docker DNS will answer first, and give an answer that doesn't match the forward lookup.

I know the standard answer is that Docker will not provide an option to disable the built-in DNS. But we would like a way to provide add-on features without work-arounds and subterfuge.