DNS Error accessing webserver

[Pie21]

Okay, I installed it without a hitch, I added my domain (with Add, not Easy Add, but it seemed straightforward enough), and for piemaster.net I added my IP (114.77.86.29) as Host IP 1 twice as NS1 and NS2 (I only typed NS1 and NS2 in the field - it's got a ".PIEMASTER.NET" appended on the end of the field), and then put NS1.PIEMASTER.NET and NS2.PIEMASTER.NET in the Manage Name Servers window thing.

This was about a week ago, and nothing worked.

Then I had a crack with FreeDNS which all went smoothly, set my name servers to NS1-4.AFRAID.NET or ORG or whatever it was and although www.piemaster.net displays a placeholder page (since I haven't aliased it to my IP), piemaster.net (which has an A Record to my IP) fails to load. Same deal.

I've put it back to NS1 and 2.PIEMASTER.NET now, but I'm convinced the problem is on my laptop somewhere, most likely in either /etc/resolv.conf AND/OR /etc/network/interfaces. What should I have in these files?

Restored from old drupal forum, for user uid:2648 username:Mir
You may reset your password to access your new account here.

[Pie21]

Hi Bahattin,

Sorry, I <em>have</em> had my laptop turned off briefly a few times recently, which may have caused some confusion, but it's given me results like that even when I execute them on the laptop while it's running and should be working fine. I'll try and leave it on from now on.

I've DMZ'd my laptop so all those important ports are wide open. I can still access http://piemaster.net and http://drumtaboo.info AND http://114.77.86.29/ from inside my home network, but they don't connect from outside.

It's gotta be something wrong with my laptop, right? What should I have in /etc/resolv.conf and in /etc/network/interfaces?

Restored from old drupal forum, for user uid:2719 usernameie21
You may reset your password to access your new account here.

[Mir]

I followed the exact steps i posted, and no problems on my end.

I think i know the problem though, when i type in your ip address, your website does not show up, telling me that you have still not fixed things on your router. What router do you have? are you sure you have a static ip address?






Restored from old drupal forum, for user uid:2719 usernameie21
You may reset your password to access your new account here.

[Pie21]

Okay, I feel like the world's dumbest dude right now.

Turns out I had DHCP on all along - I was so sure I had static IP's that I just ignored it. I noticed when suddenly the IP to my laptop was 192.168.0.198, instead of .193. So I switched off the DHCP server and we're full static now, laptop is 192.168.0.198. Router is a D-Link DIR-635 FYI.

Of course my IP wasn't changing from .193 before, so it's still not working. Again, it works on networked computers, but not from outside. My DNS server in /etc/resolv.conf is set to 192.168.0.1 (my router's internal IP), and I think that's right.

nmap 115.77.86.29 works (everything's open), host localhost and host 192.168.0.198 both time out (I think they're supposed to?), but host 114.77.86.29 returns some domain name pointer involving my ISP which sounds good. nslookup piemaster.net returns my IP as a non-authoritative answer which is good, I think, but both host ns1.piemaster.net and host ns1.drumtaboo.info time out. I just set my piemaster.net name servers back to ns1 and ns2.piemaster.net a few hours ago, but I haven't touched drumtaboo.info in ages. So that's probably a problem. All those tests ehcpdeveloper was doing before all seem to work though.

So feel free to yell at me for being such a dunce, but what should I try now that it's at least semi-correctly set up? Thanks you all so much for your patience btw.

Restored from old drupal forum, for user uid:2648 username:Mir
You may reset your password to access your new account here.

[ehcpdeveloper]

I did a small check on your site,
I found:
<code>
# host piemaster.net
piemaster.net has address 114.77.86.29
# host www.piemaster.net
www.piemaster.net has address 67.19.72.202
</code>

This means, you did not redirect all subdomains of your piemaster.net to your server..
you should redirect all dns or all subdomains (especially www subdomain, yes, www is also a subdomain) of your domain to your ip of 114.77......

Otherwise, outside world cannot see your pages..

Another note, from outside, when anyone types: http://114.77..... they should not see your piemaster.net normally, instead, they should see default ehcp homepage.. you can change that, but default behaviour is like that.

As I see, you miss something essential, like dns redirection.
I suggest you to use your own dns (your server), to do that, redirect to your server from where you bought your domain.


I should say that, running a website is not so hard.. many people do it with little work.. just follow simple steps..


Restored from old drupal forum, for user uid:2719 usernameie21
You may reset your password to access your new account here.

[Pie21]

Ah right, I forgot to delete my piemaster.net domain at FreeDNS, which I've just done now. That didn't redirect the www address, but that may have been a good idea. I wasn't aware it was necessary, and I was just tying to fiddle as little as possible.

I also hadn't updated the GoDaddy name servers *facepalm* I am easily confused when doing 4 things at once. Give it all a sec to update

Restored from old drupal forum, for user uid:1 username:ehcpdeveloper
You may reset your password to access your new account here.

[Mir]

A 192.168.x.y IP address is reserved for private networks and is not valid on the internet, therefore your router must be performing NAT. Your router has an address that is connected to the internet(115.77.86.29), you'll need to know what this is to get inbound access to your server.

Your server must have it's 192.168.x.y address staticly set. You'll configure your router to forward port 80 to 192.168.0.198 (or whatever your server's Ip address is). Then, from elsewhere on the internet you can enter 1.2.3.4 to connect to your server (where 1.2.3.4 is the publicly accessible IP address on your router).



To forward port 80 on your dlink dir-635:
<a href="http://portforward.com/english/routers/port_forwarding/Dlink/DIR-635/Apache.htm">http://portforward.com/english/routers/port_forwarding/Dlink/DIR-635/Apache.htm</a>



Restored from old drupal forum, for user uid:2719 usernameie21
You may reset your password to access your new account here.

[Pie21]

I understand that 192.168.0.x is internal, and I have forwarded all the important ports (afaik), especially 80 and 53, using the D-Link Virtual Server page, which is apparently just port forwarding but for individual ports. My laptop (server) is statically assigned to 192.168.0.198 within the network, and said ports are all forwarded to 192.168.0.198. Not only that but my laptop is DMZ'd as well, so I can't think of any way to increase its availability. MAC Address filtering is off - that's correct for static IP's, right?

Anyway, the fact remains that 114.77.86.29 fails when accessed publicly, as do piemaster.net (using 114.77.86.29 as both name servers) and drumtaboo.info (using the standard GoDaddy name servers and the Total DNS tool).

Restored from old drupal forum, for user uid:2648 username:Mir
You may reset your password to access your new account here.

[Mir]

You could try other settings, i cant really help you that much. <a href="http://www.canyouseeme.org/">http://www.canyouseeme.org/</a> is a port checker, you can try to configure your router again, and see if port 80 is still blocked....


Sorry i couldnt help you fix it.

Restored from old drupal forum, for user uid:2719 usernameie21
You may reset your password to access your new account here.

[Pie21]

No, thank you for helping so much. It's easy to think of a server as either working or not working, but really there's a lot of stuff you have to do to get it working, and I wouldn't be anywhere near as close as I am without the support of you guys.

I tried out your link, and it can see all my ports except 80 (!), where it says:

<code>Error: I could not see your service on 114.77.86.29 on port (80)
Reason: No route to host</code>

You said ISPs may block port 80, so I put my HTTP proxy port 8080 back on, forwarding to port 80, and my friend can reach http://114.77.86.29/! But not http://114.77.86.29/. The question then is how can I set http://piemaster.net/ to point at http://114.77.86.29:8080/ instead of http://114.77.86.29/? I've set it in the dnsip field of EHCP, but it hasn't fixed anything... is this another situation where I just have to wait? I can't register 114.77.86.29:8080 as a name server with GoDaddy unfortunately (because it's a port, and not a server), but it seems to be able to reach port 53 okay. Is there anything else I have to change to set make the :8080 part of piemaster.net?

EDIT: http://piemaster.net:8080/ WORKS! It's not ideal though, obviously. Is it even possible to make :8080 the default port for the domain? I would've thought that's what dnsip would do, but if it could be anything else, I'll certainly try that.

Also, I managed to lose my old .htaccess file... where should I put the new one that I'll have to write from scratch? In piemaster.net/httpdocs/?

Thanks again!

Restored from old drupal forum, for user uid:2648 username:Mir
You may reset your password to access your new account here.