{"action":"opened","issue":{"url":"https://api.github.com/repos/pjps/ndjbdns/issues/19","labels_url":"https://api.github.com/repos/pjps/ndjbdns/issues/19/labels{/name}","comments_url":"https://api.github.com/repos/pjps/ndjbdns/issues/19/comments","events_url":"https://api.github.com/repos/pjps/ndjbdns/issues/19/events","html_url":"https://github.com/pjps/ndjbdns/issues/19","id":106690913,"number":19,"title":"dnsq never resolves an address","user":{"login":"deployable","id":2499983,"avatar_url":"https://avatars.githubusercontent.com/u/2499983?v=3","gravatar_id":"","url":"https://api.github.com/users/deployable","html_url":"https://github.com/deployable","followers_url":"https://api.github.com/users/deployable/followers","following_url":"https://api.github.com/users/deployable/following{/other_user}","gists_url":"https://api.github.com/users/deployable/gists{/gist_id}","starred_url":"https://api.github.com/users/deployable/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/deployable/subscriptions","organizations_url":"https://api.github.com/users/deployable/orgs","repos_url":"https://api.github.com/users/deployable/repos","events_url":"https://api.github.com/users/deployable/events{/privacy}","received_events_url":"https://api.github.com/users/deployable/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-09-16T03:22:16Z","updated_at":"2015-09-16T03:22:16Z","closed_at":null,"body":"The `dnsq` utility never receives a response to it's queries from the `dnccache` process, or any dns server for that matter. \r\n\r\nThe requests make it into the server, but no response (or errors or debug) are generated. \r\n\r\nRunning with `dnscache` in the background with a `tcpdump` watching the traffic.\r\n\r\nsudo dnscache -c dnscache.conf  &\r\nsudo tcpdump -nn -pi lo port 53 &\r\n\r\n```\r\n[vagrant@localhost ndjbdns]$  ../../bin/dnsq a google.com 127.0.0.1\r\n02:15:06.786874 IP 127.0.0.1.53959 > 127.0.0.1.53: 59192 A? google.com. (28)\r\n02:15:07.814536 IP 127.0.0.1.51585 > 127.0.0.1.53: 20475 A? google.com. (28)\r\n02:15:10.836891 IP 127.0.0.1.46061 > 127.0.0.1.53: 17593 A? google.com. (28)\r\n```\r\n\r\n```\r\n[vagrant@localhost ndjbdns]$ dig @127.0.0.1 google.com\r\n02:16:51.448684 IP 127.0.0.1.37417 > 127.0.0.1.53: 28292+ [1au] A? google.com. (39)\r\nSep 16 2015 02:16:51 Q3 127.0.0.1:37417 28292 A? google.com.\r\nSep 16 2015 02:16:51 R3 0:success 1 44\r\n02:16:51.448888 IP 127.0.0.1.53 > 127.0.0.1.37417: 28292 1/0/0 A 216.58.220.142 (44)\r\n\r\n; <<>> DiG 9.9.4-RedHat-9.9.4-18.el7_1.5 <<>> @127.0.0.1 google.com\r\n; (1 server found)\r\n;; global options: +cmd\r\n;; Got answer:\r\n;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 28292\r\n;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0\r\n\r\n;; QUESTION SECTION:\r\n;google.com.\t\t\tIN\tA\r\n\r\n;; ANSWER SECTION:\r\ngoogle.com.\t\t156\tIN\tA\t216.58.220.142\r\n\r\n;; Query time: 0 msec\r\n;; SERVER: 127.0.0.1#53(127.0.0.1)\r\n;; WHEN: Wed Sep 16 02:16:51 UTC 2015\r\n;; MSG SIZE  rcvd: 44\r\n```\r\n\r\n```\r\n[vagrant@localhost ndjbdns]$ nslookup google.com 127.0.0.1\r\n02:17:05.638672 IP 127.0.0.1.40854 > 127.0.0.1.53: 14134+ A? google.com. (28)\r\nSep 16 2015 02:17:05 Q4 127.0.0.1:40854 14134 A? google.com.\r\nSep 16 2015 02:17:05 R4 0:success 1 44\r\n02:17:05.638875 IP 127.0.0.1.53 > 127.0.0.1.40854: 14134 1/0/0 A 216.58.220.142 (44)\r\nServer:\t\t127.0.0.1\r\nAddress:\t127.0.0.1#53\r\n\r\nNon-authoritative answer:\r\nName:\tgoogle.com\r\nAddress: 216.58.220.142\r\n```\r\n\r\nThis is on both a linux and mac build\r\n"}}