[issue35164] socket.getfqdn and socket.gethostbyname fail on MacOS

Sorin Sbarnea added the comment: Maybe I should mention that my networking is configured only with values received from the DHCP server, which includes 2 DNS servers, one ipv4 an done ipv6, both of them being the local router and *1* search domain, which is a real domain (not local). --

[issue35164] socket.getfqdn and socket.gethostbyname fail on MacOS

Sorin Sbarnea added the comment: I am able to reproduce this bug with Python 3.10 on MacOS 12.2 too, and I happen to have some extra insights about what happens, see https://github.com/tox-dev/tox/issues/2375 Basically the culprit is a reverse-dns query (PTR) that takes 30s to return, causi

[issue35164] socket.getfqdn and socket.gethostbyname fail on MacOS

George Hickman added the comment: I came across this today with the same timeout behaviour on macOS 10.14.6. After some digging I tracked it down to the Search Domains setting of my local network, this was set to "local", removing that immediately fixed the issue. -- nosy: +ghickman

[issue35164] socket.getfqdn and socket.gethostbyname fail on MacOS

Ronald Oussoren added the comment: >>My gut feeling is that this is some issue with your system or environment. > I Doubt it, happens with another MacBook air which is literally out of the > box, no mods. But on the other hand most other users (including myself and Ned) don't have this prob

[issue35164] socket.getfqdn and socket.gethostbyname fail on MacOS

James Crowther added the comment: Hi Ronald, I've replied to your comments below >My gut feeling is that this is some issue with your system or environment. I Doubt it, happens with another MacBook air which is literally out of the box, no mods. >Some more questions: >- Is this is a cons

[issue35164] socket.getfqdn and socket.gethostbyname fail on MacOS

Ronald Oussoren added the comment: This issue does not have enough information to determine what is wrong. It is however fairly clear that it is not related to "scutil --get HostName" mentioning that there is no hostname set as that is the normal state of systems, and I have never run into t

[issue35164] socket.getfqdn and socket.gethostbyname fail on MacOS

James Crowther added the comment: Hi guys, I am the OP for the stack overflow issue question that sparked this bug report. In response to Ned's question about configuration of the system: MacOS 10.14.1 Installed x-code and command line tools python versions used, varies, 3.5.3, 3.6 and 3.7

[issue35164] socket.getfqdn and socket.gethostbyname fail on MacOS

Ronald Oussoren added the comment: I agree with Ned. The code fragment works for me as well on 10.14.1 and I've used simular code in the past on different versions of macOS as well. @ssbarnea: - What is the hostname as shown in the "Sharing" preference pane? Does the name include special ch

[issue35164] socket.getfqdn and socket.gethostbyname fail on MacOS

Ned Deily added the comment: See also Issue29705. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https:/

[issue35164] socket.getfqdn and socket.gethostbyname fail on MacOS

Ned Deily added the comment: Thanks for the report but I don't think the problem you are seeing is that simple. On my 10.14.1 system, I don't see that problem: $ scutil --get HostName HostName: not set $ /usr/local/bin/python3.7 Python 3.7.1 (v3.7.1:260ec2c36a, Oct 20 2018, 03:13:28) [Clang

[issue35164] socket.getfqdn and socket.gethostbyname fail on MacOS

New submission from Sorin Sbarnea : It seems that when the MacOS machine does not have a FQDN name manually configured using `scutil`, python will be fail to resolve domain names and timeout after ~30 seconds. I mention that the DNS resolution works correctly on the machine and that the DHCP