ISP Filtering Cloudflare DNS?

Trying to figure out if Frontier is hijacking my DNS queries. Currently, my router is set to the default ISP DNS (Frontier), and my Mac is using Cloudflare DNS servers (1.1.1.2, 1.0.0.2, 2606:4700:4700::1112, 2606:4700:4700::1002). When I do a traceroute, DNS doesn’t appear to resolve to those addresses, only to Frontier’s. When WARP on my Mac is enabled, Frontier is completely cut out of the picture.

I’d love to enable WARP everywhere once it can be done at the router, not the host.

Google traceroute:
traceroute: Warning: www.google.com has multiple addresses; using 172.253.124.104
traceroute to www.google.com (172.253.124.104), 64 hops max, 52 byte packets
1 192.168.7.1 (192.168.7.1) 4.561 ms 4.864 ms 2.038 ms
2 * * *
3 te1-1-0-5—0.lcr01.clwr.fl.frontiernet.net (172.99.52.114) 8.904 ms
172.99.45.150 (172.99.45.150) 10.664 ms
172.99.45.148 (172.99.45.148) 8.480 ms
4 ae7—0.scr01.mias.fl.frontiernet.net (74.40.3.69) 13.481 ms 11.864 ms
ae8—0.scr02.mias.fl.frontiernet.net (74.40.3.73) 19.177 ms
5 ae0—0.cbr01.mias.fl.frontiernet.net (74.40.1.22) 17.450 ms
ae1—0.cbr01.mias.fl.frontiernet.net (74.40.1.126) 18.830 ms 16.836 ms
6 74.43.94.93 (74.43.94.93) 11.827 ms 11.827 ms 13.833 ms
7 * * *
8 108.170.249.1 (108.170.249.1) 15.992 ms 13.539 ms
216.239.46.140 (216.239.46.140) 14.606 ms
9 108.170.249.13 (108.170.249.13) 16.146 ms
108.170.253.18 (108.170.253.18) 18.739 ms 17.581 ms
10 142.250.212.10 (142.250.212.10) 19.113 ms 15.570 ms
209.85.246.13 (209.85.246.13) 12.954 ms
11 142.250.226.240 (142.250.226.240) 33.041 ms 29.055 ms *
12 108.170.230.67 (108.170.230.67) 45.817 ms
108.170.230.92 (108.170.230.92) 29.231 ms 29.323 ms
13 209.85.242.161 (209.85.242.161) 28.884 ms
72.14.238.133 (72.14.238.133) 29.570 ms
209.85.250.161 (209.85.250.161) 39.079 ms
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 172.253.124.104 (172.253.124.104) 33.062 ms 28.680 ms 30.142 ms

When I turn on Cloudflare WARP 1.1.1.1 on my Mac, I get this:

traceroute to www.google.com (172.217.3.68), 64 hops max, 52 byte packets

1 172.16.0.1 (172.16.0.1) 14.079 ms 13.777 ms 14.398 ms

2 108.162.210.1 (108.162.210.1) 28.062 ms 13.516 ms 15.333 ms

3 ix-ae-49-0.tcore2.mln-miami.as6453.net (63.243.152.184) 15.783 ms 13.093 ms 14.207 ms

4 72.14.215.97 (72.14.215.97) 14.243 ms 14.570 ms 14.718 ms

5 108.170.249.1 (108.170.249.1) 16.646 ms 15.694 ms 15.819 ms

6 142.250.58.103 (142.250.58.103) 16.548 ms

142.250.60.143 (142.250.60.143) 17.486 ms 14.652 ms

7 mia07s54-in-f4.1e100.net (172.217.3.68) 16.246 ms 13.854 ms 13.736 ms–

Cloudflare’s tool returns this without WARP

https://1.1.1.1/help#eyJpc0NmIjoiTm8iLCJpc0RvdCI6Ik5vIiwiaXNEb2giOiJObyIsInJlc29sdmVySXAtMS4xLjEuMSI6IlllcyIsInJlc29sdmVySXAtMS4wLjAuMSI6IlllcyIsInJlc29sdmVySXAtMjYwNjo0NzAwOjQ3MDA6OjExMTEiOiJObyIsInJlc29sdmVySXAtMjYwNjo0NzAwOjQ3MDA6OjEwMDEiOiJObyIsImRhdGFjZW50ZXJMb2NhdGlvbiI6Ik1JQSIsImlzV2FycCI6Ik5vIiwiaXNwTmFtZSI6IlBhY2tldCBIb3N0IiwiaXNwQXNuIjoiNTQ4MjUifQ==

With WARP

https://1.1.1.1/help#eyJpc0NmIjoiWWVzIiwiaXNEb3QiOiJObyIsImlzRG9oIjoiWWVzIiwicmVzb2x2ZXJJcC0xLjEuMS4xIjoiWWVzIiwicmVzb2x2ZXJJcC0xLjAuMC4xIjoiWWVzIiwicmVzb2x2ZXJJcC0yNjA2OjQ3MDA6NDcwMDo6MTExMSI6IlllcyIsInJlc29sdmVySXAtMjYwNjo0NzAwOjQ3MDA6OjEwMDEiOiJZZXMiLCJkYXRhY2VudGVyTG9jYXRpb24iOiJNSUEiLCJpc1dhcnAiOiJObyIsImlzcE5hbWUiOiJDbG91ZGZsYXJlIiwiaXNwQXNuIjoiMTMzMzUifQ==

@roger.benson thanks for your support. Have you tried reaching out to the ISP about this connectivity issue to 1.1.1.1 ? Sometimes it can be an oversight.