DNS Error accessing webserver
Hi guys, I only found out about and installed EHCP today and it looks like a brilliant app! I've almost got it working, but people outside my home network can't connect. Here's my configuration:
Wireless home network (cable modem -> D-Link wireless router, port forwarded)
Laptop (Ubuntu, Jaunty, running LAMP and EHCP)
Desktop PC (for non-hosting use, testing)
Ownership of domain piemaster.net (and drumtaboo.info) with GoDaddy.com
I followed that tutorial to set it up (went well), and I'm now running EHCP on my laptop with the domains set up. The thing is I can go to http://piemaster.net/ or http://drumtaboo.info/ in my browser and the sites work perfectly. However when people outside my home network try it, it fails to connect. EDIT: In the time I've been writing this, it no longer even works for me. See below :(.
Here's the two things I'm worried about (due to inexperience):
1. The name server setup with GoDaddy - I've read a lot of EHCP posts about this, and think I've got it right. I've registered my IP address (114.77.x.x, forwarded from my router's Virtual Server to my laptop's internal IP [192.168.0.193]) as both ns1.piemaster.net and ns2.piemaster.net, and set those name servers as the name servers for the domain. That was a couple hours ago, so it might just have not propagated yet, I'm not sure.
2. The network interface setup - the setup walkthrough said:
# The primary network interface
iface eth0 inet static
However I don't think I can just copy this format for a few reasons.
a) eth0 is my ethernet cable device afaik, and I'm using my wireless, so I put eth1 instead.
b) My network is 192.168.0.1, not .1.0 (D-Link vs Netgear I believe?), so I replaced all those 3rd-place 1's with 0's
c) Obviously the address is different, but should I leave the gateway as 192.168.0.1, or make it .1.1? Or should the network be .0.0?
3. Like I said, I've broken it for myself now too... the internal redirection USED to go from public port 8080 to local port 80, but I changed it to 80 -> 80. Then it worked for me but no one else, and I then realised I'd set up EHCP to think that the server was at 114.77.x.x:8080, so I changed it to the now correct address with no port. And now it doesn't work. The page fails to load, and Google Chrome tells me "DNS error - cannot find server".
Anyway there's no rush, but having read that can anyone suggest what course of action I can take with the best chance of success? Bear in mind it was working before I messed with the internal IP's, so the logic seems to be correct, just I've screwed up my networking somewhere.
Thank you in advance!