DNS 1.1.1.1 not working

I performed a debug test through https://1.0.0.1/help and found that only DNS 1.0.0.1 is working; also when typing 1.1.1.1 in browser address bar I get access denied message.
Notes: DNS 1.1.1.1 only works when bound with WARP; I contacted my ISP and they told me that there is no impediment for them to access 1.1.1.1; I checked the route and everything is ok.

Sepuration:
https://1.0.0.1/help#eyJpc0NmIjoiWWVzIiwiaXNEb3QiOiJObyIsImlzRG9oIjoiWWVzIiwicmVzb2x2ZXJJcC0xLjEuMS4xIjoiTm8iLCJyZXNvbHZlcklwLTEuMC4wLjEiOiJZZXMiLCJyZXNvbHZlcklwLTI2MDY6NDcwMDo0NzAwOjoxMTExIjoiTm8iLCJyZXNvbHZlcklwLTI2MDY6NDcwMDo0NzAwOjoxMDAxIjoiTm8iLCJkYXRhY2VudGVyTG9jYXRpb24iOiJHUlUiLCJpc1dhcnAiOiJObyIsImlzcE5hbWUiOiJDbG91ZGZsYXJlIiwiaXNwQXNuIjoiMTMzMzUifQ==

Images:
Captura de Tela (8)

169.254.2.x is a private IP address space I believe. If you compare that route to the route for 1.0.0.1 I think you will see very different results.

If it isn’t an ISP issue it looks like it could be an issue of your local network instead.

1 Like

Indeed. It’s within the IPv4 link local allocation. RFC 6890 - Special-Purpose IP Address Registries


It really was different. But how could I fix this problem if it’s on a local network?

Could it be a problem related to the configuration of the router or modem?

It is possible that your ISP is misusing the 1.1.1.1 address on their network. It wouldn’t be the first time such a thing has been observed.

In my case the router was configured by myself and the modem was configured by them. That’s why I wanted to know if it would be a problem of the ISP itself or a misconfiguration on my part.

It could be problem in CPE firmware. There was such a case on the AT&T network.

1 Like

The modem was left in bridge mode by the carrier and the router I can try to update the firmware.
Sorry! I’m still learning some networking concepts and I see that there’s a lot to learn in this field.

I found that Cloudflare DNS 1.1.1.1 is not working on any of my devices connected to my home network.
I was guided to contact the ISP in the previous topic, but they said there is no impediment regarding DNS 1.1.1.1.

Debug: https://1.0.0.1/help#eyJpc0NmIjoiWWVzIiwiaXNEb3QiOiJObyIsImlzRG9oIjoiWWVzIiwicmVzb2x2ZXJJcC0xLjEuMS4xIjoiTm8iLCJyZXNvbHZlcklwLTEuMC4wLjEiOiJZZXMiLCJyZXNvbHZlcklwLTI2MDY6NDcwMDo0NzAwOjoxMTExIjoiTm8iLCJyZXNvbHZlcklwLTI2MDY6NDcwMDo0NzAwOjoxMDAxIjoiTm8iLCJkYXRhY2VudGVyTG9jYXRpb24iOiJDRkMiLCJpc1dhcnAiOiJObyIsImlzcE5hbWUiOiJDbG91ZGZsYXJlIiwiaXNwQXNuIjoiMTMzMzUifQ==

Comments:

  1. When typing 1.1.1.1 in my browser’s address bar, it gives me access denied;
  2. Only DNS 1.0.0.1 works normally;
  3. DNS 1.1.1.1 only works with WARP;
  4. Running the command tracert 1.1.1.1 and tracert 1.0.0.1 I got:

If anyone can help me out by telling me possible causes of the problem or excluding non-pertinent causes. Thank you very much for any information, as it may lead me to the solution.

It’s still either your ISP or your modem blocking access to 1.1.1.1. As after 169.254.0.3 it should reach the internet, but it does not. I’d say contact your ISP again and ask for the technical support that can understand these traceroutes.

Which modem do you have BTW?

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.