[opensuse] site TLD
I installed an openSUSE Linux PC some time ago (around 2010, some configuration files may be older). openSUSE automatically created a hostname "linux-xxxx" with the TLD "site", so the local FQDN ("hostname -f") is "linux-xxxx.site". The problem is, that my Sendmail mail server has address rewriting problems since today. After debugging a bit, I found, that my provider resolves "linux-xxxx.site" as 127.0.53.53". # host linux-xxxx.site linux-xxxx.site has address 127.0.53.53 linux-xxxx.site mail is handled by 10 your-dns-needs-immediate-attention.site. See NAME COLLISION OCCURRENCE ASSESSMENT* *http://newgtlds.icann.org/sites/default/files/agreements/name-collision-asse... My questions: If *.site doesn't work anymore as a valid local domain, what is a good alternative name? Is there any warning from openSUSE for affected systems? Greetings, Björn -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Bjoern Voigt wrote:
I installed an openSUSE Linux PC some time ago (around 2010, some configuration files may be older).
openSUSE automatically created a hostname "linux-xxxx" with the TLD "site", so the local FQDN ("hostname -f") is "linux-xxxx.site".
The problem is, that my Sendmail mail server has address rewriting problems since today. After debugging a bit, I found, that my provider resolves "linux-xxxx.site" as 127.0.53.53".
# host linux-xxxx.site linux-xxxx.site has address 127.0.53.53 linux-xxxx.site mail is handled by 10 your-dns-needs-immediate-attention.site.
Right, I get exactly the same. Looks like the '.site' TLD has gone on-line ??
My questions: If *.site doesn't work anymore as a valid local domain, what is a good alternative name?
.local or .bjoernvoigt or .anythingelseyoucanthinkup Mind you, your /etc/hosts should have the appropriate .site entries for your mailserver. -- Per Jessen, Zürich (9.1°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Per Jessen wrote:
Bjoern Voigt wrote:
My questions: If *.site doesn't work anymore as a valid local domain, what is a good alternative name?
.local or .bjoernvoigt or .anythingelseyoucanthinkup
Mind you, your /etc/hosts should have the appropriate .site entries for your mailserver.
Thank you. ".local" is OK. My DSL router suggests ".lan". I will probably use the same TLD and the same hostnames on my router and on my PCs. /etc/hosts is not enough. The hostname occurs here: /etc/hostname /etc/HOSTNAME /etc/resolv.conf /etc/hosts /etc/sendmail.cf [...] Greetings, Björn -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2015-03-16 22:23, Bjoern Voigt wrote:
Per Jessen wrote:
Bjoern Voigt wrote:
My questions: If *.site doesn't work anymore as a valid local domain, what is a good alternative name?
.local or .bjoernvoigt or .anythingelseyoucanthinkup
Mind you, your /etc/hosts should have the appropriate .site entries for your mailserver.
Thank you. ".local" is OK. My DSL router suggests ".lan". I will probably use the same TLD and the same hostnames on my router and on my PCs.
Warning: .local is a bad choice if you ever pretend to connect to a Windows domain server. It is incompatible with... er... I can't remember the name now... sigh. Ah, zeroconf: https://bugs.launchpad.net/ubuntu/+source/likewise-open/+bug/205236 https://bugzilla.novell.com/show_bug.cgi?id=747939 I'd use .lnet, for a short one, or .localnet. .lan is probably a good choice. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlUHTZcACgkQja8UbcUWM1zDpQD/TVJMmeQLuV6aKIIdWZ07Gj1F uKJd42eXccJJOM/0ULsA/08enIctnbnYBsNMtnbha2T/EV+YIiTIAoQq4XGcthmu =4P4A -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Bjoern Voigt wrote:
Per Jessen wrote:
Bjoern Voigt wrote:
My questions: If *.site doesn't work anymore as a valid local domain, what is a good alternative name?
.local or .bjoernvoigt or .anythingelseyoucanthinkup
Mind you, your /etc/hosts should have the appropriate .site entries for your mailserver.
Thank you. ".local" is OK. My DSL router suggests ".lan". I will probably use the same TLD and the same hostnames on my router and on my PCs.
/ /etc/hosts is not enough. The hostname occurs here:
/etc/hostname /etc/HOSTNAME /etc/resolv.conf /etc/hosts /etc/sendmail.cf [...]
Assuming you don't run a local nameserver, my point is that /etc/hosts is enough for your name resolution. If you have your three hosts "tom.site", "dick.site" and "harry.site" listed in /etc/hosts on all your machines, none of them should have reason to do external lookups for those hosts. -- Per Jessen, Zürich (6.0°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Per Jessen wrote:
Bjoern Voigt wrote:
Per Jessen wrote:
Bjoern Voigt wrote:
My questions: If *.site doesn't work anymore as a valid local domain, what is a good alternative name?
.local or .bjoernvoigt or .anythingelseyoucanthinkup
Mind you, your /etc/hosts should have the appropriate .site entries for your mailserver.
Thank you. ".local" is OK. My DSL router suggests ".lan". I will probably use the same TLD and the same hostnames on my router and on my PCs.
/ /etc/hosts is not enough. The hostname occurs here:
/etc/hostname /etc/HOSTNAME /etc/resolv.conf /etc/hosts /etc/sendmail.cf [...]
Assuming you don't run a local nameserver, my point is that /etc/hosts is enough for your name resolution. If you have your three hosts "tom.site", "dick.site" and "harry.site" listed in /etc/hosts on all your machines, none of them should have reason to do external lookups for those hosts.
I am not sure about the technical details. But my local Sendmail server does Nameserver lookups. This Sendmail feature is called "Canonify". It translates incomplete mail addresses like anton@server1 or anton@localhost to something like anton@server1.site. I disabled this feature partially with FEATURE(`nocanonify', `canonify_hosts')dnl Documentation from /usr/share/sendmail/README If `canonify_hosts' is specified as parameter, i.e., FEATURE(`nocanonify', `canonify_hosts'), then addresses which have only a hostname, e.g., <user@host>, will be canonified (and hopefully fully qualified), too. Now I changed the hostname and domain with Yast (with results in /etc/hosts, /etc/HOSTNAME etc.) and in my router settings. I changed the local "site" domain to something else and everything works. Greetings, Björn -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Bjoern Voigt wrote:
Per Jessen wrote:
Bjoern Voigt wrote:
Per Jessen wrote:
Bjoern Voigt wrote:
My questions: If *.site doesn't work anymore as a valid local domain, what is a good alternative name?
.local or .bjoernvoigt or .anythingelseyoucanthinkup
Mind you, your /etc/hosts should have the appropriate .site entries for your mailserver.
Thank you. ".local" is OK. My DSL router suggests ".lan". I will probably use the same TLD and the same hostnames on my router and on my PCs.
/ /etc/hosts is not enough. The hostname occurs here:
/etc/hostname /etc/HOSTNAME /etc/resolv.conf /etc/hosts /etc/sendmail.cf [...]
Assuming you don't run a local nameserver, my point is that /etc/hosts is enough for your name resolution. If you have your three hosts "tom.site", "dick.site" and "harry.site" listed in /etc/hosts on all your machines, none of them should have reason to do external lookups for those hosts.
I am not sure about the technical details. But my local Sendmail server does Nameserver lookups. This Sendmail feature is called "Canonify". It translates incomplete mail addresses like anton@server1 or anton@localhost to something like anton@server1.site.
Hi Björn I am not familiar with sendmail, but with postfix canonicalisation would not lead to any dns lookups. It is a plain text substitution.
Now I changed the hostname and domain with Yast (with results in /etc/hosts, /etc/HOSTNAME etc.) and in my router settings. I changed the local "site" domain to something else and everything works.
Good stuff. -- Per Jessen, Zürich (5.8°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Per Jessen wrote:
.local or .bjoernvoigt or .anythingelseyoucanthinkup
Mind you, your /etc/hosts should have the appropriate .site entries for your mailserver.
I read the following article about the .local TLD: http://en.wikipedia.org/wiki/.local In the article, there are two warnings: "Networking device hostnames ending with .local are often employed in private networks, where they are resolved either via the multicast domain name service (mDNS) and/or local Domain Name System (DNS) servers. The implementation of both approaches on the same network can be problematic" "The connection of Macintosh and Linux computers and/or zeroconf peripherals to Windows networks can be problematic if those networks include name servers that use .local as a search domain for internal devices" In my network and in many others these conditions apply (mixed local DNS from router and Bonjour; Linux and Windows). What do you think? Should I avoid ".local"? Greetings, Björn -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Mon, 16 Mar 2015 22:42, Bjoern Voigt <bjoernv@...> wrote:
Per Jessen wrote:
.local or .bjoernvoigt or .anythingelseyoucanthinkup
Mind you, your /etc/hosts should have the appropriate .site entries for your mailserver.
I read the following article about the .local TLD:
http://en.wikipedia.org/wiki/.local
In the article, there are two warnings:
"Networking device hostnames ending with .local are often employed in private networks, where they are resolved either via the multicast domain name service (mDNS) and/or local Domain Name System (DNS) servers. The implementation of both approaches on the same network can be problematic"
"The connection of Macintosh and Linux computers and/or zeroconf peripherals to Windows networks can be problematic if those networks include name servers that use .local as a search domain for internal devices"
In my network and in many others these conditions apply (mixed local DNS from router and Bonjour; Linux and Windows).
What do you think? Should I avoid ".local"?
Well, how much "extra" work would you like the next time someone has the "brilliant" idea to make a hence optional service a needed "feature" that has to "absolutely" use ".local" as tld? IMHO, spare yourself the pain in the backside and do NOT use ".local" for naming your boxes via DNS / DHCP. As said above, it is "reserved" for mDNS" use. ATM ".lnet", or fully personalized ".bjoernvoigt" is better in your case. Personally, I'd avoid even ".lan", who knows the next brain-dead idea someone with more money and/or influence than foresight has... - Yamaban. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (4)
-
Bjoern Voigt -
Carlos E. R. -
Per Jessen -
Yamaban