<story><title>Xip.io: Wildcard DNS for everyone</title><url>http://xip.io</url></story><parent_chain><item><author>Antwan</author><text>Why not just customizing &amp;#x2F;etc&amp;#x2F;hosts then... You guys are relying too much on 3rd party tools without knowing what they do with your data and what they&amp;#x27;re becoming in the future.</text></item><item><author>bluefinity</author><text>You can set up your web server to serve different applications on different domains if you&amp;#x27;re working on multiple projects at the same time and don&amp;#x27;t want to put them on different ports or use subdirectories.&lt;p&gt;Another use case I can see is for testing subdomain-based web apps where you give each customer a subdomain (really just a wildcard dns record), e.g. acme.myapp.com</text></item><item><author>Piskvorrr</author><text>Perhaps I am missing something - what problem does this solve? Instead of an IPv4 address, you are now entering (optional) prefix, the IPv4 address, and a postfix &amp;quot;.xip.io&amp;quot; Where is the added value over entering the IP address directly?</text></item></parent_chain><comment><author>matthewmacleod</author><text>It&amp;#x27;s a DNS server. The only data they can get from you is what you&amp;#x27;re calling the subdomains on your apps.&lt;p&gt;Yes, you could achieve the same functionality by editing &amp;#x2F;etc&amp;#x2F;hosts, but that&amp;#x27;s a pain in the arse if you&amp;#x27;re rapidly switching between a set of different sites, or if you want to access a coworker&amp;#x27;s machine in the same way.&lt;p&gt;You guys are complaining too much about useful hacker-friendly tools from well-known companies.</text></comment>
<story><title>Xip.io: Wildcard DNS for everyone</title><url>http://xip.io</url></story><parent_chain><item><author>Antwan</author><text>Why not just customizing &amp;#x2F;etc&amp;#x2F;hosts then... You guys are relying too much on 3rd party tools without knowing what they do with your data and what they&amp;#x27;re becoming in the future.</text></item><item><author>bluefinity</author><text>You can set up your web server to serve different applications on different domains if you&amp;#x27;re working on multiple projects at the same time and don&amp;#x27;t want to put them on different ports or use subdirectories.&lt;p&gt;Another use case I can see is for testing subdomain-based web apps where you give each customer a subdomain (really just a wildcard dns record), e.g. acme.myapp.com</text></item><item><author>Piskvorrr</author><text>Perhaps I am missing something - what problem does this solve? Instead of an IPv4 address, you are now entering (optional) prefix, the IPv4 address, and a postfix &amp;quot;.xip.io&amp;quot; Where is the added value over entering the IP address directly?</text></item></parent_chain><comment><author>dan_manges</author><text>In most cases, customizing &amp;#x2F;etc&amp;#x2F;hosts would require every person working on a project to customize their &amp;#x2F;etc&amp;#x2F;hosts the same way. It becomes a burden when somebody wants to add or change an entry. They would need to email everybody who works on the project to tell them all to make the same change.</text></comment>