howtogeek at July 10th, 2013 12:36 — #1
Originally published at: http://www.howtogeek.com/167190/how-and-why-to-assign-the-.local-domain-to-your-raspberry-pi/
If you’re tired of looking up the IP addresses of devices you frequently access via remote login, SSH, and other means on your home network, you can save yourself a lot of time by assigning an easy to remember .local address to the device. Read on as we demonstrate by assigning an easy to remember name to our Raspberry Pi.
jacobm001 at July 10th, 2013 13:47 — #2
I don't really understand what this would be used for. Why can't you just look up the device by it's hostname? Anything on my home server is accessed by 'chocolate/'. What would using chocolate.local do?
kid1000002000 at July 11th, 2013 03:27 — #3
It depends on the protocol you're using to access 'chocolate/'. mDNS makes it easy to not have to run DNSMasq at the router.
aviad_raviv1 at July 11th, 2013 12:11 — #4
I have actually worked in 2 places that had .local as thier internal domain name...
sparked the creation of
kjs356 at July 20th, 2013 20:03 — #5
I tried this, but now i can even ssh onto my rpi at all... using raspberrypi.local or the static ip it had.
ajabberwok at September 21st, 2013 07:08 — #6
After following these instructions, it doesn't work for windows for some reason.
When I open a web browser and type in "dana.local" or "http://dana.local" it doesn't bring me to my PI's webserver. However it works fine from my Linux and OS X machines, but not my Windows 7 machines.
I will say that ping seems to work:
Pinging dana.local [af80::250:b6bb:fe5b:be80%13] with 32 bytes of data:
Reply from af80::250:b6bb:fe5b:be80%13: time=2ms