0

some strange activity MACOS with NEXTDNS udp is being used...

NextDNS I am trying to understand what I see

I have MAcOS with profile and DoH was working fine

then hit test.nextdns.io via chrome and said it was okay but using UDP!

Im not sure how this is possible other then the nextdns profile is broken for chrome but working on the OS level? On Iphone the nextdns profile is working fine and reports DOH as expected via chrome

 

secondly , on the mac OS the nextdns page says all is good  , but when I check my DNS at third party site it saying CIRA(CANADA) is resolving my request is CIRA a nextDNS valid resolver for UDP?

 

to overcome the UDP in chrome I harded coded DoH in Chrome still keeping profile  active to remove the UDP requests.

thanks for any input

4 replies

null
    • Idig
    • 2 wk ago
    • Reported - view

    MACOS : 14.3.1 (23D60)

    chrome Version 123.0.6312.59 (Official Build) (arm64)

    also for others just learning this should be a check you perform daily as I am doing to see this 

     

    https://www.fortinet.com/resources/cyberglossary/dns-hijacking

    • Calvin_Hobbes
    • 2 wk ago
    • Reported - view

    Did you follow the specific instructions for Chrome Browser?

    • Will_Tisdale
    • 2 wk ago
    • Reported - view

    This is a known Chrome (and other chromium based browsers) issue - it uses the system default resolvers instead of the resolver specified in the profile. It's because of the built in DNS resolver within Chrome. https://www.reddit.com/r/nextdns/comments/sfx0d2/chromium_based_browser_not_recognized_as_using/

    You can either fix it by disabling the built in resolver or by adding a DOH address in settings.

      • Idig
      • 2 wk ago
      • Reported - view

        thanks that exactly what I did on chrome and added DoH custom and now working like a champ

       thanks for confirming it a know issue really appreciate it.

Content aside

  • 2 wk agoLast active
  • 4Replies
  • 49Views
  • 3 Following