Here's a pretty newb/101 question I have here. I'm very new to web hosting and domain forwarding. I just opened up my first web hosting site, and I'm trying to figure out a problem I'm having with the domain forwarding. I hope I can explain this right.
Let's say my website is called Website, and the domain I bought is website.com, which redirects to webhost.com/IP 18.104.22.168. When the user types in www.website.com, I obviously want the address bar to stay as "www.website.com" instead of "webhost.com" or "22.214.171.124/~myusername" or whatever. When the user navigates to buymycrap.html, the address bar should say "www.website.com/buymycrap.html." However, I'm getting one of the following two things, depending on what settings I use at my domain registrar:
The address bar will always say "www.website.com," but if the user navigates to a page and hits refresh, they'll be bumped back to the index page. I want them to remain on whatever page they're at. I also get problems with external links where the user won't be able to navigate externally unless I add the target="_blank" attribute to my anchors.
The user will be able to navigate to different pages on my site and refresh back to those pages, and external links will work fine, but the true address (i.e. www.webhost.com) will show up on the address bar.
Through research, I know this has to do with domain gripping, but no matter what I'm setting, I can't get my desired result. Does anybody have any tips on what's going on here? Thanks!
On the domain registrant's side (namespro.ca), I have this:
- domain name: inagalaxyfarfarawry.com
- name servers: slns1.namespro.ca (126.96.36.199) and slns2.namespro.ca (188.8.131.52)
- type: Domain forwarding
- forward to: http://ns2.sslcatacombnetworking.com/~inagalax
The web hosting side (siteflip.com) doesn't really provide any information other than the whois stuff, which is above.
When I contacted namespro.ca about web gripping, they responded with:
We hope you understand that is simply a smart browser trick. There is limitation on what the gripping function can do. What you describe relates to how the web server settings are at "http://ns2.sslcatacombnetworking.com/~inagalax/". It is also not what a domain gripping function is designed to do. The only way would be to have the host at "sslcatacombnetworking.com" take on your domain as a http header, but we are not sure their admin would agree to that.