[Dnsmasq-discuss] can resolve 1 specific host
knud.skrald at guldberg.info
Sun Nov 15 13:29:11 GMT 2009
Just tested again...same issue again
asking my upstream nameserver...
camping.dba.dk => unknown
www.dba.dk => ok
again camping.dba.dk => now ok !
restart my dnsmasq makes it to known www.dba.dk and camping.dba.dk
I am running another dnsmasq server (at a school) with another upstream
nameserver...there seems no problems
It is another version of dnsmasq included in the FREESCO packged.
But it seems not to be a dnsmasq issue but further upstream problem
Just strange that this specific host gives problems and not others (to
Simon Kelley wrote:
> knud.skrald at guldberg.info wrote:
>> From time to time I get problmem with one host name
>> www.dba.dk and camping.dba.dk
>> They can not be solved, seems to be locked in some way on my dnsmasq
>> A snip (reduced) of my log file is attached.
>> Dnsmasq-discuss mailing list
>> Dnsmasq-discuss at lists.thekelleys.org.uk
> Nov 14 20:58:46 dnsmasq: query[A] www.dba.dk from 10.2.1.182
> Nov 14 20:58:46 dnsmasq: forwarded www.dba.dk to 184.108.40.206
> Nov 14 20:58:46 dnsmasq: reply www.dba.dk is 220.127.116.11
> That looks good.....
> Nov 14 20:58:59 dnsmasq: query[A] camping.dba.dk from 10.2.1.182
> Nov 14 20:58:59 dnsmasq: forwarded camping.dba.dk to 18.104.22.168
> Nov 14 20:58:59 dnsmasq: reply camping.dba.dk is <CNAME>
> Nov 14 20:58:59 dnsmasq: reply www.dba.dk is NODATA-IPv4
> Now we look up camping.dba.dk, and get back the answer that
> camping.dba.dk is a CNAME for www.dba.dk, and no data for www.dba.dk.
> This means that the domain www.dba.dk exists, but there is no "A" record
> for it. That information is cached, so future attemps to look up
> www.dba.dk or camping.dba.dk fail, because dnsmasq "knows" that
> www.dba.dk has no data.
> There's clearly something wrong in the upstream server at
> 22.214.171.124, since it gave the correct data to the first request.
> I've tried a query to 126.96.36.199 and I get the correct information,
> so it could be a problem which has been resolved:
> srk at spike$ dig @188.8.131.52 camping.dba.dk
> ; <<>> DiG 9.5.1-P3 <<>> @184.108.40.206 camping.dba.dk
> ; (1 server found)
> ;; global options: printcmd
> ;; Got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 19814
> ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 4, ADDITIONAL: 4
> ;; QUESTION SECTION:
> ;camping.dba.dk. IN A
> ;; ANSWER SECTION:
> camping.dba.dk. 600 IN CNAME www.dba.dk.
> www.dba.dk. 1444 IN A 220.127.116.11
> running this query through my local dnsmasq causes the correct thing to
> be cached.
> Summary: the problem seems to be in the upstream nameserver, but it's OK
> now. If you are still hitting problems, try restarting dnsmasq to clear
> out the bad cache entries, and try again: If it's still broken, complain
> to whoever runs that nameserver.
More information about the Dnsmasq-discuss