8 ms·

Give HN: *.til.io resolves to 127.0.0.1

46 points by jtolj 12y ago

jtolj 12y ago
I got tired of editing my host file for local development. Have been meaning to do this for a while, but I never had a domain name short enough so as not to be annoying to type.
- hydrogen18 12y ago
  This is brilliant. Just wait till lots of people are using this, load up a ton of patched software for every known protocol to record usernames and passwords on a machine. Then you can just intermittently have the domain resolve to that machine and collect the usernames and passwords. It'll be difficult to detect because it won't even be reproducible.
  - jtolj 12y ago
    Not following how this might present a security issue, but I'm curious for you to expand on this. Seems like even if the DNS record managed to change in the midst of a POST request, the post would pretty obviously fail to perform as expected. But yes, an obvious disclaimer of "don't trust me by POSTing your bank passwords to any of these subdomains" might be in order.
    - thedufer 12y ago
      You can trivially farm data that people are sending to their local apps by having DNS occasionally change to an IP you own (and then immediately back, to avoid detection). On that IP, you would have something that remembers the parts of the request that might be interesting (query parameters, body) and return a benign-looking error (just severing the connection without a response would probably do it). At the very least, you'd probably get some email/pass pairs that work on a few major sites.
    - extc 12y ago
      From your browser's perspective, the POST would fail, if it expected a certain response. That would happen after the site already recorded the contents of your POST.
_mikz 12y ago
like lvh.me. also check xip.io
slig 12y ago
See also: http://xip.io/ http://xip.io/ > xip.io is a magic domain name that provides wildcard DNS for any IP address So you can test stuff on your phone/tablet without messing with 'hosts' file, for instance: myapp.192.168.0.1.xip.io will resolve to 192.168.0.1.
- skrause 12y ago
  Also http://nip.io/ http://nip.io/
  - jtolj 12y ago
    Both of these are really useful, but a lot to type if you just need 127.0.0.1.
- astrodust 12y ago
  xip.io is great for testing on virtual machines so you can use the unusual private interface address of your host, or of the virtual machine itself.
- general_failure 12y ago
  How does this work? How do you make multilevel subdomain wildcards work? Maybe they run their own DNS server in which case this seems atleast doable. edit: It's smack on the front page of xip.io :) "xip.io runs a custom DNS server on the public Internet.".
- unfamiliar 12y ago
  That seems like more of a mess than just "messing with the hosts file." What happens when your ip changes and none of your links work correctly?
  - tomjakubowski 12y ago
    It is generally more difficult to edit a hosts file on a phone or tablet or on your non-technical coworker's computer. xip.io is useful for these situations. And if your IP address changes, surely it is more of a pain to edit the hosts file again on these several other phones/tablets/computers than to just send a new link.
swalsh 12y ago
This is pretty cool. Thanks, will be using.
Kiro 12y ago
Can someone explain what the puprose is?
- reustle 12y ago
  For example, I use dev.projectname.com for every project I work on locally. This way, the auto-filled usernames/passwords never get mixed up between projects, as they do when you do everything on 127.0.0.1:8000
- jtolj 12y ago
  If you develop multiple websites on your local machine, you distinguish them by using different domain names for each of them. You might have site1.dev and site2.dev. There are a variety of methods to handle this, but commonly you add a record to your system's host file to resolve these domain names to the ip address 127.0.0.1 (your local computer). Using site1.til.io and site2.til.io instead eliminates having to manage that host file (which is a minor and repetitive annoyance).
  - monk_e_boy 12y ago
    .dev? heathen! .local please :)
    - jtolj 12y ago
      I actually was using .local previously, but my co-workers all use .dev so I assumed that was more common ;p.
    - jatoben 12y ago
      Careful; if you or your coworkers use OS X, you may run into conflicts with Bonjour-registered hostnames.
    - astrodust 12y ago
      .local conflicts with Bonjour, so it's not as good.
    - jcampbell1 12y ago
jongalloway2 12y ago
http://readme.localtest.me/ http://readme.localtest.me/
seanp2k2 12y ago
OT, but someone should start the .JS TLD for the tons of useful javascript libs out there. How awesome would it be to just go to Angular.js or node.js and have that be their actual site?
- petercooper 12y ago
  I agree, but it would need someone to put up the $180,000 non refundable fee for it to be considered or whatever it is. Google could afford that, but then imagine the storm they'd get from the JS community..
  - TazeTSchnitzel 12y ago
    Worse than that: Someone would need to found a country called JavaScriptLand. 2-letter domains are reserved for ccTLDs.
    - petercooper 12y ago
      Good call! I could imagine a country being easier to form than getting the community to agree who would own a GTLD anyway.. ;-)
- ibrahima 12y ago
  The CDN URL can just be angular.js/angular.js
  - troels 12y ago
    Better yet, just: http://angular.js http://angular.js
- deleted 12y ago
  [deleted]
- maxwell 12y ago
  https://github.com/ozten/TLD.js/issues/8 https://github.com/ozten/TLD.js/issues/8
tootie 12y ago
How does this work? Isn't 127.0.0.1 a loopback? How does it get to the internet?
- sp332 12y ago
  Your browser asks the DNS server for the IP address corresponding to the domain name. If you ask for google.com it will reply e.g. 74.125.228.228 and then your browser will connect to 74.125.228.228 directly. When your browser asks that same DNS server for til.io's IP address, it gets 127.0.0.1, and then your browser connects to 127.0.0.1!
- astrodust 12y ago
  The point is it doesn't go to the internet, it just sets up an alias to your local machine. This is useful when you want to have several different virtual hosts on your machine, all of which would otherwise be called "localhost".
  - extc 12y ago
    It does go to the Internet, for the DNS query. This won't work offline.
sildur 12y ago
Also, http://whatever.new/ http://whatever.new/
sk5t 12y ago
Relying on a magical domain "just for development" is extremely careless behavior. Even assuming that these addresses always resolved to 127.0.0.1 with no interruption, slowdown, or redirection ever, do you really want to be leaking private hostnames etc. over the internet? Simply run a local DNS with forwarding, create a zone or two for your internal machines, all done. And you can even have other record types besides A and PTR...
- chc 12y ago
  This kind of reminds me of "A monad is just a monoid in the category of endofunctors, what's the problem?"
  - troels 12y ago
    Editing /etc/hosts isn't exactly rocket science. If you're a developer anyway.
    - chc 12y ago
      sk5t was talking about setting up a private DNS server, not editing /etc/hosts.
    - coolsunglasses 12y ago
      > isn't exactly rocket science. If you're a developer anyway. This applies to monads too.
  - sk5t 12y ago
    Do you mean that I am understating the difficulty of running DNS on a development workstation or home network? Running secure DNS at huge scale is challenging, but a puny server to mess around with is 1/10 the challenge of almost any development chore. (Apologies if I misunderstand the comparison to monad-speak.)
    - chc 12y ago
      I'm basically saying you're overestimating the average developer's understanding of the running of a private DNS server at all. Monoids and endofunctors aren't actually difficult either, but they're arcane knowledge that most people don't have, so any statement that relies on average developers having that knowledge is a bit unrealistic. Basically, I'm pretty sure I could apt-get install bind, but then I would have no clue what I was doing and I'm not entirely sure what setting up a zone entails. These problems are probably all quite solvable, but without the foundational knowledge, it's not 1/10.
Spone 12y ago
If you use Vagrant for development, there are some plugins that will modify your HOSTS file automatically when you start your Vagrant VM. See for instance https://github.com/cogitatio/vagrant-hostsupdater https://github.com/cogitatio/vagrant-hostsupdater
rdtsc 12y ago
So does localhost
rikkus 12y ago
Or, if you have your own domain, set up a wildcard in your DNS, which could be external (I use cloudflare - free and reliable). Example: I own rikk.us and want to be able to set up many websites on a few machines with my network, so: I point ✱.l.rikk.us to my laptop and now I can set up as many websites as I like on my laptop, so long as they have a binding matching ✱.l.rikk.us, and have them all work just as if they were on separate hosts. This allows me to make testsite1.l.rikk.us, testsite2.l.rikk.us, oh.bugger.i.broke.it.l.rikkus.us, etc. ✱ Sorry for the heavy asterisks but I don't know how to write a normal one without it triggering <em>
jhgg 12y ago
We have something very similar at our workplace. *.l.tsl.io resolves to localhost. We usually use it to test hostnames[1] on our django projects on the the local developeent server. Definitely beats having to add a lot of records to /etc/hosts. [1]: http://django-hosts.readthedocs.org/en/latest/ http://django-hosts.readthedocs.org/en/latest/
e0m 12y ago
This looks like another .lvh.me Although it's nice to have a backup. I've found this invaluable when testing subdomains. Each of our accounts gets their own subdomain and testing that is a huge pain with a hosts file (need to explicitly map each one). The wildcard nature of .til.io or .lvh.me is key. The only issue I've noticed with 192.168.1.101.xip.io is that if your server code splits domains on dots and expects things to be in the "nth" place then things can go wrong (cough cough Rails). The other thing this is super useful for is testing subdomains locally from a mobile device.
spacefight 12y ago
It resolves at least to that for now. Until someone forgets to pay the bill (for various reasons), runs out of money in their bank account to keep it up or whatever reason there might be. Then devs around the globe scramble to find out what data might have been leaked and to whom.
- jtolj 12y ago
  It's around $50 a year for the domain, which is a cost I'm happy to eat as I'm using it myself. But yes, if you're working on top secret projects or something that might leak sensitive data it's probably not a good idea to use this or any of these other services.
spacefight 12y ago
Well, www.til.io doesn't, for a start.
- jtolj 12y ago
  Touche. I freed that one up.
saidajigumi 12y ago
I'll recommend using dnsmasq plus some local resolver configuration to set up your own host-local magic domain, eliminating the need for reliance on a third-party magic domain. Pow[1] by the Basecamp folks provides a nicely packaged version of dnsmasq tooling for Rack & Rails apps. See also, the guard-pow and powder gems which make using Pow even nicer. For other cases (and the DIYers among us) Thomas Sutton wrote up instructions for setting up dnsmasq[2] on OS X for app development. IIRC, the dnsmasq setup should be identical on other *nix flavors. Your local resolver configuration may vary, but this guide will get you pointed the right direction. I highly recommend reading [2] even just as a guide to understand/demystify what Pow does under the hood. The dnsmasq setup can also be used for tools like Dokku[3], a Heroku-style service you can run in (e.g.) a local VM. [1] http://pow.cx/ http://pow.cx/ [2] http://passingcuriosity.com/2013/dnsmasq-dev-osx/ http://passingcuriosity.com/2013/dnsmasq-dev-osx/ [3] https://github.com/progrium/dokku https://github.com/progrium/dokku
- scott_karana 12y ago
  I love Pow, but I really, really wish they'd change their default tld from .dev to .local. The .dev TLD might end up existing soon[1], whereas .local is reserved and will never exist on root nameservers[2]. So eventually, developers using Pow might have conflicts between their local-only dev sites and real websites. Bad mojo. 1 http://icannwiki.com/.dev http://icannwiki.com/.dev 2 http://en.wikipedia.org/wiki/.local http://en.wikipedia.org/wiki/.local
  - saidajigumi 12y ago
    That won't work if you're using mDNS on the local network, as the dnsmasq resolution will hijack all queries to .local. Really, there just needs to be a small set of reserved TLDs. This includes one for which queries should never* be issued off a given host. .local (== 127.0.0.1) would have been ideal, but zeroconf slurped it up first. I'd put my vote in for .dev, but the Wikipedia link indicates that Google's looking to score it. :-P
    - scott_karana 12y ago
devoldmx 12y ago
I have used this for a while and it works fine. I understand that it is not for every project, but you can set up quickly an app. https://ngrok.com/ https://ngrok.com/
drivingmenuts 12y ago
I usually just use the real sitename with a .vm tld if I'm working in local dev space. If it turns out that someone starts up a .vm tld for real, well, no loss. I'll just switch to something else. There's no right and no wrong way to do this on your local machine as long as you don't break the internet for everyone else and as long as it's repeatable/undoable.
- kgc 12y ago
  How do you do that .vm thing?
  - drivingmenuts 12y ago
    In my hosts file, sites that are on my local vm are referred to as project1.vm, project2.vm and so on. Each virtual host is configured with the name project1.vm and so on and so forth. If I really felt like it, I could put a site on my called yahoo.com and change my hosts file to point that instead. I don't use yahoo for anything (nothing against them, I just don't) so it wouldn't hurt anything. Additionally, my vms all have two network addresses - one is dynamic from my router (for updates, etc.) and one is a host-only connector with a fixed IP. That's the address I use to connect to the sites. I don't bother with running a private DNS or anything - I'm more concerned with site development, not routing issues. The VM is an ends to a means and all that other stuff, while useful to know, takes up time I don't really feel like spending.
dingaling 12y ago
Ingenious idea, but no AAAA RR for ::1? In 2014?
- jtolj 12y ago
  Good call, added. Might take a few to propogate.
  - dingaling 12y ago
    Cheers!

46 points by jtolj 12y ago

jtolj 12y ago

I got tired of editing my host file for local development. Have been meaning to do this for a while, but I never had a domain name short enough so as not to be annoying to type.

hydrogen18 12y ago
This is brilliant. Just wait till lots of people are using this, load up a ton of patched software for every known protocol to record usernames and passwords on a machine. Then you can just intermittently have the domain resolve to that machine and collect the usernames and passwords. It'll be difficult to detect because it won't even be reproducible.
- jtolj 12y ago
  Not following how this might present a security issue, but I'm curious for you to expand on this. Seems like even if the DNS record managed to change in the midst of a POST request, the post would pretty obviously fail to perform as expected. But yes, an obvious disclaimer of "don't trust me by POSTing your bank passwords to any of these subdomains" might be in order.
  - thedufer 12y ago
    You can trivially farm data that people are sending to their local apps by having DNS occasionally change to an IP you own (and then immediately back, to avoid detection). On that IP, you would have something that remembers the parts of the request that might be interesting (query parameters, body) and return a benign-looking error (just severing the connection without a response would probably do it). At the very least, you'd probably get some email/pass pairs that work on a few major sites.
  - extc 12y ago
    From your browser's perspective, the POST would fail, if it expected a certain response. That would happen after the site already recorded the contents of your POST.

_mikz 12y ago

like lvh.me. also check xip.io

slig 12y ago

See also: http://xip.io/ http://xip.io/ > xip.io is a magic domain name that provides wildcard DNS for any IP address So you can test stuff on your phone/tablet without messing with 'hosts' file, for instance: myapp.192.168.0.1.xip.io will resolve to 192.168.0.1.

skrause 12y ago
Also http://nip.io/ http://nip.io/
- jtolj 12y ago
  Both of these are really useful, but a lot to type if you just need 127.0.0.1.
astrodust 12y ago
xip.io is great for testing on virtual machines so you can use the unusual private interface address of your host, or of the virtual machine itself.
general_failure 12y ago
How does this work? How do you make multilevel subdomain wildcards work? Maybe they run their own DNS server in which case this seems atleast doable. edit: It's smack on the front page of xip.io :) "xip.io runs a custom DNS server on the public Internet.".
unfamiliar 12y ago
That seems like more of a mess than just "messing with the hosts file." What happens when your ip changes and none of your links work correctly?
- tomjakubowski 12y ago
  It is generally more difficult to edit a hosts file on a phone or tablet or on your non-technical coworker's computer. xip.io is useful for these situations. And if your IP address changes, surely it is more of a pain to edit the hosts file again on these several other phones/tablets/computers than to just send a new link.

swalsh 12y ago

This is pretty cool. Thanks, will be using.

Kiro 12y ago

Can someone explain what the puprose is?

reustle 12y ago
For example, I use dev.projectname.com for every project I work on locally. This way, the auto-filled usernames/passwords never get mixed up between projects, as they do when you do everything on 127.0.0.1:8000
jtolj 12y ago
If you develop multiple websites on your local machine, you distinguish them by using different domain names for each of them. You might have site1.dev and site2.dev. There are a variety of methods to handle this, but commonly you add a record to your system's host file to resolve these domain names to the ip address 127.0.0.1 (your local computer). Using site1.til.io and site2.til.io instead eliminates having to manage that host file (which is a minor and repetitive annoyance).
- monk_e_boy 12y ago
  .dev? heathen! .local please :)
  - jtolj 12y ago
    I actually was using .local previously, but my co-workers all use .dev so I assumed that was more common ;p.
  - jatoben 12y ago
    Careful; if you or your coworkers use OS X, you may run into conflicts with Bonjour-registered hostnames.
  - astrodust 12y ago
    .local conflicts with Bonjour, so it's not as good.
  - jcampbell1 12y ago

jongalloway2 12y ago

http://readme.localtest.me/ http://readme.localtest.me/

seanp2k2 12y ago

OT, but someone should start the .JS TLD for the tons of useful javascript libs out there. How awesome would it be to just go to Angular.js or node.js and have that be their actual site?

petercooper 12y ago
I agree, but it would need someone to put up the $180,000 non refundable fee for it to be considered or whatever it is. Google could afford that, but then imagine the storm they'd get from the JS community..
- TazeTSchnitzel 12y ago
  Worse than that: Someone would need to found a country called JavaScriptLand. 2-letter domains are reserved for ccTLDs.
  - petercooper 12y ago
    Good call! I could imagine a country being easier to form than getting the community to agree who would own a GTLD anyway.. ;-)
ibrahima 12y ago
The CDN URL can just be angular.js/angular.js
- troels 12y ago
  Better yet, just: http://angular.js http://angular.js
deleted 12y ago
[deleted]
maxwell 12y ago
https://github.com/ozten/TLD.js/issues/8 https://github.com/ozten/TLD.js/issues/8

tootie 12y ago

How does this work? Isn't 127.0.0.1 a loopback? How does it get to the internet?

sp332 12y ago
Your browser asks the DNS server for the IP address corresponding to the domain name. If you ask for google.com it will reply e.g. 74.125.228.228 and then your browser will connect to 74.125.228.228 directly. When your browser asks that same DNS server for til.io's IP address, it gets 127.0.0.1, and then your browser connects to 127.0.0.1!
astrodust 12y ago
The point is it doesn't go to the internet, it just sets up an alias to your local machine. This is useful when you want to have several different virtual hosts on your machine, all of which would otherwise be called "localhost".
- extc 12y ago
  It does go to the Internet, for the DNS query. This won't work offline.

sildur 12y ago

Also, http://whatever.new/ http://whatever.new/

sk5t 12y ago

Relying on a magical domain "just for development" is extremely careless behavior. Even assuming that these addresses always resolved to 127.0.0.1 with no interruption, slowdown, or redirection ever, do you really want to be leaking private hostnames etc. over the internet? Simply run a local DNS with forwarding, create a zone or two for your internal machines, all done. And you can even have other record types besides A and PTR...

chc 12y ago
This kind of reminds me of "A monad is just a monoid in the category of endofunctors, what's the problem?"
- troels 12y ago
  Editing /etc/hosts isn't exactly rocket science. If you're a developer anyway.
  - chc 12y ago
    sk5t was talking about setting up a private DNS server, not editing /etc/hosts.
  - coolsunglasses 12y ago
    > isn't exactly rocket science. If you're a developer anyway. This applies to monads too.
- sk5t 12y ago
  Do you mean that I am understating the difficulty of running DNS on a development workstation or home network? Running secure DNS at huge scale is challenging, but a puny server to mess around with is 1/10 the challenge of almost any development chore. (Apologies if I misunderstand the comparison to monad-speak.)
  - chc 12y ago
    I'm basically saying you're overestimating the average developer's understanding of the running of a private DNS server at all. Monoids and endofunctors aren't actually difficult either, but they're arcane knowledge that most people don't have, so any statement that relies on average developers having that knowledge is a bit unrealistic. Basically, I'm pretty sure I could apt-get install bind, but then I would have no clue what I was doing and I'm not entirely sure what setting up a zone entails. These problems are probably all quite solvable, but without the foundational knowledge, it's not 1/10.

Spone 12y ago

If you use Vagrant for development, there are some plugins that will modify your HOSTS file automatically when you start your Vagrant VM. See for instance https://github.com/cogitatio/vagrant-hostsupdater https://github.com/cogitatio/vagrant-hostsupdater

rdtsc 12y ago

So does localhost

rikkus 12y ago

Or, if you have your own domain, set up a wildcard in your DNS, which could be external (I use cloudflare - free and reliable). Example: I own rikk.us and want to be able to set up many websites on a few machines with my network, so: I point ✱.l.rikk.us to my laptop and now I can set up as many websites as I like on my laptop, so long as they have a binding matching ✱.l.rikk.us, and have them all work just as if they were on separate hosts. This allows me to make testsite1.l.rikk.us, testsite2.l.rikk.us, oh.bugger.i.broke.it.l.rikkus.us, etc. ✱ Sorry for the heavy asterisks but I don't know how to write a normal one without it triggering <em>

jhgg 12y ago

We have something very similar at our workplace. *.l.tsl.io resolves to localhost. We usually use it to test hostnames[1] on our django projects on the the local developeent server. Definitely beats having to add a lot of records to /etc/hosts. [1]: http://django-hosts.readthedocs.org/en/latest/ http://django-hosts.readthedocs.org/en/latest/

e0m 12y ago

This looks like another .lvh.me Although it's nice to have a backup. I've found this invaluable when testing subdomains. Each of our accounts gets their own subdomain and testing that is a huge pain with a hosts file (need to explicitly map each one). The wildcard nature of .til.io or .lvh.me is key. The only issue I've noticed with 192.168.1.101.xip.io is that if your server code splits domains on dots and expects things to be in the "nth" place then things can go wrong (cough cough Rails). The other thing this is super useful for is testing subdomains locally from a mobile device.

spacefight 12y ago

It resolves at least to that for now. Until someone forgets to pay the bill (for various reasons), runs out of money in their bank account to keep it up or whatever reason there might be. Then devs around the globe scramble to find out what data might have been leaked and to whom.

jtolj 12y ago
It's around $50 a year for the domain, which is a cost I'm happy to eat as I'm using it myself. But yes, if you're working on top secret projects or something that might leak sensitive data it's probably not a good idea to use this or any of these other services.

spacefight 12y ago

Well, www.til.io doesn't, for a start.

jtolj 12y ago
Touche. I freed that one up.

saidajigumi 12y ago

I'll recommend using dnsmasq plus some local resolver configuration to set up your own host-local magic domain, eliminating the need for reliance on a third-party magic domain. Pow[1] by the Basecamp folks provides a nicely packaged version of dnsmasq tooling for Rack & Rails apps. See also, the guard-pow and powder gems which make using Pow even nicer. For other cases (and the DIYers among us) Thomas Sutton wrote up instructions for setting up dnsmasq[2] on OS X for app development. IIRC, the dnsmasq setup should be identical on other *nix flavors. Your local resolver configuration may vary, but this guide will get you pointed the right direction. I highly recommend reading [2] even just as a guide to understand/demystify what Pow does under the hood. The dnsmasq setup can also be used for tools like Dokku[3], a Heroku-style service you can run in (e.g.) a local VM. [1] http://pow.cx/ http://pow.cx/ [2] http://passingcuriosity.com/2013/dnsmasq-dev-osx/ http://passingcuriosity.com/2013/dnsmasq-dev-osx/ [3] https://github.com/progrium/dokku https://github.com/progrium/dokku

scott_karana 12y ago
I love Pow, but I really, really wish they'd change their default tld from .dev to .local. The .dev TLD might end up existing soon[1], whereas .local is reserved and will never exist on root nameservers[2]. So eventually, developers using Pow might have conflicts between their local-only dev sites and real websites. Bad mojo. 1 http://icannwiki.com/.dev http://icannwiki.com/.dev 2 http://en.wikipedia.org/wiki/.local http://en.wikipedia.org/wiki/.local
- saidajigumi 12y ago
  That won't work if you're using mDNS on the local network, as the dnsmasq resolution will hijack all queries to .local. Really, there just needs to be a small set of reserved TLDs. This includes one for which queries should never* be issued off a given host. .local (== 127.0.0.1) would have been ideal, but zeroconf slurped it up first. I'd put my vote in for .dev, but the Wikipedia link indicates that Google's looking to score it. :-P
  - scott_karana 12y ago

devoldmx 12y ago

I have used this for a while and it works fine. I understand that it is not for every project, but you can set up quickly an app. https://ngrok.com/ https://ngrok.com/

drivingmenuts 12y ago

I usually just use the real sitename with a .vm tld if I'm working in local dev space. If it turns out that someone starts up a .vm tld for real, well, no loss. I'll just switch to something else. There's no right and no wrong way to do this on your local machine as long as you don't break the internet for everyone else and as long as it's repeatable/undoable.

kgc 12y ago
How do you do that .vm thing?
- drivingmenuts 12y ago
  In my hosts file, sites that are on my local vm are referred to as project1.vm, project2.vm and so on. Each virtual host is configured with the name project1.vm and so on and so forth. If I really felt like it, I could put a site on my called yahoo.com and change my hosts file to point that instead. I don't use yahoo for anything (nothing against them, I just don't) so it wouldn't hurt anything. Additionally, my vms all have two network addresses - one is dynamic from my router (for updates, etc.) and one is a host-only connector with a fixed IP. That's the address I use to connect to the sites. I don't bother with running a private DNS or anything - I'm more concerned with site development, not routing issues. The VM is an ends to a means and all that other stuff, while useful to know, takes up time I don't really feel like spending.

dingaling 12y ago

Ingenious idea, but no AAAA RR for ::1? In 2014?

jtolj 12y ago
Good call, added. Might take a few to propogate.
- dingaling 12y ago
  Cheers!