My company use a domain registrar who also offer a web forwarding service.

We have a large number of different domain names purchased over the years and are using this web forwarding service to allow us to forward on requests to old domain names to a suitable location on our main website, as follows:

The web forwarding server has been set up to serve an http 302 redirect from www.an-old-domain.com to www.our-corporate-website.com/some-page

The user is redirected to www.our-corporate-website.com/some-page which in turn resolves via DNS to the IP of our web server

We're having a few problems with the reliability of this redirection service and I was wondering whether it would be OK to create a DNS A record for www.an-old-domain.com to resolve to www.our-corporate-website.com/some-page, which in turn resolves to the IP address of our web server.

I've always thought that DNS A records should resolve to an IP address rather than a URL, thereby creating a chain of DNS entries. A colleague tells me they that this approach is fine however, but I'm suspicious that it's a bit of a hack.

1 Answer
1

If you are not using the old domains you should be using a 301 permanent redirect not a 302 temporary (The requested resource resides temporarily under a different URI), you're losing link juice using 302's.

One solution is to setup a shared hosting account on hostmonster or another unlimited hosting provider. Have all your old domains use an .htaccess file to do the 301 to the specific path on your new domain.