0

Issues with certain IPs that can't connect to NextDNS

Hello NextDNS community,

I've been struggling with this issue for months, I've tried to debug it but can't think of any solutions currently, please suggest them?

The issue: every couple of weeks I get a bad IP in my residential IP network at home, with the said IP I can't connect to NextDNS servers, so all my devices are unable to connect to internet because of DNS. All my android/iphone devices which use system's builtin dot/doh features respectively can't connect to any service that depends on DNS.

The workaround: that I've found working is to shutdown my router and wait for a while and then restart it. So maybe I get a new IP and everything is back to normal. Then couple of weeks pass and I get a bad IP once again and I have to use the workaround which does not always work.

From my limited testing the IP can change automatically without the router restarting or any notice.

I would appreciate if anyone from NextDNS/community can offer any help.

2 replies

null
    • losnad
    • 1 yr ago
    • Reported - view

    When it stops working, what is happening if you disconnect from Wi-Fi and use mobile data? 

    Do you also have NextDNS configured on the router or not.

    The problem might be from the router.

    There might also be that you have a device which is making excessive requests on a short period of time and you get blocked by NextDNS. This can be checked by @NextDNS.

      • brigette
      • 1 yr ago
      • Reported - view

      losnad thank you very much for the answer  There might also be that you have a device which is making excessive requests on a short period of time and you get blocked by NextDNS. This can be checked by @NextDNS.❤️

      > When it stops working, what is happening if you disconnect from Wi-Fi and use mobile data? 

      Internet and nextDNS work normally

      > Do you also have NextDNS configured on the router or not.

      Router settings can't be changed, it is a proprietary system with literally no settings just stats.

      > The problem might be from the router.

      Maybe? can you elaborate more how that could be? I'm not well-versed enough in networking.

      > There might also be that you have a device which is making excessive requests on a short period of time and you get blocked by NextDNS. This can be checked by @NextDNS.

      If that was the case I would guess it would show in my NextDNS dashboard/analytics/.

Login to reply

Content aside

  • 1 yr agoLast active
  • 2Replies
  • 88Views
  • 1 Following