Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>When you connected to the server that serves StackOverflow, did you type in the IP address? It's 64.34.119.12, if that jogs your memory.</p> <p>You probably didn't. You probably typed "stackoverflow.com". There's a huge, complex, clever, and <a href="http://www.h-online.com/security/news/item/Massive-DNS-security-problem-endangers-the-internet-736419.html" rel="noreferrer">in some ways</a>, poorly implemented system called <a href="http://en.wikipedia.org/wiki/Domain_Name_System" rel="noreferrer">DNS</a> that translates sensible and human-readable names into IP addresses.</p> <p>One problem with DNS, though, is you need a "static IP", which is exactly what it sounds like: an IP address that doesn't change, which is exactly what you don't have.</p> <p>So, what can you do?</p> <ol> <li>You can buy a static IP account from your ISP (pretty expensive)</li> <li>You can use some proxy out in the Internet (a machine that <em>does</em> have a static IP and is willing to bounce your packets back and forth -- I'm not aware of any service that does this for you; you could write one and put it up on Amazon Web Services or Google App Engine, both of which would be free at your level of usage, but they'd be slow, since every packet trying to cross your living room would have have to go via some data-center in Virginia).</li> <li>You can keep doing what you're doing, looking in the net-configuration of your machine.</li> <li>You could speed (3) up a little by having your server program look up its own IP address and print it out where you could see it and type it into the server by hand.</li> <li>You can use DynDNS, as Sergey mentioned (this is the "right" solution, in that it's very general, it just might be a little complicated to set up)</li> <li>You can use <a href="http://en.wikipedia.org/wiki/IP_multicast" rel="noreferrer">multi-casting</a>.</li> </ol> <p>Multi-casting is an interesting solution, and it may work for you. The idea is, when your server starts up, it announces to the net, "Here I am, I'm providing X server, here's my IP address, talk to me." The problem is, a multi-cast won't leave your living room. Obviously, if every multi-cast were spread to every computer on the Internet, the whole thing would collapse, so your router will ignore, and not route, multi-cast packets. That may or may not be a deal-breaker for you. <strong>EDIT</strong> Re-reading your question, I see it <em>is</em> a deal-breaker for you. I'd go with #5, but be aware there may be routing issues (address translations that prevent a server from knowing the address that other computers can find it at) or fire-wall issues (that is, your ISP may prevent your server from receiving incoming packets even if the address is correct).</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    3. VO
      singulars
      1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload