0

Native MacOS App Much slower than Router CLI

I was just doing some random testing and when the client is enabled the responses are much higher (85ms) vs the Unifi Router responses upstream at 0ms.

 

I am curious why the native app seems much slower to resolve.

MacOS App

;; ANSWER SECTION:
www.yahoo.com.          300     IN      A       74.6.143.26
www.yahoo.com.          300     IN      A       74.6.143.25
www.yahoo.com.          300     IN      A       74.6.231.20
www.yahoo.com.          300     IN      A       74.6.231.21

;; Query time: 83 msec
;; SERVER: 192.0.2.42#53(192.0.2.42)
;; WHEN: Thu Apr 28 08:59:05 EDT 2022
;; MSG SIZE  rcvd: 106

Router Upstream from same laptop Native App Disabled

;; ANSWER SECTION:
www.yahoo.com.          5       IN      A       74.6.143.25
www.yahoo.com.          5       IN      A       74.6.143.26
www.yahoo.com.          5       IN      A       74.6.231.20
www.yahoo.com.          5       IN      A       74.6.231.21

;; Query time: 0 msec
;; SERVER: 192.168.100.1#53(192.168.100.1)
;; WHEN: Thu Apr 28 09:01:40 EDT 2022
;; MSG SIZE  rcvd: 106

3 replies

null
    • Pro subscriber ✓
    • DynamicNotSlow
    • 2 yrs ago
    • Reported - view

    0ms is only because it's cached 

    • Chris_Colotti
    • 2 yrs ago
    • Reported - view

    Then it seems curious why the native client does not cache (or have the option to) like the router CLI

      • NextDNs
      • 2 yrs ago
      • Reported - view

      Chris Colotti dig does not query the system stub resolver and thus short circuit the system’s DNS cache by connecting to the system configured resolver IP directly. When using CLI on router, dig connects to it as a resolver and thus benefits from its cache.

Login to reply

Content aside

  • 2 yrs agoLast active
  • 3Replies
  • 59Views
  • 2 Following