[issue34105] test_socket.test_host_resolution_bad_address fails on Mac OS X 10.13.6

Change by Ronald Oussoren : -- stage: -> resolved status: pending -> closed ___ Python tracker ___ ___ Python-bugs-list mailing

[issue34105] test_socket.test_host_resolution_bad_address fails on Mac OS X 10.13.6

Ronald Oussoren added the comment: For some reason your system resolves invalid names, likely due to some upstream nameserver misbehaving. Is your Internet provider T-Online in Germany? The address 62.138.239.45 is registered to that company, the IP address also appears to host some kind of

[issue34105] test_socket.test_host_resolution_bad_address fails on Mac OS X 10.13.6

Lysandros Nikolaou added the comment: When running the terminal command host '0.1.1.~1' I get the following output: 0.1.1.~1 has address 62.138.239.45 0.1.1.~1 has address 62.138.238.45 Host 0.1.1.~1 not found: 3(NXDOMAIN) Host 0.1.1.~1 not found: 3(NXDOMAIN) If I ping the above IP address

[issue34105] test_socket.test_host_resolution_bad_address fails on Mac OS X 10.13.6

Change by Ronald Oussoren : -- assignee: -> ronaldoussoren ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue34105] test_socket.test_host_resolution_bad_address fails on Mac OS X 10.13.6

Ronald Oussoren added the comment: Note that the test itself has the following comment: def test_host_resolution_bad_address(self): # These are all malformed IP addresses and expected not to resolve to # any result. But some ISPs, e.g. AWS, may successfully resolve these

[issue34105] test_socket.test_host_resolution_bad_address fails on Mac OS X 10.13.6

Ronald Oussoren added the comment: This is not expected, but I don't know where the problem is. On my machine I get: >>> socket.gethostbyname('0.1.1.~1') Traceback (most recent call last): File "", line 1, in socket.gaierror: [Errno 8] nodename nor servname provided, or not known This is

[issue34105] test_socket.test_host_resolution_bad_address fails on Mac OS X 10.13.6

Change by Berker Peksag : -- components: +macOS nosy: +ned.deily, ronaldoussoren ___ Python tracker ___ ___ Python-bugs-list

[issue34105] test_socket.test_host_resolution_bad_address fails on Mac OS X 10.13.6

Lysandros Nikolaou added the comment: Is this expected behaviour, should the tests be changes, or is it a bug? -- ___ Python tracker ___

[issue34105] test_socket.test_host_resolution_bad_address fails on Mac OS X 10.13.6

New submission from Lysandros Nikolaou : On my Mac OS X 10.13.6 system test_socket.test_host_resolution_bad_address fails with the following error: == FAIL: test_host_resolution_bad_address