0

identifying device with dnsmasq.conf

The dnsmasq.conf entries suggested for routers on the setup page includes setting 

add-cpe-id=<profile_id>

so that NextDNS can identify which profile to use when processing requests.

In the logs and analytics my router then shows up as an unknown device. I had hoped that the instructions for identifying devices for DoT and DoH would also work for the dnsmasq.conf setting so I tried

add-cpe-id=<device_name>-<profile_id>

but this does not work. The setup page said something to the effect that my device was not using a profile.

Can this be improved upon on the server side?

2 replies

null
    • R_P_M
    • 1 yr ago
    • Reported - view

    It’s just not possible to get dnsmasq to do what you want. Are there no alternatives to dnsmasq available? Otherwise you just have to accept the unknown device in the logs. 

    • Leng
    • 13 hrs ago
    • Reported - view

    i tried this and for now it is fine:

    set dnsmasq just like you want to set Nextdns only via dnsmasq(you can see it on setup page):

    no-resolv
bogus-priv
strict-order
server=XXXX:XXXX::
server=XX.XX.XX.XX
server=XXXX:XXXX::
server=XX.XX.XX.XX
add-cpe-id=XXXXXX

    then add the address#port in it like:

    no-resolv
bogus-priv
strict-order
server=127.0.0.1#XXXX
server=XXXX:XXXX::
server=XX.XX.XX.XX
server=XXXX:XXXX::
server=XX.XX.XX.XX
add-cpe-id=XXXXXX
add-mac
add-subnet=32,128

    then restart dnsmasq and cli  both.

    try it i dont know if this is reliable,but for me . it is fine for now.

Login to reply

Content aside

  • 13 hrs agoLast active
  • 2Replies
  • 354Views
  • 3 Following