No subject

> $ dig volltreffer.de
> 
> ; <<>> DiG 9.7.0-P1 <<>> volltreffer.de
> ;; global options: +cmd
> ;; connection timed out; no servers could be reached


deadwood log:
> Got DNS query for \013volltreffer\002de\000\000\001
> Sending reply for query \013volltreffer\002de\000\000\001
> Sending reply for query \013volltreffer\002de\000\000\001
> Got DNS query for \013volltreffer\002de\000\000\001
> Sending reply for query \013volltreffer\002de\000\000\001
> Processing NS refer for \013volltreffer\002de\000\000\001
> Processing NS refer for \003ns\061\010first\055ns\002de\000\000\001
> Processing NS refer for \002ns\011second\055ns\003com\000\000\001
> Got DNS query for \013volltreffer\002de\000\000\001
> Sending reply for query \013volltreffer\002de\000\000\001
> Sending reply for query \013volltreffer\002de\000\000\001
> Processing NS refer for \010robotns\062\011second\055ns\002de\000\000\001
> Caching direct answer at \010robotns\062\011second\055ns\002de\000\000\001
> Processing NS refer for \003ns\061\013your\055server\002de\000\000\001
> Caching direct answer at \003ns\061\013your\055server\002de\000\000\001
> Caching direct answer at \003ns\063\011second\055ns\002de\000\000\001
> Caching direct answer at \003ns\061\010first\055ns\002de\000\000\001
> Caching direct answer at \013volltreffer\002de\000\000\001
> Sending reply for query \013volltreffer\002de\000\000\001
> Fetching \013volltreffer\002de\000\000\001 from cache


digging a second time:
> $ dig volltreffer.de
> 
> ; <<>> DiG 9.7.0-P1 <<>> volltreffer.de
> ;; global options: +cmd
> ;; Got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 55948
> ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
> 
> ;; QUESTION SECTION:
> ;volltreffer.de.                        IN      A
> 
> ;; ANSWER SECTION:
> volltreffer.de.         3284    IN      A       88.198.209.2
> 
> ;; Query time: 1 msec
> ;; SERVER: 192.168.1.1#53(192.168.1.1)
> ;; WHEN: Mon Jul 26 11:54:36 2010
> ;; MSG SIZE  rcvd: 48


query time 1msec -> Oh wonder, it's cached by dnsmasq.

To get it more visual what I mean, I use nslookup.

> C:\>nslookup clubber.de
> Server:  router.lan
> Address:  192.168.1.1
> 
> Nicht autorisierende Antwort:
> DNS request timed out.
>     timeout was 2 seconds.
> Name:    clubber.de
> Address:  88.198.34.48



deadwood logs:
> Got DNS query for \007clubber\002de\000\000\001
> Sending reply for query \007clubber\002de\000\000\001
> Caching direct answer at \007clubber\002de\000\000\001
> Sending reply for query \007clubber\002de\000\000\001
> Fetching \007clubber\002de\000\000\001 from cache
> Got DNS query for \007clubber\002de\000\000\034
> Sending reply for query \007clubber\002de\000\000\034
> Sending reply for query \007clubber\002de\000\000\034


I can't tell you much more since it's happening by random.

Another one:
> C:\>nslookup mueller.de
> Server:  router.lan
> Address:  192.168.1.1
> 
> DNS request timed out.
>     timeout was 2 seconds.
> DNS request timed out.
>     timeout was 2 seconds.
> *** Zeitüberschreitung bei Anforderung an router.lan.

> C:\>nslookup mueller.de
> Server:  router.lan
> Address:  192.168.1.1
> 
> Nicht autorisierende Antwort:
> DNS request timed out.
>     timeout was 2 seconds.
> Name:    mueller.de
> Address:  80.148.9.139


> Got DNS query for \007mueller\002de\000\000\001
> Sending reply for query \007mueller\002de\000\000\001
> Sending reply for query \007mueller\002de\000\000\001
> Got DNS query for \007mueller\002de\000\000\034
> Sending reply for query \007mueller\002de\000\000\034
> Processing NS refer for \007mueller\002de\000\000\034
> Got DNS query for \007mueller\002de\000\000\001
> Sending reply for query \007mueller\002de\000\000\001
> Caching direct answer at \007mueller\002de\000\000\001
> Sending reply for query \007mueller\002de\000\000\001
> Fetching \007mueller\002de\000\000\001 from cache
> Got DNS query for \007mueller\002de\000\000\034
> Sending reply for query \007mueller\002de\000\000\034
> Sending reply for query \007mueller\002de\000\000\034
> Processing NS refer for \014secondary\060\060\066\004dtag\003net\000\000\001
> Processing NS refer for \003pns\004dtag\002de\000\000\001
> Caching direct answer at \003pns\004dtag\002de\000\000\001
> Caching direct answer at \014secondary\060\060\066\004dtag\003net\000\000\001
> Processing NS refer for \014secondary\060\060\066\004dtag\003net\000\000\001
> Caching direct answer at \014secondary\060\060\066\004dtag\003net\000\000\001
> Sending SERVER FAIL for query \007mueller\002de\000\000\034


Using nslookup on linux.
> $ nslookup ochsen.de
> ;; connection timed out; no servers could be reached
> 
> $ nslookup ochsen.de
> Server:         192.168.1.1
> Address:        192.168.1.1#53
> 
> Non-authoritative answer:
> Name:   ochsen.de
> Address: 85.199.129.66


> Got DNS query for \006ochsen\002de\000\000\001
> Sending reply for query \006ochsen\002de\000\000\001
> Sending reply for query \006ochsen\002de\000\000\001
> Got DNS query for \006ochsen\002de\000\000\001
> Sending reply for query \006ochsen\002de\000\000\001
> Sending reply for query \006ochsen\002de\000\000\001
> Got DNS query for \006ochsen\002de\000\000\001
> Sending reply for query \006ochsen\002de\000\000\001
> Sending reply for query \006ochsen\002de\000\000\001
> Got DNS query for \006ochsen\002de\000\000\001
> Sending reply for query \006ochsen\002de\000\000\001
> Processing NS refer for \006ochsen\002de\000\000\001
> Processing NS refer for \003ns\063\013dnsmittwald\002de\000\000\001
> Caching direct answer at \004ns\061\060\004ns\061\064\002de\000\000\001
> Caching direct answer at \003ns\063\013dnsmittwald\002de\000\000\001
> Caching direct answer at \006ochsen\002de\000\000\001
> Sending reply for query \006ochsen\002de\000\000\001
> Fetching \006ochsen\002de\000\000\001 from cache


Cheers,
Sebastian