This router allows DNS configuration, but not DHCP. However it seems to be curiously reluctant to respond to some DNS requests from Linux hosts, including Debian running under WSL on Windows, when DNS is redirected to the Pi-hole. I get
bill@Cynthia:~$ dig @192.168.1.254 google.com
; <<>> DiG 9.10.3-P4-Debian <<>> @192.168.1.254 google.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 7016
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;google.com. IN A
;; ANSWER SECTION:
google.com. 249 IN A 216.58.211.174
;; Query time: 4 msec
;; SERVER: 192.168.1.254#53(192.168.1.254)
;; WHEN: Sun Jun 23 13:05:55 BST 2019
;; MSG SIZE rcvd: 55
bill@Cynthia:~$ dig @192.168.1.254 raspberrypi.org
;; Truncated, retrying in TCP mode.
;; Connection to 192.168.1.254#53(192.168.1.254) for raspberrypi.org failed: connection refused.
The fix is to redirect DNS to the pi-hole. Under WSL the first line of resolv.conf says remove this line to stop the file being rewritten by WSL, so I changed it to point to the pi-hole and removed the first line...
bill@Cynthia:~$ cat /etc/resolv.conf
nameserver 192.168.1.253
search lan
This works fine. On a Pi running Debian stretch the fix is to add an entry at the end of dhcpcd.conf...
pi@catherine:~ $ tail /etc/dhcpcd.conf
# fallback to static profile on eth0
#interface eth0
#fallback static_eth0
static domain_name_servers=192.168.1.253