You may not be able to access the site when NextDNS is enabled

t_k
13 days ago
11replies

First of all, let me apologize.

I am Japanese and this sentence was translated into English using the Mac's translation function.

It may be difficult to understand.

Well, you may not be able to access the site when NextDNS is enabled.

You may not be able to log in to the smartphone app.

A failure occurs when NextDNS is enabled on Mac, iPhone, Android smartphones, and all of them.

※You may not always be unable to access the site or log in to the app, but you may be able to.

Failures occur when connected to Wi-Fi, and no problems occur during mobile communication.

Is this a problem with the Wi-Fi device or the Internet connection service I am using?

When I type Ping from my Mac to the target site, the IP returned when NextDNS is active and when it is disabled is different, but I think that's the reason.

- Jos
- 13 days ago
- Reported - view
Could nextdns be blocked by your internet provider? Are you able to visit https://ping.nextdns.io
- t_k
  
  12 days ago
  
  Reported - view
  Thank you for your comment.
  
  NextDNS will not be blocked by Internet providers.
  
  Even when NextDNS is active, not all sites cannot be connected, only certain sites will not respond.
  
  The site is not blocked by NextDNS, and the connection seems to time out.
  
  Access to https://ping.nextdns.io is available.
  
  zepto-tyo 6 ms (anycast1, ultralow2)
  
  ■ vultr-tyo 7 ms (anycast2, ultralow1)
  vultr-sel 37 ms
  zepto-sel 39 ms
  zepto-hkg 58 ms
  lightnode-tpe 68 ms
  lightnode-mnl 87 ms
  zepto-tpe 92 ms
  anexia-hkg 169 ms
  premiumrdp-mnl 179 ms
- R_P_M
- 13 days ago
- Reported - view
Please provide the domain you are having issue with, if possible.
- t_k
  
  12 days ago
  
  Reported - view
  Thank you for your comment.
  
  An example of a problematic domain is netsuper.rakuten.co.jp.
  
  The results of Ping will be posted below.
  
  When NextDNS is enabled.
  
  PING netsuper.rakuten.co.jp (23.222.96.163): 56 data bytes
  
  Request timeout for icmp_seq 0
  
  Request timeout for icmp_seq 1
  
  Request timeout for icmp_seq 2
  
  Request timeout for icmp_seq 3
  
  When NextDNS is disabled.
  
  PING e3597.b.akamaiedge.net (210.57.92.140): 56 data bytes
  
  64 bytes from 210.57.92.140: icmp_seq=0 ttl=55 time=6.314 ms
  
  64 bytes from 210.57.92.140: icmp_seq=1 ttl=55 time=5.905 ms
  
  64 bytes from 210.57.92.140: icmp_seq=2 ttl=55 time=5.368 ms
  
  64 bytes from 210.57.92.140: icmp_seq=3 ttl=55 time=7.681 ms
  
  The above is the Ping result from the Mac terminal.
  
  The results of Ping execution from the Wi-Fi router are posted below.
  
  netsuper.rakuten.co.jp
  
  64 bytes from 23.55.208.165: icmp_seq=0 ttl=58 time=4.901 ms
  64 bytes from 23.55.208.165: icmp_seq=1 ttl=58 time=3.936 ms
  64 bytes from 23.55.208.165: icmp_seq=2 ttl=58 time=2.624 ms
  64 bytes from 23.55.208.165: icmp_seq=3 ttl=58 time=2.310 ms
- t_k
- 12 days ago
- Reported - view
Additional information.

Certain sites that cannot be connected are not blocked by NextDNS, and the NextDNS log does not state the fact of blocking.

In addition, you cannot connect to a specific site even if you do not use all the functions of NextDNS (privacy, security, etc.).

This problem does not occur much on Macs and is frequent on iPhones.
- Jos
  
  11 days ago
  
  Reported - view
  have you got Apple’s Private Relay enabled in your iCloud settings on the device? If yes, can you disable it and test again? The domains you provided load fine here with nextdns enabled.
- t_k
  
  10 days ago
  
  Reported - view
  I don't use iCloud Private Relay.
  
  I don't think it's a problem with devices or OS because problems occur not only on Apple devices but also on Android devices.
  
  I think the possible factors are Wi-Fi devices, Internet providers, or NextDNS.
  
  There was no problem until the other day, either Internet provider or NextDNS or both.
  
  I also contacted the Internet provider, but the failure does not seem to be confirmed.
  
  Thank you.
- R_P_M
  
  10 days ago
  
  Reported - view
  In the settings page of my.nextdns.io Turn off "EDNS"
  
  or Turn on "EDNS" if it is already off.
  
  Then try problem domain again.
- t_k
  
  9 days ago
  
  Reported - view
  I tried to turn off all NextDNS-specific functions, including that attempt, but the situation did not improve.
  
  I feel like it has improved slightly when the block page display is enabled, but it is not perfect.
  
  Thank you.
- t_k
- 8 days ago
- Reported - view
This is additional information.

I contacted the Internet provider and had it verified.

In the verification of the Internet provider, it was confirmed that both NextDNS and AdGuard DNS ping to netsuper.rakuten.co.jp was successful or failed.

No failure was confirmed with Google's public DNS.

It seems that Internet providers do not filter or restrict communication on their own lines.

It is a problem on the external DNS side with ad blocking and tracker blocking functions, and it is difficult to verify and identify the cause of the failure further.

This topic may no longer be appropriate because it is not a NextDNS-specific issue because similar problems have been identified in AdGuard DNS.

Thank you very much.
- t_k
- 5 days ago
- Reported - view
I solved it myself.

It seems that the problem was solved by setting 8.8.8.8 and 8.8.4.4 to the Internet-side DNS of the Wi-Fi router and the LAN-side DHCP server DNS.

Content aside

5 days agoLast active
11Replies
145Views
3 Following

You may not be able to access the site when NextDNS is enabled

11 replies

Content aside

Home

Tags