Tracked in Github Issues as https://github.com/canonical/cloud- init/issues/2794
** Bug watch added: github.com/canonical/cloud-init/issues #2794 https://github.com/canonical/cloud-init/issues/2794 ** Changed in: cloud-init Status: Triaged => Expired -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to cloud-init. https://bugs.launchpad.net/bugs/1658734 Title: DNS queries of does-not-exist.example.com and example.invalid Status in cloud-init: Expired Status in cloud-init package in CentOS: Fix Released Bug description: cloud-init makes several DNS queries for does-not-exist.example.com and example.invalid (and also some random names). https://git.launchpad.net/cloud-init/tree/cloudinit/util.py#n1100 We understand that it does this to detect the kind of DNS redirection that's done an many universities, some ISPs, and services like OpenDNS (when used for filtering or typo correction). However, it can be problematic in an environment where an intrusion detection system might flag these queries as potentially malicious, and in a system where DNS redirection is not used it unnecessarily increases boot time. It looks like the feature was written to make it possible to disable it or provide specific redirection IPs, but that it never gained a config option to control it. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1658734/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
