Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #269509
| From | tomas@tuxteam.de |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: OpenSMTPD can't parse smarthost |
| Date | 2024-05-23 21:30 +0200 |
| Message-ID | <IHmit-floi-1@gated-at.bofh.it> (permalink) |
| References | (1 earlier) <IH8Iy-fdeG-1@gated-at.bofh.it> <IHfgZ-fh4N-3@gated-at.bofh.it> <IHkTn-fkpP-7@gated-at.bofh.it> <IHlPr-fkZp-5@gated-at.bofh.it> <IHm8N-fllo-3@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
[Multipart message — attachments visible in raw view] - view raw
On Thu, May 23, 2024 at 03:17:00PM -0400, Jeffrey Walton wrote: [...] > > If your LAN is isolated, you can basically do whatever you > > want. > > And then act surprised when networking breaks :) You just have to understand what's going on, that's all > > > And then there are "special" TLDs (.local, I'm looking at > > you) where you'll get lots of fun effects should you decide > > to use them (zeroconf, I'm looking at you :-) > > I _think_ .local is reserved for mDNS. See > <https://www.iana.org/assignments/special-use-domain-names/special-use-domain-names.xhtml>. It's a while ago -- I went through this in some $BIGCORP. Windows ops insisted in having the internal top level as .local (don't ask :-) For me it was as easy as kicking out Avahi. For the Mac users it was... interesting :-) > It looks like .internal and possibly .private are coming soon. See > <https://www.icann.org/en/public-comment/proceeding/proposed-top-level-domain-string-for-private-use-24-01-2024> > and <https://www.theregister.com/2024/01/29/icann_internal_tld/>. Whatever. Your net, your rules. Just make sure the software you use plays along (Avahi is fond of .local because of mDNS, for example). Cheers -- tomás
Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
OpenSMTPD can't parse smarthost Paul M Foster <paulf@quillandmouse.com> - 2024-05-23 03:40 +0200
Re: OpenSMTPD can't parse smarthost Paul M Foster <paulf@quillandmouse.com> - 2024-05-23 13:50 +0200
Re: OpenSMTPD can't parse smarthost <tomas@tuxteam.de> - 2024-05-23 14:00 +0200
Re: OpenSMTPD can't parse smarthost <tomas@tuxteam.de> - 2024-05-23 14:40 +0200
Re: OpenSMTPD can't parse smarthost Greg Wooledge <greg@wooledge.org> - 2024-05-23 14:40 +0200
Re: OpenSMTPD can't parse smarthost Paul M Foster <paulf@quillandmouse.com> - 2024-05-23 14:00 +0200
Re: OpenSMTPD can't parse smarthost Jeffrey Walton <noloader@gmail.com> - 2024-05-23 20:00 +0200
Re: OpenSMTPD can't parse smarthost Paul M Foster <paulf@quillandmouse.com> - 2024-05-23 20:10 +0200
Re: OpenSMTPD can't parse smarthost <tomas@tuxteam.de> - 2024-05-23 21:00 +0200
Re: OpenSMTPD can't parse smarthost Jeffrey Walton <noloader@gmail.com> - 2024-05-23 21:20 +0200
Re: OpenSMTPD can't parse smarthost tomas@tuxteam.de - 2024-05-23 21:30 +0200
Re: OpenSMTPD can't parse smarthost gene heskett <gheskett@shentel.net> - 2024-05-27 09:00 +0200
Re: OpenSMTPD can't parse smarthost Jeffrey Walton <noloader@gmail.com> - 2024-05-23 07:00 +0200
Re: OpenSMTPD can't parse smarthost <tomas@tuxteam.de> - 2024-05-23 06:40 +0200
csiph-web