cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Go to solution

Domain forwarding path being lost?

I have setup my domain to forward to an IP address (forwarding only, permanent) in Domain Manager on GoDaddy.

 

When I enter the domain in a browser it correctly forwards it to the IP. But if I add a path to the domain, it does not forward to the path. I've waited a few days for DNS to update.

 

So exampletest.com correctly forwards to 192.168.1.72

But exampletest.com/thislink does not forward to 192.168.1.72/thislink

 

As a test, I forwarded a domain that I purchased from another provider, and it works.

 

2 ACCEPTED SOLUTIONS


@JesseW wrote:

For the moment, I would suggest looking at other options if you need the path matching to work.  


Thanks for the honest answer. 

I found a quick workaround bouncing the domains onto a web server that lets me fiddle with the .htaccess file and rewrite rules...

View solution in original post


@tomhunt wrote:

Appreciate the suggestion of "looking at other options."

Could you explain what those options might be???


I solved the problem pointing the URL to a different website, where I have an hosting account that allows me to control the behavior of my virtual instance of the webserver using .htaccess configuration files.

 

I only applies to you if you have such alternative hosting account; the setup requires some technical knowledge, but all you need to ready is at http://www.htaccess-guide.com/

View solution in original post

58 REPLIES 58
Community Manager

Hi @ogrepie. Welcome to GoDaddy Community! Our forwarding service does not work with URL paths, unfortunately. If you want to redirect and match a path, you would need to point the domain to a hosting plan and then do a 301 or 302 redirect there. Perhaps the IP you're forwarding to can be instead set up to host your domain, so you do not need to do the forward. 

 

JesseW - GoDaddy | Community Manager | 24/7 support available at x.co/247support | Remember to choose a solution and give kudos.


@JesseW wrote:

Our forwarding service does not work with URL paths. 


Some official clarification seems required.

 

Here you say the godaddy subdomain forwarding service does not preserve paths.

However, until recently, it used to preserve paths just fine. So if mysub.mydom.com was forwarded to example.com, then automatically without any further intervention, mysub.mydom.com/somepath/somemore would forward to example.com/somepath/somemore just fine.

 

Then something went broken, now mysub.mydom.com/somepath/somemore surprisingly goes to a godaddy URL shortening page.

 

I chatted with godaddy support and the broken paths with subdomain forwarding were mentioned as "known bug" but developers did not commit to a timeline for a fix.

 

So, could you please clarify whether path preservation will be fixed as a feature of subdomain forwarding OR the feature has been intentionally withdrawn and won't be reintroduced?

 

Just need to know whether to wait for the fix or to start manually correcting a large set of links...

 

Thanks.

Yes, path forwarding previously work for me too. This is a recent issue.

Community Manager

Hi @ihcsasac@ogrepie - Yes, this did work previously. We changed the service at the end of June to increase stability and performance as well as address other internal issues. Domain forwarding now uses the same backend that our URL shortener service uses. Unfortunately, due to this, the path match no longer works for any forwarding. There aren't currently plans to add the feature back, but that could change in the future. For the moment, I would suggest looking at other options if you need the path matching to work. Sorry Man Sad

 

JesseW - GoDaddy | Community Manager | 24/7 support available at x.co/247support | Remember to choose a solution and give kudos.


@JesseW wrote:

For the moment, I would suggest looking at other options if you need the path matching to work.  


Thanks for the honest answer. 

I found a quick workaround bouncing the domains onto a web server that lets me fiddle with the .htaccess file and rewrite rules...

View solution in original post

I've been wrestling with this one too.

 

Appreciate the suggestion of "looking at other options."

Could you explain what those options might be???

 

Thanks.

Is there some way to prevent that URL Shortener page from popping up?

At this point, the redirect of an old domain (with no path) works in calling up the main page of the new domain, but any combination of path with old domain brings up the URL Shortener page (an extremely odd and unhelpful thing for visitors who may be following an old link).

 

Is there any way that oldwebsite.com/anypath.html could have its path ignored so visitors would at least find their way to newwebsite.com ?

 

Does the URL Shortener page pop up due to some sort of error handling that can be customized to call up the main newwebsite.com page?

 

Thanks.

Was there ever an answer to this??

 

Is there any way that oldwebsite.com/anypath.html could have its path ignored so visitors would at least find their way to newwebsite.com ?

 

Does the URL Shortener page pop up due to some sort of error handling that can be customized to call up the main newwebsite.com page?

 

We don't really care if the paths are mapped, but it would be really helpful if it could at least send the visitors to the homepage of the new website.  

The .htaccess changes didn't work for me, but I'm not a sysadmin and am not wise in the ways of Apache. However, I was able to find an alternative workaround.

 

I changed our old domain's forwarding from our new domain to the www subdomain of the old domain and then set the CNAME of the www subdomain to point to the new domain. The only drawback is that the links, which now work, display the old domain name instead of the new domain.

ThorLeach I ended up turning off domain forwarding in GoDaddy and just entering a DNS A record pointing to our server.  Then in the Apache config file on our server, httpd.conf, I added a ServerAlias directive so that Apache would know which website a request for this domain should go to.

 

Now the full URL is passed along.

evilsizor,

 

Thanks!

 

That sounds like a better solution than mine, unfortunately I don't have easy access to to the httpd.conf file and even if I did, I wouldn't know how to add a ServerAlias directive... That being said, if time and resources allow (or if the boss demands it), I'll be getting in touch with our server/hosting/magento guys and passing your solution along to them.

 

-Thor


@tomhunt wrote:

Appreciate the suggestion of "looking at other options."

Could you explain what those options might be???


I solved the problem pointing the URL to a different website, where I have an hosting account that allows me to control the behavior of my virtual instance of the webserver using .htaccess configuration files.

 

I only applies to you if you have such alternative hosting account; the setup requires some technical knowledge, but all you need to ready is at http://www.htaccess-guide.com/

View solution in original post

We really need this to work again. Any updates?

Yeah .. This REALLY sucks.  This can kill off thousands of backlinks that were built up over the years. 

Seconded: this worked until just a few months ago, as literally every subdomain service since Geocities has done. To just silently break all links for the sake of "stability" is absurd, and deeply disappointing.

Hi Everyone. I just wanted to update here to let you all know that our developers are working on adding this functionality back to the forwarding service. I don't have an exact timeframe I can give as to when that will be released, but it is definitely on the roadmap. Hopefully, it won't be too far in the future. If I find out more, I will definitely update here. 

 

JesseW - GoDaddy | Community Manager | 24/7 support available at x.co/247support | Remember to choose a solution and give kudos.

Hi JesseW,

 

We're migrating to a new domain and path forwarding is very important for us. We can't afford to lose our backlinks and default all traffic to the domain root.

 

Google Domains allows path forwarding (https://support.google.com/domains/answer/4522141), but I'd prefer not going through the hassle of migrating to a new registrar.

 

I know you don't have an exact timeline, but are we talking days, weeks or months? Should we look into other solutions or GoDaddy is expecting to address this issue soon?

 

Thank you very much!

Community Manager

Hi @Kingdju. Development timeframes can be tricky. I don't think it will be as soon as "days". More likely "weeks". I would be surprised if it was "months" though. Hope that helps. 

 

JesseW - GoDaddy | Community Manager | 24/7 support available at x.co/247support | Remember to choose a solution and give kudos.

We are really unhappy that this change was made with no notification.  I'm glad that is being reinstated but if it doesn't happen fairly quickly we will be moving all of our domains elsewhere.

Thanks for the rough estimate on reinstating this feature. This change was a huge blow to our operations and caused a ton of confusion and GoDaddy chat support had NO CLUE about anything you mentioned. I felt like I was going crazy..."wait, did it ever work?" I felt gas-lighted. Oddly, some of my domains work with the path forwarding, but most do not. Getting this feature reinstated is critical to our continuing to register/renew the 200+ domains we have in our account with GoDaddy. Our status as a GoDaddy customer is 100% dependent on the re-implementation of this feature.