0

NextDNS added own domain to DenyList

This is very strange and frustrating.....

Today I got several calls from clients some of my websites were not being resolved e.g. web1.local.com, web2.local.com.

On further investigation, I noticed *.local.com is added to DenyList!! No one has access to NextDNS client control panel apart from myself.

I have gone to NextDNS webpage to contact support for explanation and investigation but they have no support contact details. 

For now, I have reverted to public DNS until I figure out why this happen or NextDNS support team read this post and contact me.

PS. I have a paid subscription.

I anyone has direct NextDNS contact details, please send them here.

5 replies

null
    • Chris.20
    • 9 mths ago
    • Reported - view

    It automatically get re-added to DenyList even if I manually removes it 馃槨

    • NextDNs
    • 9 mths ago
    • Reported - view

    This is definitely not something our product would do by itself. Either someone has accessed your account, or you've connected something to the API. You might want to consider changing your credentials and ensuring that you haven't given access to any of your profiles that have write permissions to someone else (Settings -> Access).

    • fmirwais8
    • 9 mths ago
    • Reported - view

    Mirwais

    • TheAliDev
    • 9 mths ago
    • Reported - view

    Add domains to whitelist , bro use common sense 

      • Chris.20
      • 9 mths ago
      • Reported - view

       Wow, brilliant idea champ!

Content aside

  • 9 mths agoLast active
  • 5Replies
  • 205Views
  • 4 Following