4 replies to this topic

[JayUK20]

I've really hit a brickwall and not sure what else to do.

I am testing a website but it cannot be displayed locally or through the Internet.

First of all I have PowerDNS setup with my domain and WAN IP and then setup a DNS forwarder with the following settings:

Oh my IIS bindings are mydomain.com/My WAN IP/Port 80

[Nas]

A few comments:
1. Your forwarder has the "www" prefix... that usually isn't necessary. You'll usually setup the "www" as a CNAME to the root domain entry.
2. Your firewalls may very well not allow traffic through Port 80 unless explicitly configured.
3. Your inability to review LOCALLY (127.0.0.1 or localhost) means your IIS is not routing properly. In other words, your IIS Binding needs additional entries (or simply leave the space blank; all traffic would listen to port 80).

[JayUK20]

Ok well I have opened up port 80 on the server from in my router and with the bindings I tried removing my domain name and left it blank and the localhost displayed the IIS start page. Also I remove the www. prefix.

[+BudMan]

Not sure why you feel you need to setup an authoritative zone for this on your local dns pointing to the public IP? You would only do this if you wanted to point your local clients to the private IP of the iis server.

Which would be common practice.

Also you can have lots of problems testing a websites public IP from internally, this is nat reflection, or loopback forwarding, etc. Not all routers support this and quite often does not work.

You normally access a local webserver with its local IP, and setup a forward on your router for public clients to access the public IP which is forwarded to the private IP.

Powerdns handles your public dns - does it not? So there is no reason to setup a local copy of this to point to the public IP.

[olger901]

Actually a server directly connected to the with internet with a public IP address should be in a DMZ and shouldn't have any private IP addresses. Then you wouldn't be having this problem.