[issue42092] test_host_resolution_bad_address does not always fail as expected

Gregory P. Smith added the comment: Rule #1 for home users: Never use your ISPs DNS. Always configure a reputable one in your router. If you can't control your router, configure your computer to ignore the router's DNS. Classic best in breed non-ISP servers exist: 8.8.8.8 (google),

[issue42092] test_host_resolution_bad_address does not always fail as expected

Change by Barry A. Warsaw : -- pull_requests: +27351 pull_request: https://github.com/python/cpython/pull/29085 ___ Python tracker ___

[issue42092] test_host_resolution_bad_address does not always fail as expected

Barry A. Warsaw added the comment: Woot! I finally figured out the problem and how to fix it. It has nothing to do with Python and everything to do with AT They run a service called DNS Error Assist, quoting: "Sometimes we enter a wrong search word, or a wrong web address, or maybe the

[issue42092] test_host_resolution_bad_address does not always fail as expected

New submission from Barry A. Warsaw : This is very likely caused by something janky my ISP (AT) is doing with IPv6, but the above named test fails for me because IPv6 addresses like `::1q` do not fail to resolve as the test expects. I'm not sure what can or should be done about it, but as