21–30 of 31 posts
Given the number of people that still can't route to 1.1.1.1, this is an interesting backup!
Interested to see who that might be, it seems a bit nuts that that wouldn't work.
Great! Now the whole world can see which domains you are interested in. This is supposed to be some last resort backup when all other DNS servers (8.8.8.8 and others) are down or blocked? In that extreme case of unavailability, what is the guarantee that local Govt is not involved and Twitter and/or sms to Twitter is not blocked. Am I missing any use case here?
Info on 1.1.1.1: https://blog.cloudflare.com/announcing-1111/
How do you get a query to through?
Tweet to @1111Resolver followed by the DNS Record type and the Domain Name. Example: @1111Resolver A http://google.com
Earlier quoted context omitted.
Interested to see who that might be, it seems a bit nuts that that wouldn't work.
I mentioned this in the other thread yesterday, but my AT&T gigapower router is hard coded with 1.1.1.1 on an internal interface, so I can't use it. I can still use 1.0.0.1 though.
Wow, AT&T of all people should know better. I mean, I understand the attraction to that address for customer setup reasons, and bypassing different configured NAT address ranges (i.e. 10/8, 172.16/12, and 192.168/16 networks), but surely a customer who configures a custom address range would be capable of finding the new address.
Here's hoping that as IPv6 becomes ubiquitous, this is replaced broadly with something standard, possibly based on ND.
Is there any difference between which address you list first in your DNS list (1.0.0.1 and 1.1.1.1)? I saw a suggestion to list 1.0.0.1 first since it likely gets much less traffic.
Earlier quoted context omitted.
I mentioned this in the other thread yesterday, but my AT&T gigapower router is hard coded with 1.1.1.1 on an internal interface, so I can't use it. I can still use 1.0.0.1 though.
> I mentioned this in the other thread yesterday, but my AT&T gigapower router is hard coded with 1.1.1.1 on an internal interface Wow, AT&T of all people should know better. I mean, I understand the attraction to that address for customer setup reasons, and bypassing different configured NAT address ranges (i.e. 10/8, 172.16/12, and 192.168/16 networks), but surely a customer who configures a custom address range wo…
Less junk traffic, less latency for folk behind CGNAT on IPv6-only mobile networks, no chance of collision with poorly a configured network equipment.
Earlier quoted context omitted.
> I mentioned this in the other thread yesterday, but my AT&T gigapower router is hard coded with 1.1.1.1 on an internal interface Wow, AT&T of all people should know better. I mean, I understand the attraction to that address for customer setup reasons, and bypassing different configured NAT address ranges (i.e. 10/8, 172.16/12, and 192.168/16 networks), but surely a customer who configures a custom address range wo…
And to help march towards ubiquity shouldn't we be encouraging IPv6-connected users to point to 2606:4700:4700::1111 Less junk traffic, less latency for folk behind CGNAT on IPv6-only mobile networks, no chance of collision with poorly a configured network equipment.
I'll try it again in another year.
Earlier quoted context omitted.
I mentioned this in the other thread yesterday, but my AT&T gigapower router is hard coded with 1.1.1.1 on an internal interface, so I can't use it. I can still use 1.0.0.1 though.
> I mentioned this in the other thread yesterday, but my AT&T gigapower router is hard coded with 1.1.1.1 on an internal interface Wow, AT&T of all people should know better. I mean, I understand the attraction to that address for customer setup reasons, and bypassing different configured NAT address ranges (i.e. 10/8, 172.16/12, and 192.168/16 networks), but surely a customer who configures a custom address range wo…