How can I host a website from my home machine? I have a DynDNS address so that even if my external IP changes, the machine is accessible.

Lets say, for example, the machine is accessible at example.dyndns-home.com (this is a free service from DynDNS). I've registered a domain name for my website from GoDaddy. Let's say that domain name is example.com

Right now, I've forwarded port 80 so I can enter example.dyndns-home.com from anywhere and I can see whatever I've hosted at my homebox.

How can I make it so that, when I enter www.example.com, I see the same thing? I want to see what I host on my home machine out on the internet via example.com.

migrated from superuser.com Mar 8 '12 at 23:54

This question came from our site for computer enthusiasts and power users.

  • There should be an option from your domain registrar to let the domain point to something else, in this case your DynDNS address. – slhck Mar 8 '12 at 19:35
  • Do you mean forwarding? so when someone says www.example.com, they are taken to example.dyndns-home.com ? – hari Mar 8 '12 at 19:39
  • Personally, I don't like adding unnecessary hops if it can be avoided. You should be able to point your domain to the IP address of your home router. If your ISP provides a Static IP address then this would solve your problems. If not, you could always ask your ISP what the lease time of the IP addresses are and then ask if they have sticky ip addresses. Personally, I've swapped service packages, modems, and routers and never lost my IP address since it is a Sticky Dynamic IP. – kobaltz Mar 8 '12 at 22:03

Add a cname record to the DNS record for your domain, pointing from www.example.com to example.dyndns-home.com. I've only ever used one domain registrar (not Godaddy), but they have a neat web interface where you can update the DNS record.

Raw example:


Working example is provided, at least using Google's nameservers.

Edit (twice):

If you wanted http://example.com to work too, you must add a second entry from example.com to example.dyndns-home.com. This might be done by forwarding @.example.com, I don't know if that's standard or not.

  • Thanks Eroen. I do not want anyone to ever see example.dyndns-home.com in their address-bar or anywhere else. is that possible? – hari Mar 8 '12 at 19:47
  • 3
    Sure, as long as the web server claims to be www.example.com and does not redirect to example.dyndns-home.com. – Eroen Mar 8 '12 at 19:52
  • 1
    Thank you! I've just made this change. Let it propagate! I will report back. – hari Mar 8 '12 at 20:05
  • 1
    I don't know if you mean in the DNS record or on your computer, but if it works for the first case, you will likely break something if you change it. In the second case, you probably want to use Godaddy's servers while you are changing stuff, so you won't have to wait for caches to be refreshed before testing. – Eroen Mar 8 '12 at 21:35
  • 1
    Think of the nameserver records for your domain as the thing that advertises where your DNS records are. If you change your nameservers then the records on godaddy will do nothing, so you'd have to enter those records at the location you set the name server to. – ridogi Mar 8 '12 at 21:49

Finally i know What is the problem ? For me My ISP block port 80 and 8080 So i configure My Website to work with another port For Example :


1- I register for 14 Trial Days in Dyn Standard Dns

2- I configure my domain with the DNS from dyndns


3- I create anew WebHop to forward my Domain To My DynDns Domain For Example

Host-name  : example.com    

Service    : WebHop 

Details    : http://example.dyndns.org:5060 

Assuming you have a server running Linux, and you are looking to update a DNS A record with the IP of your home server on DNS hosted by GoDaddy, you could do the following on the home server. Note that it my violate your EULA. Be sure that you follow the rules!

  1. Install Python2.7 (it is likely already installed).

  2. Place the following file at /config/scripts/godaddy_ddns.py. It is the part that does the actual work of updating godaddy using the pygodaddy library. It will update all domains associated with your godaddy account. It will set an A record for the '@' subdomain wildcard. You can edit this, if you want to specify alternate subdomains. You must also replace '@USERNAME@' with your godaddy username and '@PASSWORD@' with your godaddy password.

    #!/usr/bin/env python
    import logging
    import pif
    import pygodaddy
    # Original Source:
    # https://saschpe.wordpress.com/2013/11/12/godaddy-dyndns-for-the-poor/
    # https://github.com/observerss/pygodaddy
    # Modified by Jeremy Sears (https://stackoverflow.com/users/1240482/jsears)
    logging.basicConfig(filename='godaddy.log', format='%(asctime)s %(message)s', level=logging.INFO)
    # the "requests" library logs noisily, so turn that off                                                       
    logging.debug("DEBUG:   Running godaddy_ddns.py");
    client = pygodaddy.GoDaddyClient()                       
    success = client.login(U,P)                              
    if success:                                                                                      
            logging.debug("DEBUG:   Successfully logged in.")                                        
            logging.error("ERROR:   Failed to log in to godaddy.com with username: '{0}'.".format(U))
    for domain in client.find_domains():                                            
            logging.debug("DEBUG:   Looking up DNS Records for {0}.".format(domain))           
            dns_records = client.find_dns_records(domain)                                      
            public_ip = pif.get_public_ip()                                                    
            logging.debug("DEBUG:   Domain '{0}' DNS records: {1}".format(domain, dns_records))
            logging.debug("DEBUG:   Current Public IP '{0}'.".format(public_ip))
            if len(dns_records) == 0:                                                                  
                    logging.debug("DEBUG:   No existing DNS records found.")                           
                    logging.debug("DEBUG:   Existing IP in DNS is '{0}'.".format(dns_records[0].value))
            if len(dns_records) == 0 or public_ip != dns_records[0].value:                      
                    logging.debug("DEBUG:   Updating A record for domain '{0}'.".format(domain))                                  
                    success = client.update_dns_record("@."+domain, public_ip)                                                    
                    if success:                                                                                                   
                            logging.info("INFO:     Domain '{0}': Successfully set public IP to '{1}'.".format(domain, public_ip))
                            logging.error("ERROR:   Domain '{0}': Unable to update public IP to '{1}'.".format(domain, public_ip))                         
                    logging.info("INFO:     Public IP A record DNS record for domain '{0}' is up to date, and does not need to be updated.".format(domain))
  3. Run sudo chown root /config/scripts/godaddy_ddns.py

  4. Run sudo chmod u+x /config/scripts/godaddy_ddns.py
  5. Place the following file at /config/scripts/godaddy_ddns.sh. This is a wrapper script that sets up a virtualenv to isolate the libraries used by the python script. It then invokes the above python script.

    # Original Source:
    # https://saschpe.wordpress.com/2013/11/12/godaddy-dyndns-for-the-poor/
    # https://github.com/observerss/pygodaddy
    # Modified by Jeremy Sears (https://stackoverflow.com/users/1240482/jsears)
    ROOT_DIR=$(dirname $0)
    if [ -n "$1" ] ; then
    mkdir -p $WORKING_DIR
    if [ ! -d .venv27 ] ; then
        curl -O https://pypi.python.org/packages/source/v/virtualenv/virtualenv-1.9.tar.gz
        tar xvfz virtualenv-1.9.tar.gz
        python virtualenv-1.9/virtualenv.py .venv27
    source .venv27/bin/activate
    pip install -q --upgrade pif pygodaddy
    cd $OLD_PWD
  6. Run sudo chown root /config/scripts/godaddy_ddns.sh

  7. Run sudo chmod u+x /config/scripts/godaddy_ddns.sh
  8. Place the following file at /etc/cron.hourly/run_godaddy_ddns (no file extension). This will call the godaddy_ddns.sh script each hour.

    exec /config/scripts/godaddy_ddns.sh $WORKING_DIR     
    exit 0                                                
  9. Run sudo chown root /etc/cron.hourly/run_godaddy_ddns

  10. Run sudo chmod u+x /etc/cron.hourly/run_godaddy_ddns
  11. Logs will be written to godaddy.log in the /var/local/godaddy_ddns directory. This directory can be changed by editing the run_godaddy_ddns script.
  12. Place the following file at /etc/logrotate.d/godaddy_ddns (no file extension). This will ensure that your log file doesn't fill up your disk, by rotating the log file. If you changed the logging location, you will need to edit the log file location.

    /var/local/godaddy_ddns/godaddy.log {
        rotate 12
        maxage 365                                                       
  13. You will also need to add a CNAME record in the GoDaddy domain manager to point 'www' to '@'

Security Note: You probably should edit the run_godaddy_ddns script and su to a user other than root, so that the script is run with more limited permissions.

  • OP simply asked to have his now domain point to the domain he registered with dyndns. For this you suggest installing Python, and close to 100 or more lines of code? – Matt Jan 12 '18 at 13:41

Register/move your domain to a registrar that supports Dynamic DNS functionality. Namecheap.com is one such registrar. Instructions are in their knowledgebase. Note that you can enable dynamic DNS for a subdomain by creating a subdomain entry of type 'A+ Dynamic DNS'.

The default config for ddclient package (on Arch Linux, at least) includes the settings for this registrar's protocol:

## NameCheap (namecheap.com)
protocol=namecheap,                     \
server=dynamicdns.park-your-domain.com, \
login=YOUR-TOP-LEVEL-DOMAIN,            \

Your Answer

By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.

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