local.gd

The easiest way to serve localhost. DNS that always resolves to 127.0.0.1.

Synopsis

Use mysite.local.gd when developing locally and it'll resolve to 127.0.0.1 just like magic! Any subdomain like *.local.gd will work.

It's like xip.io and nip.io but straight up easier since we always point to 127.0.0.1.

We use Netlify DNS so we're pretty sure you're always within 10ms of a DNS server, wherever you are. It's super quick!

Try it now!

Use any subdomain you like, and sub-sub-domains work too!

    $ dig startup.local.gd
    startup.local.gd.   	86400	IN	A	127.0.0.1

    $ dig www.startup.local.gd
    www.startup.local.gd.	86400	IN	A	127.0.0.1

    $ dig my.project.company.local.gd
    my.project.company.local.gd.	86400	IN	A	127.0.0.1

    $ dig alderaan.local.gd
    alderaan.local.gd.  	86400	IN	A	127.0.0.1
    

Apache

Just use ServerName and ServerAlias and you're good to go:

    ServerName froogle.local.gd
    ServerAlias www.froogle.local.gd
    

Nginx

Nginx is just as easy as Apache2 and you can add multiple hostnames to one line:

    server_name bloogle.local.gd www.bloogle.local.gd;
    

Why?

Built as a personal tool but may be useful for others. I may switch projects a few times on a regular development day, so these features provide the following advantages:

• use a different port for each project locally (and they don't all bash on port 3000, 5000 or 8080)
• use a different local hostname for each project, such as cssminifier.local.gd or img-resize.local.gd, and Apache or Nginx just forwards to the correct port
• use mkcert for https if I need to set up SSL for a development site

Who

• By Andrew Chilton (@andychilton).
• For Apps Attic Ltd (@AppsAttic).

(Ends)