IP address is shown in address bar instead of domain











up vote
2
down vote

favorite
2












I have a WAMP home web server up and running on a static IP and registered a domain with Namecheap, but I'm a bit shaky with DNS. At first I used URL Redirect and pointed it to my IP. This meant that when you typed in the domain (like example.com) it just redirected you right to my IP, replacing the domain name with it in the address bar. Now I'm trying to get the domain to show instead of the IP in the address bar, which I'm struggling to understand exactly how to do.



The latest thing I've tried which many people say to do is instead of using URL Redirect to use the A (Address) record type and point it to my IP, which I thought would finally fix my problems. Of course after 15 min or so when it all got updated I'm getting a 400 Bad Request with nginx under it in Firefox, and a blank page in Chrome. Now I'm getting blank pages in both. Did I do something wrong here? Do I need to edit something on the web server such as httpd.conf? Am I going at this completely wrong?










share|improve this question






















  • Question about server installation and configuration could be asked at serverfault.com
    – F. Hauri
    Sep 20 '16 at 6:39















up vote
2
down vote

favorite
2












I have a WAMP home web server up and running on a static IP and registered a domain with Namecheap, but I'm a bit shaky with DNS. At first I used URL Redirect and pointed it to my IP. This meant that when you typed in the domain (like example.com) it just redirected you right to my IP, replacing the domain name with it in the address bar. Now I'm trying to get the domain to show instead of the IP in the address bar, which I'm struggling to understand exactly how to do.



The latest thing I've tried which many people say to do is instead of using URL Redirect to use the A (Address) record type and point it to my IP, which I thought would finally fix my problems. Of course after 15 min or so when it all got updated I'm getting a 400 Bad Request with nginx under it in Firefox, and a blank page in Chrome. Now I'm getting blank pages in both. Did I do something wrong here? Do I need to edit something on the web server such as httpd.conf? Am I going at this completely wrong?










share|improve this question






















  • Question about server installation and configuration could be asked at serverfault.com
    – F. Hauri
    Sep 20 '16 at 6:39













up vote
2
down vote

favorite
2









up vote
2
down vote

favorite
2






2





I have a WAMP home web server up and running on a static IP and registered a domain with Namecheap, but I'm a bit shaky with DNS. At first I used URL Redirect and pointed it to my IP. This meant that when you typed in the domain (like example.com) it just redirected you right to my IP, replacing the domain name with it in the address bar. Now I'm trying to get the domain to show instead of the IP in the address bar, which I'm struggling to understand exactly how to do.



The latest thing I've tried which many people say to do is instead of using URL Redirect to use the A (Address) record type and point it to my IP, which I thought would finally fix my problems. Of course after 15 min or so when it all got updated I'm getting a 400 Bad Request with nginx under it in Firefox, and a blank page in Chrome. Now I'm getting blank pages in both. Did I do something wrong here? Do I need to edit something on the web server such as httpd.conf? Am I going at this completely wrong?










share|improve this question













I have a WAMP home web server up and running on a static IP and registered a domain with Namecheap, but I'm a bit shaky with DNS. At first I used URL Redirect and pointed it to my IP. This meant that when you typed in the domain (like example.com) it just redirected you right to my IP, replacing the domain name with it in the address bar. Now I'm trying to get the domain to show instead of the IP in the address bar, which I'm struggling to understand exactly how to do.



The latest thing I've tried which many people say to do is instead of using URL Redirect to use the A (Address) record type and point it to my IP, which I thought would finally fix my problems. Of course after 15 min or so when it all got updated I'm getting a 400 Bad Request with nginx under it in Firefox, and a blank page in Chrome. Now I'm getting blank pages in both. Did I do something wrong here? Do I need to edit something on the web server such as httpd.conf? Am I going at this completely wrong?







apache dns wamp wampserver






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked May 27 '13 at 6:40









Cains

40321120




40321120












  • Question about server installation and configuration could be asked at serverfault.com
    – F. Hauri
    Sep 20 '16 at 6:39


















  • Question about server installation and configuration could be asked at serverfault.com
    – F. Hauri
    Sep 20 '16 at 6:39
















Question about server installation and configuration could be asked at serverfault.com
– F. Hauri
Sep 20 '16 at 6:39




Question about server installation and configuration could be asked at serverfault.com
– F. Hauri
Sep 20 '16 at 6:39












3 Answers
3






active

oldest

votes

















up vote
1
down vote













Yes you should do away with the redirect and instead create an "A record". The sub-domain entry would typically be, but is not restricted to "www". The record type "A" and destination/target would be your external IP address. Once you update this record it may take several hours before you notice it taking effecting, upon where on people typing your URL would be directed to your web server.



You will need to forward port 80 on your router to the server hosting WAMP.



Finally the WAMP server should be provided with your domain name so it knows which site to load. If use the VirtualHost file this will allow you to host multiple domains on your web server. To do this...



Uncomment the following line so it appears like below in your Apache httpd.conf, to allow Apache to use virutal hosts



# Virtual hosts
Include conf/extra/httpd-vhosts.conf


Then locate the httpd-vhosts.conf file, should be found in your WAMP installation location, such as C:wampbinapacheapache*version_number*confextra



Add an entry for your site, altering the details to your own domain name and website location.



<VirtualHost *:80>
ServerName www.stackoverflow.com
ServerAlias stackoverflow.com
DocumentRoot "C:/websites/stackoverflow/"
ErrorLog "C:/websites/stackoverflow/logs/error.log"
CustomLog "C:/websites/stackoverflow/logs/access.log" common
</VirtualHost>


Now restart your WAMP server and give it a whirl.



Tip: If your server won't start after these changes, check that you have created the folder structure for the log files!






share|improve this answer





















  • I also posted this on Namecheap, where my domain is registered, and their response was similar to yours (other than editing my hosts file), and for the most part it works. Unfortunately while mydomain.net works, www.mydomain.net gives a blank page. A records for mydomain.net and www.mydomain.net are created for my external IP. link is my hosts file, and link is my VH setup.
    – Cains
    May 27 '13 at 21:29










  • You shouldn't really need to edit your HOSTS file, this will only effect your PC locally, not for external user. If you only want this locally then there was no need to even purchase a domain! If you are wanting it to be visible to the outside world then don't touch the host file, instead create a DNS A record... DNS will then resolve to the correct location. Then open port 80 (port forward) on your router to ensure visitors get directed to the webserver itself. If you only want to do it locally you can just add an additonal line to your HOSTS file for WWW. ps vhosts file looks fine :)
    – robert_longworth
    May 28 '13 at 18:07












  • Many of the articles I've seen on vhost have been for local setups rather than domains so that probably caused that confusion, thanks for clearing it up. With DNS A records for mydomain.net and www.mydomain.net pointing to my IP and that vhost setup I have the problem of mydomain.net working fine and www.mydomain.net turning up a blank page. Any idea why this would be? I'm really stumped. For now I just have www.mydomain.net redirecting to mydomain.net but I'd prefer to not do it this way.
    – Cains
    May 29 '13 at 19:23


















up vote
1
down vote













Solution described here could resolve this issue.



Most of the free dynamic dns providers, allow acquiring more than one free host name. If allowed you can solve the problem by getting a second name, e.g., mysite2.somefree.org.
Now, go and configure your free domain names in the dashboard of free provider in the following way (assume your IP is 188.165.15.29 and your server's listening to port 8085).




  • redirect mysite1.somefree.org to mysite2.somefree.org:8085

  • redirect mysite2.somefree.org to your dynamic IP, say, to 188.165.15.29


This also works when you are using Apache httpd server alone, not being part of WAMP. You do not need to tweak virtual host or any part of your server. You only configure inbound direction.






share|improve this answer




























    up vote
    0
    down vote













    Use Forward with masking where you registered your domain. mine is GoDaddy.
    in the forward settings, you will see this at bottom of the page. click Forward with masking and add the title you want them to see in the address bar of the browser when they go to your site. instead of showing your IP address






    share|improve this answer























      Your Answer






      StackExchange.ifUsing("editor", function () {
      StackExchange.using("externalEditor", function () {
      StackExchange.using("snippets", function () {
      StackExchange.snippets.init();
      });
      });
      }, "code-snippets");

      StackExchange.ready(function() {
      var channelOptions = {
      tags: "".split(" "),
      id: "1"
      };
      initTagRenderer("".split(" "), "".split(" "), channelOptions);

      StackExchange.using("externalEditor", function() {
      // Have to fire editor after snippets, if snippets enabled
      if (StackExchange.settings.snippets.snippetsEnabled) {
      StackExchange.using("snippets", function() {
      createEditor();
      });
      }
      else {
      createEditor();
      }
      });

      function createEditor() {
      StackExchange.prepareEditor({
      heartbeatType: 'answer',
      convertImagesToLinks: true,
      noModals: true,
      showLowRepImageUploadWarning: true,
      reputationToPostImages: 10,
      bindNavPrevention: true,
      postfix: "",
      imageUploader: {
      brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
      contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
      allowUrls: true
      },
      onDemand: true,
      discardSelector: ".discard-answer"
      ,immediatelyShowMarkdownHelp:true
      });


      }
      });














       

      draft saved


      draft discarded


















      StackExchange.ready(
      function () {
      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f16767624%2fip-address-is-shown-in-address-bar-instead-of-domain%23new-answer', 'question_page');
      }
      );

      Post as a guest















      Required, but never shown

























      3 Answers
      3






      active

      oldest

      votes








      3 Answers
      3






      active

      oldest

      votes









      active

      oldest

      votes






      active

      oldest

      votes








      up vote
      1
      down vote













      Yes you should do away with the redirect and instead create an "A record". The sub-domain entry would typically be, but is not restricted to "www". The record type "A" and destination/target would be your external IP address. Once you update this record it may take several hours before you notice it taking effecting, upon where on people typing your URL would be directed to your web server.



      You will need to forward port 80 on your router to the server hosting WAMP.



      Finally the WAMP server should be provided with your domain name so it knows which site to load. If use the VirtualHost file this will allow you to host multiple domains on your web server. To do this...



      Uncomment the following line so it appears like below in your Apache httpd.conf, to allow Apache to use virutal hosts



      # Virtual hosts
      Include conf/extra/httpd-vhosts.conf


      Then locate the httpd-vhosts.conf file, should be found in your WAMP installation location, such as C:wampbinapacheapache*version_number*confextra



      Add an entry for your site, altering the details to your own domain name and website location.



      <VirtualHost *:80>
      ServerName www.stackoverflow.com
      ServerAlias stackoverflow.com
      DocumentRoot "C:/websites/stackoverflow/"
      ErrorLog "C:/websites/stackoverflow/logs/error.log"
      CustomLog "C:/websites/stackoverflow/logs/access.log" common
      </VirtualHost>


      Now restart your WAMP server and give it a whirl.



      Tip: If your server won't start after these changes, check that you have created the folder structure for the log files!






      share|improve this answer





















      • I also posted this on Namecheap, where my domain is registered, and their response was similar to yours (other than editing my hosts file), and for the most part it works. Unfortunately while mydomain.net works, www.mydomain.net gives a blank page. A records for mydomain.net and www.mydomain.net are created for my external IP. link is my hosts file, and link is my VH setup.
        – Cains
        May 27 '13 at 21:29










      • You shouldn't really need to edit your HOSTS file, this will only effect your PC locally, not for external user. If you only want this locally then there was no need to even purchase a domain! If you are wanting it to be visible to the outside world then don't touch the host file, instead create a DNS A record... DNS will then resolve to the correct location. Then open port 80 (port forward) on your router to ensure visitors get directed to the webserver itself. If you only want to do it locally you can just add an additonal line to your HOSTS file for WWW. ps vhosts file looks fine :)
        – robert_longworth
        May 28 '13 at 18:07












      • Many of the articles I've seen on vhost have been for local setups rather than domains so that probably caused that confusion, thanks for clearing it up. With DNS A records for mydomain.net and www.mydomain.net pointing to my IP and that vhost setup I have the problem of mydomain.net working fine and www.mydomain.net turning up a blank page. Any idea why this would be? I'm really stumped. For now I just have www.mydomain.net redirecting to mydomain.net but I'd prefer to not do it this way.
        – Cains
        May 29 '13 at 19:23















      up vote
      1
      down vote













      Yes you should do away with the redirect and instead create an "A record". The sub-domain entry would typically be, but is not restricted to "www". The record type "A" and destination/target would be your external IP address. Once you update this record it may take several hours before you notice it taking effecting, upon where on people typing your URL would be directed to your web server.



      You will need to forward port 80 on your router to the server hosting WAMP.



      Finally the WAMP server should be provided with your domain name so it knows which site to load. If use the VirtualHost file this will allow you to host multiple domains on your web server. To do this...



      Uncomment the following line so it appears like below in your Apache httpd.conf, to allow Apache to use virutal hosts



      # Virtual hosts
      Include conf/extra/httpd-vhosts.conf


      Then locate the httpd-vhosts.conf file, should be found in your WAMP installation location, such as C:wampbinapacheapache*version_number*confextra



      Add an entry for your site, altering the details to your own domain name and website location.



      <VirtualHost *:80>
      ServerName www.stackoverflow.com
      ServerAlias stackoverflow.com
      DocumentRoot "C:/websites/stackoverflow/"
      ErrorLog "C:/websites/stackoverflow/logs/error.log"
      CustomLog "C:/websites/stackoverflow/logs/access.log" common
      </VirtualHost>


      Now restart your WAMP server and give it a whirl.



      Tip: If your server won't start after these changes, check that you have created the folder structure for the log files!






      share|improve this answer





















      • I also posted this on Namecheap, where my domain is registered, and their response was similar to yours (other than editing my hosts file), and for the most part it works. Unfortunately while mydomain.net works, www.mydomain.net gives a blank page. A records for mydomain.net and www.mydomain.net are created for my external IP. link is my hosts file, and link is my VH setup.
        – Cains
        May 27 '13 at 21:29










      • You shouldn't really need to edit your HOSTS file, this will only effect your PC locally, not for external user. If you only want this locally then there was no need to even purchase a domain! If you are wanting it to be visible to the outside world then don't touch the host file, instead create a DNS A record... DNS will then resolve to the correct location. Then open port 80 (port forward) on your router to ensure visitors get directed to the webserver itself. If you only want to do it locally you can just add an additonal line to your HOSTS file for WWW. ps vhosts file looks fine :)
        – robert_longworth
        May 28 '13 at 18:07












      • Many of the articles I've seen on vhost have been for local setups rather than domains so that probably caused that confusion, thanks for clearing it up. With DNS A records for mydomain.net and www.mydomain.net pointing to my IP and that vhost setup I have the problem of mydomain.net working fine and www.mydomain.net turning up a blank page. Any idea why this would be? I'm really stumped. For now I just have www.mydomain.net redirecting to mydomain.net but I'd prefer to not do it this way.
        – Cains
        May 29 '13 at 19:23













      up vote
      1
      down vote










      up vote
      1
      down vote









      Yes you should do away with the redirect and instead create an "A record". The sub-domain entry would typically be, but is not restricted to "www". The record type "A" and destination/target would be your external IP address. Once you update this record it may take several hours before you notice it taking effecting, upon where on people typing your URL would be directed to your web server.



      You will need to forward port 80 on your router to the server hosting WAMP.



      Finally the WAMP server should be provided with your domain name so it knows which site to load. If use the VirtualHost file this will allow you to host multiple domains on your web server. To do this...



      Uncomment the following line so it appears like below in your Apache httpd.conf, to allow Apache to use virutal hosts



      # Virtual hosts
      Include conf/extra/httpd-vhosts.conf


      Then locate the httpd-vhosts.conf file, should be found in your WAMP installation location, such as C:wampbinapacheapache*version_number*confextra



      Add an entry for your site, altering the details to your own domain name and website location.



      <VirtualHost *:80>
      ServerName www.stackoverflow.com
      ServerAlias stackoverflow.com
      DocumentRoot "C:/websites/stackoverflow/"
      ErrorLog "C:/websites/stackoverflow/logs/error.log"
      CustomLog "C:/websites/stackoverflow/logs/access.log" common
      </VirtualHost>


      Now restart your WAMP server and give it a whirl.



      Tip: If your server won't start after these changes, check that you have created the folder structure for the log files!






      share|improve this answer












      Yes you should do away with the redirect and instead create an "A record". The sub-domain entry would typically be, but is not restricted to "www". The record type "A" and destination/target would be your external IP address. Once you update this record it may take several hours before you notice it taking effecting, upon where on people typing your URL would be directed to your web server.



      You will need to forward port 80 on your router to the server hosting WAMP.



      Finally the WAMP server should be provided with your domain name so it knows which site to load. If use the VirtualHost file this will allow you to host multiple domains on your web server. To do this...



      Uncomment the following line so it appears like below in your Apache httpd.conf, to allow Apache to use virutal hosts



      # Virtual hosts
      Include conf/extra/httpd-vhosts.conf


      Then locate the httpd-vhosts.conf file, should be found in your WAMP installation location, such as C:wampbinapacheapache*version_number*confextra



      Add an entry for your site, altering the details to your own domain name and website location.



      <VirtualHost *:80>
      ServerName www.stackoverflow.com
      ServerAlias stackoverflow.com
      DocumentRoot "C:/websites/stackoverflow/"
      ErrorLog "C:/websites/stackoverflow/logs/error.log"
      CustomLog "C:/websites/stackoverflow/logs/access.log" common
      </VirtualHost>


      Now restart your WAMP server and give it a whirl.



      Tip: If your server won't start after these changes, check that you have created the folder structure for the log files!







      share|improve this answer












      share|improve this answer



      share|improve this answer










      answered May 27 '13 at 9:09









      robert_longworth

      361




      361












      • I also posted this on Namecheap, where my domain is registered, and their response was similar to yours (other than editing my hosts file), and for the most part it works. Unfortunately while mydomain.net works, www.mydomain.net gives a blank page. A records for mydomain.net and www.mydomain.net are created for my external IP. link is my hosts file, and link is my VH setup.
        – Cains
        May 27 '13 at 21:29










      • You shouldn't really need to edit your HOSTS file, this will only effect your PC locally, not for external user. If you only want this locally then there was no need to even purchase a domain! If you are wanting it to be visible to the outside world then don't touch the host file, instead create a DNS A record... DNS will then resolve to the correct location. Then open port 80 (port forward) on your router to ensure visitors get directed to the webserver itself. If you only want to do it locally you can just add an additonal line to your HOSTS file for WWW. ps vhosts file looks fine :)
        – robert_longworth
        May 28 '13 at 18:07












      • Many of the articles I've seen on vhost have been for local setups rather than domains so that probably caused that confusion, thanks for clearing it up. With DNS A records for mydomain.net and www.mydomain.net pointing to my IP and that vhost setup I have the problem of mydomain.net working fine and www.mydomain.net turning up a blank page. Any idea why this would be? I'm really stumped. For now I just have www.mydomain.net redirecting to mydomain.net but I'd prefer to not do it this way.
        – Cains
        May 29 '13 at 19:23


















      • I also posted this on Namecheap, where my domain is registered, and their response was similar to yours (other than editing my hosts file), and for the most part it works. Unfortunately while mydomain.net works, www.mydomain.net gives a blank page. A records for mydomain.net and www.mydomain.net are created for my external IP. link is my hosts file, and link is my VH setup.
        – Cains
        May 27 '13 at 21:29










      • You shouldn't really need to edit your HOSTS file, this will only effect your PC locally, not for external user. If you only want this locally then there was no need to even purchase a domain! If you are wanting it to be visible to the outside world then don't touch the host file, instead create a DNS A record... DNS will then resolve to the correct location. Then open port 80 (port forward) on your router to ensure visitors get directed to the webserver itself. If you only want to do it locally you can just add an additonal line to your HOSTS file for WWW. ps vhosts file looks fine :)
        – robert_longworth
        May 28 '13 at 18:07












      • Many of the articles I've seen on vhost have been for local setups rather than domains so that probably caused that confusion, thanks for clearing it up. With DNS A records for mydomain.net and www.mydomain.net pointing to my IP and that vhost setup I have the problem of mydomain.net working fine and www.mydomain.net turning up a blank page. Any idea why this would be? I'm really stumped. For now I just have www.mydomain.net redirecting to mydomain.net but I'd prefer to not do it this way.
        – Cains
        May 29 '13 at 19:23
















      I also posted this on Namecheap, where my domain is registered, and their response was similar to yours (other than editing my hosts file), and for the most part it works. Unfortunately while mydomain.net works, www.mydomain.net gives a blank page. A records for mydomain.net and www.mydomain.net are created for my external IP. link is my hosts file, and link is my VH setup.
      – Cains
      May 27 '13 at 21:29




      I also posted this on Namecheap, where my domain is registered, and their response was similar to yours (other than editing my hosts file), and for the most part it works. Unfortunately while mydomain.net works, www.mydomain.net gives a blank page. A records for mydomain.net and www.mydomain.net are created for my external IP. link is my hosts file, and link is my VH setup.
      – Cains
      May 27 '13 at 21:29












      You shouldn't really need to edit your HOSTS file, this will only effect your PC locally, not for external user. If you only want this locally then there was no need to even purchase a domain! If you are wanting it to be visible to the outside world then don't touch the host file, instead create a DNS A record... DNS will then resolve to the correct location. Then open port 80 (port forward) on your router to ensure visitors get directed to the webserver itself. If you only want to do it locally you can just add an additonal line to your HOSTS file for WWW. ps vhosts file looks fine :)
      – robert_longworth
      May 28 '13 at 18:07






      You shouldn't really need to edit your HOSTS file, this will only effect your PC locally, not for external user. If you only want this locally then there was no need to even purchase a domain! If you are wanting it to be visible to the outside world then don't touch the host file, instead create a DNS A record... DNS will then resolve to the correct location. Then open port 80 (port forward) on your router to ensure visitors get directed to the webserver itself. If you only want to do it locally you can just add an additonal line to your HOSTS file for WWW. ps vhosts file looks fine :)
      – robert_longworth
      May 28 '13 at 18:07














      Many of the articles I've seen on vhost have been for local setups rather than domains so that probably caused that confusion, thanks for clearing it up. With DNS A records for mydomain.net and www.mydomain.net pointing to my IP and that vhost setup I have the problem of mydomain.net working fine and www.mydomain.net turning up a blank page. Any idea why this would be? I'm really stumped. For now I just have www.mydomain.net redirecting to mydomain.net but I'd prefer to not do it this way.
      – Cains
      May 29 '13 at 19:23




      Many of the articles I've seen on vhost have been for local setups rather than domains so that probably caused that confusion, thanks for clearing it up. With DNS A records for mydomain.net and www.mydomain.net pointing to my IP and that vhost setup I have the problem of mydomain.net working fine and www.mydomain.net turning up a blank page. Any idea why this would be? I'm really stumped. For now I just have www.mydomain.net redirecting to mydomain.net but I'd prefer to not do it this way.
      – Cains
      May 29 '13 at 19:23












      up vote
      1
      down vote













      Solution described here could resolve this issue.



      Most of the free dynamic dns providers, allow acquiring more than one free host name. If allowed you can solve the problem by getting a second name, e.g., mysite2.somefree.org.
      Now, go and configure your free domain names in the dashboard of free provider in the following way (assume your IP is 188.165.15.29 and your server's listening to port 8085).




      • redirect mysite1.somefree.org to mysite2.somefree.org:8085

      • redirect mysite2.somefree.org to your dynamic IP, say, to 188.165.15.29


      This also works when you are using Apache httpd server alone, not being part of WAMP. You do not need to tweak virtual host or any part of your server. You only configure inbound direction.






      share|improve this answer

























        up vote
        1
        down vote













        Solution described here could resolve this issue.



        Most of the free dynamic dns providers, allow acquiring more than one free host name. If allowed you can solve the problem by getting a second name, e.g., mysite2.somefree.org.
        Now, go and configure your free domain names in the dashboard of free provider in the following way (assume your IP is 188.165.15.29 and your server's listening to port 8085).




        • redirect mysite1.somefree.org to mysite2.somefree.org:8085

        • redirect mysite2.somefree.org to your dynamic IP, say, to 188.165.15.29


        This also works when you are using Apache httpd server alone, not being part of WAMP. You do not need to tweak virtual host or any part of your server. You only configure inbound direction.






        share|improve this answer























          up vote
          1
          down vote










          up vote
          1
          down vote









          Solution described here could resolve this issue.



          Most of the free dynamic dns providers, allow acquiring more than one free host name. If allowed you can solve the problem by getting a second name, e.g., mysite2.somefree.org.
          Now, go and configure your free domain names in the dashboard of free provider in the following way (assume your IP is 188.165.15.29 and your server's listening to port 8085).




          • redirect mysite1.somefree.org to mysite2.somefree.org:8085

          • redirect mysite2.somefree.org to your dynamic IP, say, to 188.165.15.29


          This also works when you are using Apache httpd server alone, not being part of WAMP. You do not need to tweak virtual host or any part of your server. You only configure inbound direction.






          share|improve this answer












          Solution described here could resolve this issue.



          Most of the free dynamic dns providers, allow acquiring more than one free host name. If allowed you can solve the problem by getting a second name, e.g., mysite2.somefree.org.
          Now, go and configure your free domain names in the dashboard of free provider in the following way (assume your IP is 188.165.15.29 and your server's listening to port 8085).




          • redirect mysite1.somefree.org to mysite2.somefree.org:8085

          • redirect mysite2.somefree.org to your dynamic IP, say, to 188.165.15.29


          This also works when you are using Apache httpd server alone, not being part of WAMP. You do not need to tweak virtual host or any part of your server. You only configure inbound direction.







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Oct 15 '15 at 20:47









          peter jones

          20827




          20827






















              up vote
              0
              down vote













              Use Forward with masking where you registered your domain. mine is GoDaddy.
              in the forward settings, you will see this at bottom of the page. click Forward with masking and add the title you want them to see in the address bar of the browser when they go to your site. instead of showing your IP address






              share|improve this answer



























                up vote
                0
                down vote













                Use Forward with masking where you registered your domain. mine is GoDaddy.
                in the forward settings, you will see this at bottom of the page. click Forward with masking and add the title you want them to see in the address bar of the browser when they go to your site. instead of showing your IP address






                share|improve this answer

























                  up vote
                  0
                  down vote










                  up vote
                  0
                  down vote









                  Use Forward with masking where you registered your domain. mine is GoDaddy.
                  in the forward settings, you will see this at bottom of the page. click Forward with masking and add the title you want them to see in the address bar of the browser when they go to your site. instead of showing your IP address






                  share|improve this answer














                  Use Forward with masking where you registered your domain. mine is GoDaddy.
                  in the forward settings, you will see this at bottom of the page. click Forward with masking and add the title you want them to see in the address bar of the browser when they go to your site. instead of showing your IP address







                  share|improve this answer














                  share|improve this answer



                  share|improve this answer








                  edited Nov 10 at 18:22









                  Moritz

                  56.9k19131184




                  56.9k19131184










                  answered Nov 10 at 16:59









                  Darrin

                  1




                  1






























                       

                      draft saved


                      draft discarded



















































                       


                      draft saved


                      draft discarded














                      StackExchange.ready(
                      function () {
                      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f16767624%2fip-address-is-shown-in-address-bar-instead-of-domain%23new-answer', 'question_page');
                      }
                      );

                      Post as a guest















                      Required, but never shown





















































                      Required, but never shown














                      Required, but never shown












                      Required, but never shown







                      Required, but never shown

































                      Required, but never shown














                      Required, but never shown












                      Required, but never shown







                      Required, but never shown







                      Popular posts from this blog

                      Florida Star v. B. J. F.

                      Danny Elfman

                      Lugert, Oklahoma