Chromium and Mozilla to enforce 1 year validity for TLS certificates

Re:Chromium and Mozilla to enforce 1 year validity for TLS c... by jt2190 on Monday June 29, 2020 @08:54AM (#23677119)

I think you’re talking about running DNS locally (not sure) and resolving .local addresses by DNS. In that case, yes, the devices that do lookups by mDNS will experience a delay caused by first querying mDNS before falling back onto DNS. The solution is to set up mDNS for the internal resources.

Using an unregistered domain like .lan has serious security implications. See here: https://serverfault.com/a/17566

[ Parent | on HN ]

Re:Chromium and Mozilla to enforce 1 year validity for TLS c... by Karunamon on Monday June 29, 2020 @12:05PM (#23678845)

.lan is called out in appendix G of the MDNS RFC as "not recommended, but many people do this".

Personally speaking, I'm not too worried about .lan getting registered as a gTLD anytime soon. I'm a lot more worried about forgetting to renew my domain and having things horrifically break if/when that domain gets picked up by someone else. This is a lot more likely...

[ Parent | on HN ]

Re:Chromium and Mozilla to enforce 1 year validity for TLS c... by jt2190 on Monday June 29, 2020 @05:56PM (#23683689)

I’m not sure I understand... What would break on your local network if a public domain you own and use only for internal resources is registered by someone else? How is this different from making up a domain name? In both cases you have to set up something to resolve the names to IP addresses on your local network, be it a hosts file or DNS. I would expect that to keep working regardless of the ownership of the domain name.

[ Parent | on HN ]

Re:Chromium and Mozilla to enforce 1 year validity for TLS c... by paledot on Tuesday June 30, 2020 @08:21PM (#23696378)

I would have said the same about .dev, and did, until Google came along and registered it.

[ Parent | on HN ]