DNS for GoDaddy, Weebly, and WinHost

Discussion in 'DNS/Domain names' started by Jay Shaw, Jun 5, 2020.

  1. Hello,

    Any help is appreciated!

    My domain name, www.BinghamtonYoga.com is registered with GoDaddy, so I use their DNS servers.

    My website is at Weebly. So I created an A Records at GoDaddy that points to my Weebly IP address of 199.34.228.68. That DNS on this is working fine.

    Here's where I need WinHost help:
    I also have a WinHost account that I'd like to use for a subdomain. What I mean is that when someone navigates to http://subdomain.binghamtonyoga.com, it will take me to my WinHost directory, which WinHost says lives at http://bingham2.w30.wh-2.com/. (WinHost also says my IP address is 64.209.142.214, but that doesn't display my default webpage.)

    What DNS records do I need to create to make this redirect happen?

    THANK YOU!
     
    Last edited: Jun 5, 2020
  2. SOLVED: GoDaddy has a Domain and/or Subdomain Forwarding feature that allowed me to do this.

    In GoDaddy...
    1. Scroll down to Additional Settings and select Manage DNS.
    2. Scroll down to the Forwarding section.
    3. Click Add next to Domain or Subdomain to set up forwarding. ...
    4. In the blank field under Forward to, enter the destination URL you want to redirect your domain or subdomain to.
     
  3. Elshadriel

    Elshadriel Winhost Staff

    That's one way to do it. The better way is to create a sub-domain DNS "A" record that points to 64.209.142.214. You can't access your site by IP because it's a shared IP.
     
  4. So, when I use the IP address, http://64.209.142.214, I get this error message:

    Web Page is Unavailable

    We are very sorry.

    The web page you are trying to reach is unavailable.

    Please contact the Website Administrator.

    We apologize for the inconvenience. ​

    And when I use the Secondary URL, http://bingham2.w30.wh-2.com, I get a IIS 502.5 Error:

    HTTP Error 502.5 - Process Failure
    Common causes of this issue:
    • The application process failed to start
    • The application process started but then stopped
    • The application process started but failed to listen on the configured port

    Neither one produces the simple Blazor template website that I expect.
    It seems like when I use the IP address I'm not accessing the right default webpage. And when I use the Secondary URL, the server isn't generating the page.

    What can I do to use either approach to display the Blazor template website?

    Thanks!
     
  5. Elshadriel

    Elshadriel Winhost Staff

    I enabled ASP.NET Core error logging for you, and this is the error I see:

    "Unhandled exception. System.FormatException: Could not parse the JSON file."

    And you can't access your site using IP address because it's a shared IP address. IIS uses host headers for additional name resolution.
     
  6. My mistake! Thank you.
     

Share This Page