Re: IP address or DNS name (bug or feature)

On 12.06.2017 16:35, Tim wrote: Allegedly, on or about 12 June 2017, Walter H. sent: which Domain do you use for local? Back to the general question... I'd certainly like to see .lan reserved as for use with private LANs, just for this, there exists an I-D, which will become an RFC, and there

Re: IP address or DNS name (bug or feature)

Allegedly, on or about 12 June 2017, Walter H. sent: > which Domain do you use for local? Back to the general question... I'd certainly like to see .lan reserved as for use with private LANs, on normal DNS/DHCP that the user can control, as opposed to things like .local being under automatic

Re: IP address or DNS name (bug or feature)

Tim: >> I run a local DNS server, that's integrated with my DHCP server (in that >> new hosts assigned an IP by the DHCP server get their data incorporated >> into the DNS server, so all clients on my LAN use my DNS server for >> *all* name resolution, local and WWW). I don't make use of the

Re: IP address or DNS name (bug or feature)

On Fri, June 9, 2017 22:33, Tim wrote: > I run a local DNS server, that's integrated with my DHCP server (in that > new hosts assigned an IP by the DHCP server get their data incorporated > into the DNS server, so all clients on my LAN use my DNS server for > *all* name resolution, local and

Re: IP address or DNS name (bug or feature)

Gordon Messmer wrote: >> In any case, if that solution isn't workable for you, you can remove >> "mdns4_minimal [NOTFOUND=return]" from /etc/nsswitch.conf, and you >> should be able to look up .local hosts using DNS. Tom Horsley: > On every system I've ever tried *all* dns lookups always > fail

Re: IP address or DNS name (bug or feature)

On Thu, 8 Jun 2017 10:08:54 -0700 Gordon Messmer wrote: > In any case, if that solution isn't workable for you, you can remove > "mdns4_minimal [NOTFOUND=return]" from /etc/nsswitch.conf, and you > should be able to look up .local hosts using DNS. On every system I've ever tried *all* dns

Re: IP address or DNS name (bug or feature)

On 06/07/2017 10:53 PM, Walter H. wrote: when you do yum remove nss-mdns and say yes, you will remove more than 150 MBytes including many packets which refernce to nss-mdns ... including X11 Not on my system. The only thing that appears to depend on nss-mdns is wine, here. In any case, if

Mailman is broken (was: IP address or DNS name (bug or feature))

On Wed, June 7, 2017 23:27, Ed Greshko wrote: > On 06/08/17 00:25, Walter H. wrote: >> On 07.06.2017 17:40, stan wrote: >>> >>> But the message that shows up as the empty dots in Samuel's message is >>> from Walter and has the following encoding. >>> Content-Type: multipart/mixed; >>>

Re: IP address or DNS name (bug or feature)

On Wed, June 7, 2017 22:08, Gordon Messmer wrote: > On 06/07/2017 12:05 PM, Walter H. wrote: >> On 05.06.2017 22:44, Gordon Messmer wrote: >>> Sounds likely. In this case, you probably want to *remove* nss-mdns, >> remove the whole X? :D >> > > I don't really know what that means. when you do

Re: IP address or DNS name (bug or feature)

On 06/08/17 00:25, Walter H. wrote: > On 07.06.2017 17:40, stan wrote: >> >> But the message that shows up as the empty dots in Samuel's message is >> from Walter and has the following encoding. >> Content-Type: multipart/mixed; >> boundary="===7498209977189103805==" > this is because,

Re: IP address or DNS name (bug or feature)

On 06/07/2017 12:05 PM, Walter H. wrote: On 05.06.2017 22:44, Gordon Messmer wrote: Sounds likely. In this case, you probably want to *remove* nss-mdns, remove the whole X? :D I don't really know what that means. ___ users mailing list --

Re: IP address or DNS name (bug or feature)

On 05.06.2017 22:44, Gordon Messmer wrote: Sounds likely. In this case, you probably want to *remove* nss-mdns, remove the whole X? :D smime.p7s Description: S/MIME Cryptographic Signature ___ users mailing list -- users@lists.fedoraproject.org To

Re: IP address or DNS name (bug or feature)

Allegedly, on or about 07 June 2017, Samuel Sieb sent: > I've always done that and almost did that again right here. :-) It's > easier to just put a newline in instead of also deleting the extra ">" > from the previous line. > Just hitting enter twice would quickly break the quoting apart. If

Re: IP address or DNS name (bug or feature)

On 06/07/2017 09:25 AM, Walter H. wrote: On 07.06.2017 17:40, stan wrote: But the message that shows up as the empty dots in Samuel's message is from Walter and has the following encoding. Content-Type: multipart/mixed; boundary="===7498209977189103805==" this is because, my

Re: IP address or DNS name (bug or feature)

On 07.06.2017 17:40, stan wrote: But the message that shows up as the empty dots in Samuel's message is from Walter and has the following encoding. Content-Type: multipart/mixed; boundary="===7498209977189103805==" this is because, my Thunderbird generates both variants, the

Re: IP address or DNS name (bug or feature)

On 06/07/2017 01:05 AM, Tim wrote: I suspect you've got an option set to mask/hide/mute/silence quotes in replies. Some mailers offer that as option to make it easier to see new content in messages that are bloated with unedited quotes of prior messages. But they can get confused when

Re: IP address or DNS name (bug or feature)

On Wed, 7 Jun 2017 22:33:33 +0800 Ed Greshko wrote: > On 06/07/17 22:07, stan wrote: > > I use claws mail and had no problem seeing this message. I think > > Bob didn't see it because claws doesn't allow html messages unless > > asked to. There is an option to render

Re: IP address or DNS name (bug or feature)

On 06/07/17 22:07, stan wrote: > On Wed, 7 Jun 2017 17:39:20 +0800 > Ed Greshko wrote: > >> On 06/07/17 04:49, Bob Marcan wrote: > >>> Empty mail again. What is going on? >> >> Well, it seems you are using Claws Mail 3.14.1 to access your mail. >> >> Maybe you should

Re: IP address or DNS name (bug or feature)

On Wed, 7 Jun 2017 17:39:20 +0800 Ed Greshko wrote: > On 06/07/17 04:49, Bob Marcan wrote: >> Empty mail again. What is going on? > > > Well, it seems you are using Claws Mail 3.14.1 to access your mail. > > Maybe you should use the Web interface of gmail to see

Re: IP address or DNS name (bug or feature)

On 06/07/17 04:49, Bob Marcan wrote: > On Tue, 6 Jun 2017 12:59:07 -0700 > Samuel Sieb wrote: > >> On 06/06/2017 12:49 PM, Walter H. wrote: >> [...] >> [...] >> [...] >> >> [...] >> >> [...] >> ___ >> users mailing list

Re: IP address or DNS name (bug or feature)

Allegedly, on or about 06 June 2017, Bob Marcan sent: > > [...] > > [...] > > [...] > > > > [...] > > > > [...] > Empty mail again. What is going on? I suspect you've got an option set to mask/hide/mute/silence quotes in replies. Some mailers offer that as option to make it

Re: IP address or DNS name (bug or feature)

On Tue, June 6, 2017 06:31, Gordon Messmer wrote: > OP is using that domain in standard DNS, in violation of relevant > standards. can someone bring this to a standard https://www.ietf.org/staging/draft-hoehlhubmer-private-tlds-00.txt ___ users

Re: IP address or DNS name (bug or feature)

On Tue, 6 Jun 2017 12:59:07 -0700 Samuel Sieb wrote: > On 06/06/2017 12:49 PM, Walter H. wrote: > [...] > [...] > [...] > > [...] > > [...] > ___ > users mailing list -- users@lists.fedoraproject.org > To unsubscribe

Re: IP address or DNS name (bug or feature)

On 06.06.2017 21:59, Samuel Sieb wrote: On 06/06/2017 12:49 PM, Walter H. wrote: so when renaming my local domain to something different, this must be sure, that not any other future bug makes me renaming it again ... There are no guarantees, but at this point .lan is not likely to have any

Re: IP address or DNS name (bug or feature)

On 06/06/2017 12:49 PM, Walter H. wrote: On 06.06.2017 20:27, Samuel Sieb wrote: Either you've been lucky or those other systems don't support MDNS yet. given the possibility that the strange phenomens mentioned in the OP are really caused by using .local as my intranet-TLD, then why doesn't

Re: IP address or DNS name (bug or feature)

On 06.06.2017 20:27, Samuel Sieb wrote: On 06/06/2017 11:22 AM, Walter H. wrote: On 06.06.2017 20:13, Samuel Sieb wrote: On 06/05/2017 11:27 PM, Walter H. wrote: On Tue, June 6, 2017 07:40, Samuel Sieb wrote: On 06/05/2017 10:19 PM, Walter H. wrote: p.s. in case the phenomenas of the OP

Re: IP address or DNS name (bug or feature)

On 06/06/2017 11:22 AM, Walter H. wrote: On 06.06.2017 20:13, Samuel Sieb wrote: On 06/05/2017 11:27 PM, Walter H. wrote: On Tue, June 6, 2017 07:40, Samuel Sieb wrote: On 06/05/2017 10:19 PM, Walter H. wrote: p.s. in case the phenomenas of the OP won't change these are true bugs. I don't

Re: IP address or DNS name (bug or feature)

On 06.06.2017 20:15, Samuel Sieb wrote: On 06/05/2017 11:27 PM, Walter H. wrote: I had .home., but when I noticed that the pre-registration of .home. has started, I changed this to .local.; And that's when your problems started. no. it startet with this Fedora box, or to say it differently

Re: IP address or DNS name (bug or feature)

On 06.06.2017 20:13, Samuel Sieb wrote: On 06/05/2017 11:27 PM, Walter H. wrote: On Tue, June 6, 2017 07:40, Samuel Sieb wrote: On 06/05/2017 10:19 PM, Walter H. wrote: p.s. in case the phenomenas of the OP won't change these are true bugs. I don't understand what you're saying here. the

Re: IP address or DNS name (bug or feature)

On 06/05/2017 11:27 PM, Walter H. wrote: I had .home., but when I noticed that the pre-registration of .home. has started, I changed this to .local.; And that's when your problems started. at work we have company.local. You should warn them that they are going to run into the same problem

Re: IP address or DNS name (bug or feature)

On 06/05/2017 11:27 PM, Walter H. wrote: On Tue, June 6, 2017 07:40, Samuel Sieb wrote: On 06/05/2017 10:19 PM, Walter H. wrote: p.s. in case the phenomenas of the OP won't change these are true bugs. I don't understand what you're saying here. the system/Firefox has to take e.g.

Re: IP address or DNS name (bug or feature)

On 06/06/2017 10:28 AM, Doug wrote: was made by Murata. Now the problem: yesterday and today it is inaccessible by any means--ping by ip or name, or by nmap. I have tried connecting and disconnecting the lan cable, the power cable, and rebooted the router, but nothing works. And since I can't

Re: IP address or DNS name (bug or feature)

On Tue, 2017-06-06 at 10:32 -0700, stan wrote: > On Tue, 6 Jun 2017 09:38:39 -0500 > Robert Nichols wrote: > > > On 06/05/2017 11:31 PM, Gordon Messmer wrote: > > > As far as I know, there are no TLDs reserved for private > > > networks. All users should use

Re: IP address or DNS name (bug or feature)

On Tue, Jun 6, 2017 at 1:32 PM, stan wrote: > On Tue, 6 Jun 2017 09:38:39 -0500 > Robert Nichols wrote: > > > On 06/05/2017 11:31 PM, Gordon Messmer wrote: > > > As far as I know, there are no TLDs reserved for private > > > networks.

Re: IP address or DNS name (bug or feature)

On Tue, 6 Jun 2017 09:38:39 -0500 Robert Nichols wrote: > On 06/05/2017 11:31 PM, Gordon Messmer wrote: > > As far as I know, there are no TLDs reserved for private > > networks. All users should use properly registered domains for all > > DNS zones, private and

Re: IP address or DNS name (bug or feature)

On 06/05/2017 11:13 PM, Walter H. wrote: On Mon, June 5, 2017 22:25, Samuel Sieb wrote: On 06/05/2017 11:44 AM, Walter H. wrote: On 05.06.2017 20:38, Samuel Sieb wrote: nslookup resolved the .local addresses? That's surprising and might be a problem. I'm using inside my network a .local

Re: IP address or DNS name (bug or feature)

On 06.06.2017 16:43, Matthew Miller wrote: On Tue, Jun 06, 2017 at 09:38:39AM -0500, Robert Nichols wrote: Swell. Happen to know of a registrar that will let me register a domain that has no public facing DNS server? (At pretty much zero cost, of course) Almost any registrar should let you do

Re: IP address or DNS name (bug or feature)

On Tue, Jun 06, 2017 at 09:38:39AM -0500, Robert Nichols wrote: > Swell. Happen to know of a registrar that will let me register a > domain that has no public facing DNS server? (At pretty much zero > cost, of course) Almost any registrar should let you do this. -- Matthew Miller

Re: IP address or DNS name (bug or feature)

On 06/05/2017 11:31 PM, Gordon Messmer wrote: As far as I know, there are no TLDs reserved for private networks. All users should use properly registered domains for all DNS zones, private and public. Swell. Happen to know of a registrar that will let me register a domain that has no

Private DNS (was: IP address or DNS name (bug or feature))

On Tue, June 6, 2017 07:40, Samuel Sieb wrote: > .lan meets your requirements and I have seen that used. Or you could > make up something random. Since it's just your private network, if the > one you choose gets used later, you will have to change it again, but > you'll have lots of warning.

Re: IP address or DNS name (bug or feature)

Allegedly, on or about 05 June 2017, Walter H. sent: > I'm using inside my network a .local domain which is defined in a ZONE > on my DNS - so no problem ... If somewhere on your LAN are things using ZeroConf, Bonjour, or other similar autonomous psuedo-DNS software (client or server), then

Re: IP address or DNS name (bug or feature)

On Tue, June 6, 2017 07:40, Samuel Sieb wrote: > On 06/05/2017 10:19 PM, Walter H. wrote: >> .intranet. >> .internal. >> .private. >> .corp. >> .home. >> .lan." >> >> and the TLD .home. is just in a pre-registration phase ... >> >> tell me a TLD I can use instead, and which meets the following 3

Re: IP address or DNS name (bug or feature)

On 06/05/2017 10:19 PM, Walter H. wrote: .intranet. .internal. .private. .corp. .home. .lan." and the TLD .home. is just in a pre-registration phase ... tell me a TLD I can use instead, and which meets the following 3 criterias: (1) it will never been used officially (2) it is not .test.,

Re: IP address or DNS name (bug or feature)

On Tue, June 6, 2017 06:29, Samuel Sieb wrote: > According to https://tools.ietf.org/html/rfc6762 .local is reserved for > MDNS use and is not supposed to be DNS resolvable. exact this RFC says in "Appendix G. Private DNS Namespaces" "We do not recommend use of unregistered top-level domains at

Re: IP address or DNS name (bug or feature)

On 06/05/2017 09:13 PM, Walter H. wrote: On Mon, June 5, 2017 22:25, Samuel Sieb wrote: On 06/05/2017 11:44 AM, Walter H. wrote: On 05.06.2017 20:38, Samuel Sieb wrote: nslookup resolved the .local addresses? That's surprising and might be a problem. I'm using inside my network a .local

Re: IP address or DNS name (bug or feature)

On 06/05/2017 09:13 PM, Walter H. wrote: Actually, that*IS* a problem. You should not be doing that. That is quite likely the source of all your problems. That domain name is reserved for a specific purpose and putting it in DNS will cause conflicts. Sorry, you're telling*BULLSHIT*; the TLD

Re: IP address or DNS name (bug or feature)

On 06/05/2017 09:13 PM, Walter H. wrote: On Mon, June 5, 2017 22:25, Samuel Sieb wrote: On 06/05/2017 11:44 AM, Walter H. wrote: On 05.06.2017 20:38, Samuel Sieb wrote: nslookup resolved the .local addresses? That's surprising and might be a problem. I'm using inside my network a .local

Re: IP address or DNS name (bug or feature)

On Mon, June 5, 2017 22:25, Samuel Sieb wrote: > On 06/05/2017 11:44 AM, Walter H. wrote: >> On 05.06.2017 20:38, Samuel Sieb wrote: >>> nslookup resolved the .local addresses? That's surprising and might >>> be a problem. >> I'm using inside my network a .local domain which is defined in a ZONE

Re: IP address or DNS name (bug or feature)

On 06/05/2017 01:25 PM, Samuel Sieb wrote: On 06/05/2017 11:44 AM, Walter H. wrote: On 05.06.2017 20:38, Samuel Sieb wrote: nslookup resolved the .local addresses? That's surprising and might be a problem. I'm using inside my network a .local domain which is defined in a ZONE on my DNS - so

Re: IP address or DNS name (bug or feature)

On 06/05/2017 11:44 AM, Walter H. wrote: On 05.06.2017 20:38, Samuel Sieb wrote: nslookup resolved the .local addresses? That's surprising and might be a problem. I'm using inside my network a .local domain which is defined in a ZONE on my DNS - so no problem ... Actually, that *IS* a

Re: IP address or DNS name (bug or feature)

On 05.06.2017 20:38, Samuel Sieb wrote: nslookup resolved the .local addresses? That's surprising and might be a problem. I'm using inside my network a .local domain which is defined in a ZONE on my DNS - so no problem ... smime.p7s Description: S/MIME Cryptographic Signature

Re: IP address or DNS name (bug or feature)

On 06/05/2017 11:25 AM, Walter H. wrote: as this is the first time I'm using Fedora, I noticed the following ... (a) when open a SSH connection, it tells e.g. Last login: Mon Jun 5 20:14:37 2017 from 192.168.1.1 all other Linux VMs and/or the Router box show there Last login: Sat Jun 3

IP address or DNS name (bug or feature)

Hello, as this is the first time I'm using Fedora, I noticed the following ... (a) when open a SSH connection, it tells e.g. Last login: Mon Jun 5 20:14:37 2017 from 192.168.1.1 all other Linux VMs and/or the Router box show there Last login: Sat Jun 3 21:41:45 2017 from winpc.local (b) when