-
192.168.1.10.local-ip.sh resolves to 192.168.1.10 - dots.192.168.1.10.local-ip.sh resolves to 192.168.1.10 - dashes.192-168-1-10.local-ip.sh resolves to 192.168.1.10-
*.local-ip.sh
:-
-
- server.pem -
- server.key -
In our case, this certificate will only match subdomains of + +
local-ip.sh
++ _ _ _ _ + | | | | (_) | | + | | ___ ___ __ _| | _ _ __ ___| |__ + | |/ _ \ / __/ _` | |_____| | '_ \ / __| '_ \ + | | (_) | (_| (_| | |_____| | |_) |\__ \ | | | + |_|\___/ \___\__,_|_| |_| .__(_)___/_| |_| + | | + |_| ++
What is local-ip.sh?
++ local-ip.sh is a magic domain name that provides wildcard DNS for any IP address. It is heavily inspired by + local-ip.co, sslip.io, and xip.io. +
+Quick example, say your LAN IP address is 192.168.1.10. Using local-ip.sh,
+ ++ ...and so on. You can use these domains to access virtual hosts on your development web server + from devices on your local network. No configuration required! +
+The best part is, you can serve your content over HTTPS with our TLS certificate for *.local-ip.sh
:
-
+
- server.pem +
- server.key +
+ Be aware that wildcard certificates are not recursive, meaning they don't match
+ "sub-subdomains".
In our case, this certificate will only match subdomains of
local-ip.sh
such as 192-168-1-10.local-ip.sh
where dashes separate
- the numbers that make up the IP address.
How does it work?
++ local-ip.sh runs publicly a custom DNS server. When your computer looks up a local-ip.sh domain, the local-ip.sh DNS server resolves to the IP address it extracts from the domain. -