Root Domain Pointer Question

Discussion in 'Hosting Services / Control Panel' started by mbwilliamsoncom, Sep 22, 2005.

Thread Status:
Threads that have been inactive for 5 years or longer are closed to further replies. Please start a new thread.
  1. I currently own a domain through DiscountASP and am interested in the Root Domain Pointer feature. If I add this feature to my current domain (www.abc.com) and have my new domain pointer (www.xyz.com), will www.xyz.com remain in the address bar in the browser? Or will it change to www.abc.com? Thanks.

    Matt
     
  2. Bruce

    Bruce DiscountASP.NET Staff

    the domain pointer will remain at the address bar.

    Bruce

    DiscountASP.NET
    www.DiscountASP.NET
     
  3. Hi Bruce,


    Unfortunately, not in our case, though we're not really sure if we followed the correct procedure.


    After reading numerousposts related to this, we felt quite confident that we could mask our DASP-hosted domain in the browser address bar if the user typed in the domain pointer URL. So, we decided to purchase the Root Domain Pointer add-on to point our country-specific domain "ourDomain.com.co"to our DASP-hosted domain - ourDomain.com and did the following:


    (1) We added 2 A records (i.e., www.ourDomain.com.co & ourDomain.com.co) to our domain registrar's DNS and enteredour DASP-assigned I.P. address to the value field;
    (2) We set up & configured DNN 4.0.3 onto our \portal subdirectory;
    (3) We modified our root index.aspx to redirect to \portal.


    With step #1, we figured that adding the two A record entries(above) to our domain registrar's DNS would have the same effect as changing our nameservers to that ofDASP's. We didn't want to give up our extra privileges being offered by our registrar.


    Result(s):
    It worked the first time. But subsequent attempts never produced the desired result. Yes, both www.ourDomain.com.co & ourDomain.com.coURLsresolved to ourDASP-hosted domain everytime. Fine, but the address bar still shows ourDomain.com/portal after typing-in any of the two (domain pointer) URLs; definitely not what we want and most definitely not the same as what the predicted end-resultswould be, as discussed here. [​IMG]


    Are we missing something here?


    -Mark
     
  4. Bruce

    Bruce DiscountASP.NET Staff

  5. Bruce

    Bruce DiscountASP.NET Staff

  6. Just a quick follow thru...


    Got the domain masking to work in DNN by adding a number of portal aliases to our main DNN site portal settings.


    We're having fun!!! [​IMG]

    Post Edited (neo_ph) : 5/27/2006 1:09:17 AM GMT
     
  7. I am having the same problem and some


    I have 2 domains


    One DASP account


    A sub directory with a DNN install wwwroot/grdnn


    The main site will be transferred to rootand has classic asp


    The Main portal Is in wwwroot/grdnn


    I have a redirect in wwwroot/index.aspx


    andmy second domain wwwroot/grdnn/test/ has a meta tag as follows


    %@ Page language="VB" %>
    <%@ Import Namespace="DotNetNuke" %>


    <meta http-equiv="refresh" content="0;url=www.test.net">


    <script runat="server">


    Sub Page_Load(ByVal sender As Object, ByVal e As EventArgs)



    the redirect actually gets the domain name opening a page as required


    but it unfortunately opens the default DNN portal and shows the standard url (it is the temp one I'm using at the moment as the main site isnt going to be active until this is sorted out)


    unfortunately the sub dir grdnn is shown too


    I believe that this can be sorted by setting the iis to have a virtual directory pointing at the root ( see nina meirs video on dnn sub portals at www.xd.com.au) but dont know


    I really need to get this resolved as I have 3 other sub portals to create quite urgently





    Regards Dave


    Thanks in advance
     
Thread Status:
Threads that have been inactive for 5 years or longer are closed to further replies. Please start a new thread.

Share This Page