1

Logs not working

Hello there, I have several profiles and noticed that my logs are not working. Is there anything I can do to kick them back in gear?

https://nextdns.io/diag/cb9cfb50-a998-11ee-aced-17d931f6f415

7 replies

null
    • Matt_bell
    • 10 mths ago
    • Reported - view

    Seeing the same thing here. My logs are either lagging by 5 minutes, or not showing up at all. Removed my diag link as it provides location information as to where I live.

    Just noticed doing nslookups to NextDNS servers are also failing: 

    C:\Users\matt>nslookup yahoo.com 45.90.28.42
    DNS request timed out.
        timeout was 2 seconds.
    Server:  UnKnown
    Address:  45.90.28.42

    DNS request timed out.
        timeout was 2 seconds.
    DNS request timed out.
        timeout was 2 seconds.
    DNS request timed out.
        timeout was 2 seconds.
    DNS request timed out.
        timeout was 2 seconds.
    *** Request to UnKnown timed-out

    C:\Users\matt>nslookup yahoo.com 45.90.30.42
    DNS request timed out.
        timeout was 2 seconds.
    Server:  UnKnown
    Address:  45.90.30.42

    DNS request timed out.
        timeout was 2 seconds.
    DNS request timed out.
        timeout was 2 seconds.
    DNS request timed out.
        timeout was 2 seconds.
    DNS request timed out.
        timeout was 2 seconds.
    *** Request to UnKnown timed-out

    For some more info:

    C:\Users\matt>curl -v https://dns.nextdns.io/info
    *   Trying 149.248.36.234:443...
    * Connected to dns.nextdns.io (149.248.36.234) port 443
    * schannel: disabled automatic use of client certificate
    * ALPN: curl offers http/1.1
    * ALPN: server did not agree on a protocol. Uses default.
    * using HTTP/1.x
    > GET /info HTTP/1.1
    > Host: dns.nextdns.io
    > User-Agent: curl/8.4.0
    > Accept: */*
    >
    < HTTP/1.1 200 OK
    < Access-Control-Allow-Origin: *
    < Content-Type: application/json
    < Strict-Transport-Security: max-age=63072000; includeSubDomains; preload
    < Timing-Allow-Origin: *
    < Date: Wed, 03 Jan 2024 20:47:11 GMT
    < Content-Length: 85
    <
    {"locationName": "馃嚭馃嚫 Seattle, United States", "pop": "vultr-sea", "rtt": 13592}* Connection #0 to host dns.nextdns.io left intact

    • CFD
    • 10 mths ago
    • Reported - view

    I've also seen this in the past few days. Logs are no longer working in real-time, with significant delays (anywhere from 45m to 2h). Very difficult to monitor traffic when you can't follow it as it's happening. Any help/tips here would be greatly appreciated.

    • NextDNs
    • 10 mths ago
    • Reported - view

    We are aware of the delay. We are working on a resolution.

      • Matt_bell
      • 10 mths ago
      • Reported - view

       Seems to be fixed from what I can see! Thank you NextDNS Staff!

      • CFD
      • 10 mths ago
      • Reported - view

      Appears fixed on my end as well. Thanks so much for the attention and fast turnaround.

      • Fred_B
      • 8 mths ago
      • Reported - view

        Logs are not working again since yesterday ('m in France)

      • revue_2_presse
      • 8 mths ago
      • Reported - view

Content aside

  • Status Fixed
  • 1 Likes
  • 8 mths agoLast active
  • 7Replies
  • 197Views
  • 6 Following