Take the 2-minute tour ×
Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Since our ISP doesn't provide static IP, I am using a dynamic dns service to access a Windows server from the internet,

now I would like to expose a static web page to the net using a domain name that I just registered (ie: mydomain.tld not mydomaine.dynprovider.tld)

In IIS 7 -> Web site -> binding, I tried to set dynamic host instead of IP but found that this was not possible.

So, I wonder how to make binding for this web site, in order to make it pointing to the host dynamic IP.

share|improve this question
    
Have you changed the DNS settings of the web hostname to that of the DNS ones? –  Jake Elsley Nov 13 '12 at 13:28
    
I have not installed any DNS role on the server, and Dynamic DNS provider have the right settings which enable me to access the server remotely. –  Sami-L Nov 13 '12 at 13:55
1  
Are you binding the public ip address directly to the server NIC? This would be a whole lot easier if you bind an RFC 1918 ip address to the server and let your network firewall/router port forward from the public ip address to the private ip address. –  joeqwerty Nov 13 '12 at 14:56
    
@joeqwerty, glad to see you, my server is behind a shared connection (firewall/router), port forwarding is active and private ip address is fixed. –  Sami-L Nov 13 '12 at 15:14
1  
OK, so then you don't need to bind the web site to anything other than the private ip address on the server. The router/firewall will forward port 80 from the public ip address to the private ip address on the server. What it sounds like you want to do is to make sure that your public DNS correctly resolves to the public ip address. To do that you would install and configure a dynamic DNS client on the server so that the server can detect the public ip address and update the DNS record at your dynamic DNS provider. –  joeqwerty Nov 13 '12 at 15:22

1 Answer 1

up vote 0 down vote accepted

The most important part of the answer to this question was given by @joeqwerty above, I only continued the research since he could not imagine all the scenario.

Since I found that generaly Dynamic DNS providers give 1 to 3 hostnames (host.dynamicdnsprovider.tld type) free for 30 days, then one have to buy 1 service per domaine (mydomain.tld type) each one 2x to 3x expensiver than a static IP, at this time DNS for each domain could be managed into dynamic dns provider control panel, so I returned back to my registrar which provides dynamic dns service for each registered domain but do not support or have any Client updater, then I searched for third party client updaters on the net and finaly found one shareware which can support my registrar dyn services, run in background as windows service, and point multiple domains to the dynamic IP. That way I can manage dns records at my registrar, and use its name servers.

Now this is the second day updating, yesterday the server restarted after a Windows update, and dns client updater restarted automaticaly.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.