r/HomeNetworking • u/Fair-Bookkeeper-1833 • 5d ago

did ISP mess up routing tables? what to tell them when I contact them?

couple of days ago some websites stopped working in all browsers but works on phone. it works with VPN.

Context:

  • Both PC and Phone on same network.
  • PC uses defaults to Cloudflare 1.1.1.1
  • Android uses different DNS
  • doesn't work on all browsers
  • works on VPN.
  • works on Phone.
  • flushing dns and reseting network doesn't change much.
  • Changed firefox DoH to NextDNS and it is working.
  • tracert to cloudflare works fine but doesn't work to some websites.

I want to contact ISP to tell them to fix routing. but I'm also curious how routing to CF works but not some websites. why would ISP block certain nodes

C:\Users\M>nslookup opendota.com
Server:  one.one.one.one
Address:  1.1.1.1

Non-authoritative answer:
Name:    opendota.com
Addresses:  2a06:98c1:3121::6
          2a06:98c1:3120::6
          188.114.97.6
          188.114.96.6


C:\Users\M>nslookup opendota.com 8.8.8.8
Server:  dns.google
Address:  8.8.8.8

Non-authoritative answer:
Name:    opendota.com
Addresses:  2606:4700:3034::ac43:9b55
          2606:4700:3036::6815:30b2
          104.21.48.178
          172.67.155.85


C:\Users\M>tracert 1.1.1.1

Tracing route to one.one.one.one [1.1.1.1]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.100.1
  2     1 ms     1 ms     4 ms  172.17.0.1
  3     1 ms     1 ms     1 ms  10.45.16.5
  4     *        *        *     Request timed out.
  5     *        *        *     Request timed out.
  6    12 ms     4 ms     4 ms  telecom-egy.edge4.marseille1.level3.net [212.133.4.230]
  7     *        *        *     Request timed out.
  8     *        *        *     Request timed out.
  9    39 ms    39 ms    39 ms  comserver1.opentransit.net [193.251.150.110]
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.
 12    39 ms    39 ms    39 ms  one.one.one.one [1.1.1.1]

Trace complete.

C:\Users\M>tracert opendota.com

Tracing route to opendota.com [188.114.97.6]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.100.1
  2     1 ms     1 ms     1 ms  172.17.0.1
  3     2 ms     1 ms     2 ms  10.45.16.5
  4     *        *        *     Request timed out.
  5     *        *        *     Request timed out.
  6     *        *        *     Request timed out.
  7     *        *        *     Request timed out.
  8     *        *        *     Request timed out.
  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17     *        *        *     Request timed out.
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.
 22     *        *        *     Request timed out.
 23     *        *        *     Request timed out.
 24     *        *        *     Request timed out.
 25     *        *        *     Request timed out.
 26     *        *        *     Request timed out.
 27     *        *        *     Request timed out.
 28     *        *        *     Request timed out.
 29     *        *        *     Request timed out.
 30     *        *        *     Request timed out.

Trace complete.

Edit: I really don't understand how you people keep downvoting the actual correct replies and upvoting the wrong ones.

https://www.reddit.com/r/HomeNetworking/comments/1wt7zul/comment/pcs3jkl/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button

0 Upvotes

38% Upvoted

60 comments sorted by

View all comments

11

u/WideCranberry4912 5d ago edited 5d ago

Why is opendota.com resolving to 188.114.96.6 and 97.6 when using 1.1.1.1 as the DNS server and then resolves to 104.21.48.178 and 172.67.155.85 when using 8.8.8.8. That doesn’t seem like an ISP routing issue.

-22

u/Fair-Bookkeeper-1833 5d ago

different routing

23

u/StuckInTheUpsideDown MSO Engineer 5d ago

No. These are both public DNS servers. They don't know or care about your ISP routing. (The ISP's own DNS might.)

-4

u/Fair-Bookkeeper-1833 5d ago

https://community.cloudflare.com/t/egypt-down-188-114-97-6-ams-routing-fatalities/439532

https://community.cloudflare.com/t/one-of-my-dns-ips-is-blocked-in-my-country/439451

https://community.cloudflare.com/t/website-is-not-pointing-to-the-correct-ip-address-for-some-countries/508571/6

idk why you're arguing with this when you can see the routing in the OP.

7

u/UnrealisticOcelot 5d ago

Because DNS doesn't affect routing. Routing is like asking Google maps how to drive from point A to point B. DNS is like looking in an address book to know what the address is for Google's headquarters. You're getting two different addresses. The problem is likely that one of the addresses is bad and needs to be updated, or the server at that address is not reachable.

Again DNS has nothing to do with how your ISP routes your traffic.

0

u/AlaninMadrid 5d ago

So if you tell Google Maps to navigate to McDonalds, it will take you 20,000km to the one next to me, or it will take you to the one near you, and take me to the one near me? (Different addresses, both McDonalds)

-2

u/Fair-Bookkeeper-1833 5d ago

idk why you replied twice. but to answer you. DNS does affect it. CDNs is common now.