Yes, there are other methods besides using a VPN to influence your ISP's IP node routing.
Yes, there are other methods besides using a VPN to influence your ISP's IP node routing.
I'm experiencing problems mainly with this one friend who resides within the same state. When I connect as a host, the IP node frequently jumps, leading to significant packet losses. This has persisted for years. In Windows tracert, it appears the connection repeatedly goes through over 30 nodes even though we're in the same state. Any other link between us and others remains stable, and our bufferbloat tests are consistently "A" grade.
It’s unlikely to be useful, though occasionally switching your DNS provider might alter your routing. Your ISP will assign addresses via DHCP, which will likely configure their DNS server for name-to-address changes. You could manually adjust your DHCP settings to use services like OpenDNS, and this might lead to an alternative route being employed unintentionally. Even if the path changes, the problematic aspect remains. There are typically many hops between a home network and the ISP’s system through local areas before reaching the main backbone; if any node fails, the ISP must fix it—good luck with that!
DNS only matters when a site name resolves to several IP addresses. You can check various DNS settings with a basic nslookup command by entering the server's IP address at the end. Everything depends on the level of virtualization. In the straightforward scenario, a physical server always maintains the same IP regardless of the DNS used. With cloud services, you can request the same DNS and receive different IP addresses randomly, while using different servers yields distinct IPs. Ultimately, the route to any specific IP remains consistent unless events like a fiber cut alter it, redirecting traffic to an alternate path. The number of hops is less significant than the overall latency. Today’s equipment often minimizes router-induced delays, making them hard to detect. Additionally, the route to a website can differ greatly from the return path. To understand this better, you’d need to trace the path using tools like tracert from your server to your IP address. Exploring ISP routers and using services such as looking glass sites can reveal more about the actual routing tables. You can only adjust settings if you’re curious, as changes won’t resolve existing problems.