Response time shown in "Diagnostics…DNS Lookup" - 2.3.2

RickNY

I'm using DNS Resolver on 2.3.2 and forwarding disabled.. I notice that when I perform any DNS lookups under "Diagnostics…DNS Lookup", the response time for any query shows "127.0.0.1 0 msec". Is this broken in this version? If its not, can someone explain why it always shows 0 msec? Also, this happens when querying entries that I know would not be in the cache.

Thanks,
Rick

johnpoz

Well clearly what your looking up is in the cache.

Restart the service so your sure the cache is clear - then do your lookup

clearyourcache.jpg_thumb

nextlookup.jpg_thumb

RickNY

I had cleared the cache by restarting the service and I've rebooted. Still every query shows 0 msec on that page.

So.. If I do the same from a command line, I do see actual times (Just so I am clear – I did the below.. Then restarted Unbound.. Then used the GUI utility for same.


[2.3.2-RELEASE][root@mydomain.com]/root: host -v -t A www.yahoo.com
Trying "www.yahoo.com"
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 36622
;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;www.yahoo.com.                 IN      A

;; ANSWER SECTION:
www.yahoo.com.          299     IN      CNAME   fd-fp3.wg1.b.yahoo.com.
fd-fp3.wg1.b.yahoo.com. 60      IN      A       98.139.183.24
fd-fp3.wg1.b.yahoo.com. 60      IN      A       98.139.180.149

Received 90 bytes from 127.0.0.1#53 in 437 ms

But no matter how many times I restart the Unbound service, the GUI utility returns 0 msec for everything..

after_cache_clear.jpg_thumb

johnpoz

did you clear your browser cache? I would think something more related with browser, try different 1 which 1 are you using? I am not showing the problem here. Using firefox 49

RickNY

I tried clearing browser cache and using under both Chrome and Firefox.. No dice.. As an experiment I took a full backup of the config and did a clean install of 2.3.2 with all of its default settings, using igb0 for WAN with DHCP and igb1 for LAN with the default 192.168.1.1 address, and observed the same exact behavior.. Strange… This has worked for me in the past without issue - not sure what happened.. I'm using the ADI CE build (pfSense-CE-memstick-ADI-2.3.2-RELEASE-amd64.img.gz) on a Netgate RCC-VE 2440 if that makes any difference.

RickNY

Out of curiosity – what version are you using? I just tried 2.3.1, and it seems to behave properly there.. I just did a clean install of 2.3.1 in Vmware and tested, and the utility is showing response times for uncached items.. I then did a clean install of 2.3.2, and its reporting 0 msec there for everything I try to look up.

MoonKnight

I do get the same results.
Did a DNS Lookup on www.cnn.com (<–-- never used to be here and my pfSense has been running for only 1 day now and my browser cache is clean.

![Desktop 24-09-2016 20.57.20-598.png](/public/imported_attachments/1/Desktop 24-09-2016 20.57.20-598.png)
![Desktop 24-09-2016 20.57.20-598.png_thumb](/public/imported_attachments/1/Desktop 24-09-2016 20.57.20-598.png_thumb)