Timeline for Issues with web hosting at home
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 31, 2012 at 12:15 | history | undeleted | MemLeak | ||
| May 21, 2012 at 22:41 | history | deleted | MemLeak | ||
| May 21, 2012 at 22:13 | comment | added | MemLeak | Text is updated localhost only as example. But this works only inhouse. | |
| May 21, 2012 at 22:06 | comment | added | MemLeak | Maybe a dns resolving problem? Sry | |
| May 21, 2012 at 22:05 | comment | added | hari | Thanks for the help but I didn't get you. you mean, I should make it point in a way I could call it localhost? why so? | |
| May 21, 2012 at 22:04 | comment | added | MemLeak | Sry I didn't understand the question right. So a work around would be to add C:\Windows\System32\drivers\etc\hosts (on W7) 192.168.1.4 name your want, (localhost, foo.dyndns.org) | |
| May 21, 2012 at 22:00 | comment | added | hari | Can you please elaborate on "alias" part? | |
| May 21, 2012 at 21:58 | comment | added | hari | I am not quite getting what you mean here. I have portforwarding enabled/working. From outside, I can see my www.example.com thingi. Point is, I cannot check www.example.com from inside home network. I have to do 192.168.1.4. | |
| May 21, 2012 at 21:57 | history | answered | MemLeak | CC BY-SA 3.0 |