jonpugh

4 ms·

1. 1.▲
   by jonpugh 10y ago

   I build systems (devshop/aegir) that create and destroy websites on the fly. If I'm working on a feature related to that process I could create and delete a dozen or more arbitrary domains in a day. I also know plenty of web devel
2. 2.▲
   by jonpugh 10y ago

   I never suggested using the domain for anything but web browser requests, not sure why anyone would need to use it to connect in any other way. So as long as users don't use it for connecting to their local server are they safe? Don&#x
3. 3.▲
   by jonpugh 10y ago

   The benefit is not zero, it is having unlimited domains pointed to local without having to ever mess with DNS or /etc/hosts.
4. 4.▲
   by jonpugh 10y ago

   Sure, but this record goes to 127.0.0.1. How would I get the IP of your development server other than 127.0.0.1? When you request local.computer, it's not sending me your IP, it's requesting one. Right? Public DNS for a private
5. 5.▲
   by jonpugh 10y ago

   I still can't quite put my finger on the security risk for others, can you help explain what makes it one? Here's the only scenario I can think of: Say you are a web developer and you use mybusiness.local.computer for developing y
6. 6.▲
   by jonpugh 10y ago

   It's really just for convenience. I build a lot of drupal sites and often need to run a lot of them at once locally. Instead of putting each one on it's own port (hard to remember) or starting and stopping VMs or containers (tedio