0

IPv4 + Linked IP stopped associating with my NextDNS profile since August 8

Hi everyone,

 

I’ve been using NextDNS through my router with the IPv4 resolvers:

 

- "45.90.28.184"

- "45.90.30.184"

 

This setup worked perfectly before August 8, 2026.

 

Since then, the DNS requests still reach NextDNS successfully, but my profile is no longer associated with the requests.

 

For example, "test.nextdns.io" returns:

 

status: ok

protocol: DOT

client: 116.75.209.92

srcIP: 116.75.209.92

destIP: 45.90.28.184

server: vultr-del-1

clientName: unknown-dot

 

The important part is that the "profile" field is missing.

 

My Linked IP is still showing as successfully linked in the NextDNS dashboard.

 

I also tested this on multiple devices connected to the same router, so it doesn't appear to be device-specific.

 

Interestingly, when I switch to DNS-over-TLS using my Configuration ID, it immediately works:

 

status: ok

protocol: DOT

profile: fpc675e87509423ae5

client: 116.75.209.92

srcIP: 116.75.209.92

destIP: 139.84.176.72

server: vultr-del-1

clientName: unknown-dot

 

So the profile itself is fine, and DoT works. The problem seems specific to IPv4 + Linked IP profile association.

 

Has anyone else experienced this since around August 8? Was there a change or issue with Linked IP / IPv4 profile detection around that time?

 

Any ideas or information would be appreciated.

1 reply

null
    • Mike_V
    • 2 hrs ago
    • Reported - view

    Your first test indicates that DNS over TLS (DOT) is also being used, and the profile is supposed to be specified as part of the DoT hostname, regardless of the originating IP address. I'm pretty sure that the linked IP address is just for unencrypted DNS lookups, since there's no way to specify a profile in that kind of lookup. Maybe your router got a firmware update and is now using DoT to make its connections when possible?

Content aside

  • 2 hrs agoLast active
  • 1Replies
  • 27Views
  • 1 Following