Replaces .lan local domain with .thisnode.info fixes #540

[ilario]

See #540

[nicopace]

Why replacing it?
would suggest to add instead of replace, both can be at the same time, .lan is short (but requires to write the whole http://site.lan/ url), and the other one is longer but proper without the http:// part, so we should leave both.

[ilario]

would suggest to add instead of replace, both can be at the same time

I didn't know it was possible. @nicopace how do you set it up in OpenWrt?

[nicopace]

Don't know how...

This is another approach: https://web.archive.org/web/20180722223228/https://iyware.com/dont-use-dev-for-development/
like the .localhost subdomain as it is saying is a local host (local for the network) , and is a valid domain!

[ilario]

.lan is short

Consider that even if we replace .lan with .thisnode.info, the nodes will be accessible BOTH with http://lime-ddeeff.thisnode.info and with http://lime-ddeeff
so, if someone prefers to write less, it can already avoid writing the domain name.

[nicopace]

Well.. it looks it is not possible to define two domains (at least not in a fast search, because that "domain" key is also used to tell DHCP clients in which domain they are at.

This is another approach: https://web.archive.org/web/20180722223228/https://iyware.com/dont-use-dev-for-development/

Based on that document that I shared earlier, to be standards compliant we can use the *.thisnode.info, or the *.localhost domains.

On the other hand, using *.thisnode.info allows us to capture when the users are using the domain outside their network (like through their mobile network when it exists), and help them through it...