[Dnsmasq-discuss] "random" problem with name resolution
stefano.bridi at gmail.com
Thu Jul 30 17:23:11 BST 2009
On Fri, Jul 24, 2009 at 1:12 PM, Simon Kelley<simon at thekelleys.org.uk> wrote:
> Stefano Bridi wrote:
> My guess is that when it goes wrong, the upstream server is returning the
> CNAME record, but not the A record. That's the most likely explanationf for
> the log messages you are seeing.
> I've never found an actual standard that says what the semantics of this
> are, but practically, all resolvers, when they ask for the A record for
> <domain> and get back
> <domain> CNAME <target>
> without the corresponding
> <target> A 18.104.22.168
> treat this to mean the there is no A record for target, and don't try a
> query for A <target>
> Dnsmasq will just be passing this reply straight through, so the resolver
> which made the query will behave in this way.
> This looks like an upstream server problem. Making the TTLs equal might be
> enough to solve it.
>> At the moment I'm trying to "patch" with dnsmasq that ask to a
>> dedicated pdnsd that act as a recursive dns cache server. In the
>> eventuality that this sandwich setup solve the problem... In your
>> opinion can I gain other advantage/problem?
> Given the above, that may well be a good solution.
At the moment it seems to work properly but I'm still crossing my fingers ;)
More information about the Dnsmasq-discuss