This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author loewis
Recipients baikie, ezio.melotti, jesterKing, lemburg, loewis, r.david.murray, vstinner
Date 2010-10-29.22:25:22
SpamBayes Score 1.0032675e-10
Marked as misclassified No
Message-id <>
In-reply-to <>
> The DNS name of the Windows machine is the combination of the DNS host
> name and the DNS domain that you setup on the machine. I think the
> misunderstanding is that you assume this combination will
> somehow appear as known DNS name of the machine via some
> DNS server on the network - that's not the case.

I don't assume that - I merely point it that it clearly has no
relationship to the DNS (unless you explicitly make it that way).
So, I wonder why they call it the DNS name - they could have just
as well called the "LDAP name", or the "NIS name". In either case,
setting the name would have no impact on the respective naming

> FWIW, you can do the same on a Linux box, i.e. setup the host name
> and domain to some completely bogus values. And as David pointed out,
> without also updating the /etc/hosts on the Linux, you always get the
> resolver error with hostname -f I mentioned earlier on (which does
> a DNS lookup), so there's no real connection to the DNS system on
> Linux either.

Yes, but Linux (rightly) calls it the "hostname", not the "DNS name".
Date User Action Args
2010-10-29 22:25:24loewissetrecipients: + loewis, lemburg, vstinner, baikie, ezio.melotti, r.david.murray, jesterKing
2010-10-29 22:25:22loewislinkissue9377 messages
2010-10-29 22:25:22loewiscreate