Public bug reported:
In our cloud deployment, we configured neutron-dhcp-agent
to have multiple external DNS servers
However, the last server on the list happened to be misconfigured (by others).
So it returned SERVFAIL instead of correct responses and strace showed that
dnsmasq only ever asked the last server for a name.
My testing shows that dropping the --strict-order parameter helped this problem.
It was introduced in commit 43960ee448 without reason given.
** Affects: neutron
Importance: Undecided
Assignee: Dirk Mueller (dmllr)
Status: In Progress
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1746000
Title:
dnsmasq does not fallback on SERVFAIL
Status in neutron:
In Progress
Bug description:
In our cloud deployment, we configured neutron-dhcp-agent
to have multiple external DNS servers
However, the last server on the list happened to be misconfigured (by
others). So it returned SERVFAIL instead of correct responses and strace showed
that dnsmasq only ever asked the last server for a name.
My testing shows that dropping the --strict-order parameter helped this
problem.
It was introduced in commit 43960ee448 without reason given.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1746000/+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
