Author: laner
Description:
Both dnsmasq and our recursors are caching lookups to private DNS. This
is really annoying when an instance is deleted, cached, then recreated,
because we need to SIGHUP dnsmasq and we need to wipe the cache on the
recursors to make the instance immediately available.
Either dnsmasq or our recursors should cache, not both.
dvanliere wrote:
Hey Ryan,
Is this still an issue?
D
Both dnsmasq and our recursors are caching lookups to private DNS. This
is really annoying when an instance is deleted, cached, then recreated,
because we need to SIGHUP dnsmasq and we need to wipe the cache on the
recursors to make the instance immediately available.Either dnsmasq or our recursors should cache, not both.
On Thu Apr 17 07:09:53 2014, ariel wrote:
GIving this to Marc to follow up, since he's labs point person now.
There are other issues caused/made worse by dnsmasq and the entire thing needs
to be rethought. I'll keep this on my radar, but that's not going to be
anywhere sooner than Q3.
Yeah, I'm planning on creating a proper recursor this week that should fix most/all of those issues.
Recreating dead instances with same name should be rare enough for the 5min TTL to not be a big deal, I think.
If it ever turns out to be an issue, reducing the TTL slightly would be acceptable (but no lower than 2 min or so - it takes that long to build an instance anyways)