Feature Requests

As a relay user, I would like the ability to modify a relay instance's relay.conf file remotely from the dashboard. This would involve the ability to modify local domains in the same user experience as a roaming client, for instance.

The RELAY should be able to process LOCAL domains and a List of BLACK HOLE domains including wild carded domains / subdomains that you simply do NOT want to be processed at all. Since these will not match the local domains they will now go upstream to DNS Filter to be processed. THIS causes a huge problem for SMART TVS and apps on these TVS. A single SMART TV can generate 2 million DNS requests per month -- non of which are legitimate DNS requests. They are using DNS port 53, / 853 and DNS over TLS or HTTP to sneek an outbound packet that basically reveals WHAT YOU are watching and how long you are watching it. These packets can be a stream of continuous DNS packets going out from the TV. Everyone of these should be DROPPED before they even get to DNSFilter becasue if they go to DNSFilter then their traffic will OFFSET the sites traffic significantly thereby causing the customer license to be SHORT. A single Smart TV left on 24x7 will generate 2million DNS packets and that is the DNSFilter license traffic equivalent of about 40 users... Rather then letting this go upstream, provide a simple way to BLACK HOLE it on the DNS RELAY -- and while Im thinking of it -- WHY NOT allow for a catch all BLACK HOLE in the DNSFilter cloud that if domains are matched here there are simply DISCARDED with no DNS reply response -- thereby not counting as traffic processed by DNSFilter at all and not counted against your TRAFFIC threashold.. This is a major issue. SURE -- we can reconfigure the TVs to use 1.1.1.1 or some other DNS server, but shouldn't DNSFilter offer a soluition here - -you can not expect everyone to be savy enough to change their DNS server settings. Lets be honest, the average user of a smart TV is using IP addressing and DNS server settings pushed to their device via DHCP probably associated with their WIFI router or a telcom network end point. Users are completely oblivious to DNS servers and changing them. So we need an elegant way to just DROP this traffic at the RELAY server and also at the CLOUD level so it is just not counted. Just drop the DNS request and do not process it at all. The TV will still run and now you are PROTECTING the users of that TV so that their USER WATCHING habits are not being spied on and used for targeted advertizing. THIS IS a security and privacy issue.

Please start cooperation with Draytek so that proper DNS forwarding is implemented on firmware level of 3910 router - drayteks already have lan forwarding functionality, if i understand well only thing that needed to be added is to report the internal IP of the requesting host. Please note specifically this functionality should be secured by DoT or DoH so that does not cause dns leakage between router and dnsfilter.com

Looking for support for the DNSFilter Relay with the MicroTik equipment. Steps and or video tutorial would be nice.

DNSFilter should make a hardware device that can be plugged into a network with a static IP, configured as the DNS server, and offer DNS relay. A GUI configuration option would be great to configure relaying DNS to DNSFilter so that LAN IPs can be recorded. Ability to work across multiple VLANs would be ideal. This shouldn't be incredibly expensive as a small Pi could probably accomplish this. Supporting DoT back to DNSFilter would be an added benefit.

Create easy, smooth way to install, configure and use raspberry pi as Relay.

a simple windows service install for the relay application some of our clients do not have a way we can install a linux VM

The Deployment > Relays page already shows the status of when a Relay is successfully sending queries to DNSFilter. It would be very helpful in troubleshooting if an additional column (or two) could be added to this page to show which communication channels are correctly configured and active. Specifically, add a notification if the incoming queries are unencrypted or encrypted. In my over simplified image attachment and indicator can show if a Relay is successfully sending encrypted queries. This info can be extract by searching through the Relay logs but it's a nuisance to do it when this could be quickly added to this status page.

Let me start by saying, the DNS Filter Relay Services is our primary DNS IP used on everything. We use it too track individual DNS Requests by IP. Been using it for months now with no issues. Here is my main ask: We have many domains, and the relay does not give me control of what hits what DNS Server. It only allows for a list of dns servers and list of domains. But many are not associated in any way. Very inefficient... Can we please assign the IPs to a domain. This way the DNS request can be targeted. Example: [local_dns_server] domain.name = ["4.4.4.4","5.5.5.5"] subdomain1.domain.name = ["1.1.1.1","2.2.2.2"] Ask #2 For emergancies, can there be a fail open to a defined public dns server with email notification. [public_dns_server] fail_open = ["8.8.8.8","8.8.4.4"] email = [" email1@domain.com "," email2@domain.com "] Note: would like email from you, but if not possible, add smtp config info here as well.

I'm following the instructions to convert the virtual box file into something I can import as a vmware virtual machine. I'm not having any success. Why do you make virtual box image available? Nobody's going to want to run it there in production, are they? Isn't everyone going to either use vmware, hyper-v, or kvm for their virtualization?