Is aliasing better than URL forwarding?

[Head Boy]

What do you think?

Aliasing is the association of an alternative domain name to an existing hosted domain (they're what cpanel incorrectly calls "parked domains")

URL forwarding is sending traffic for one domain to a specific URL. It usually requires the use of a 3rd part service.

[Geeman]

hmm.. I don´t get it 100%
aliasing uses the hosting service
and url forwarding uses the domain registrar service?

so there are no differences with the results right?
both ending up on your prefered domain.

I use url forwarding on some domains because I am not dependent on the hosting though I´m not sure if this is the best way.

[Head Boy]

URL forwarding may not catch 404s, and I believe there are some differences in the way SE's handle things. URL forwarding can handle 3rd level names when you hosting can't . The differences are things like that.

[AbsolutePorn]

So... but what you said, Aliasing is much better right?

[slaxxx]

depending on who the registrar is, you can setup URL forwarding to catch 404's...i have done that at enom resellers and at moniker.

with NATS sponsors the uniques are tracked correctly and i see them using the right campaigns...but with some other sponsors it just shows up as NULL and doesn't count as a unique for that campaign.

btw...i use url forwarding and not frame forwarding.

[AbsolutePorn]

Ohhh I see... thanks for the explanation slaxxx

[Head Boy]

You have to work with your host to pick the 404s though, so if you are forwarding straight to a sponsor you may lose out.

Frame forwarding is sometimes known as cloaked forwarding btw.

[slaxxx]

Originally Posted by Head Boy

You have to work with your host to pick the 404s though, so if you are forwarding straight to a sponsor you may lose out.

no, with moniker you can have it set to catch any 404's at the DNS level using their url forwarding...no host involved...and i am forwarding straight to the sponsor.

maybe they do something different with their dns servers, but i am doing that on a bunch of my domains.

[Head Boy]

Well DNS forwarding requires the name to run through the hosting co server. I guess if they put a 404 re-route in htaccess they could do it. I can assign separate URLs for 2nd level forwards, www 3rd level forward, and wildcard forwards, but most DNS services should be able to handle that. 404s also work if I've got htaccess in the target domain directory.

[slaxxx]

Originally Posted by Head Boy

Well DNS forwarding requires the name to run through the hosting co server. I guess if they put a 404 re-route in htaccess they could do it. I can assign separate URLs for 2nd level forwards, www 3rd level forward, and wildcard forwards, but most DNS services should be able to handle that. 404s also work if I've got htaccess in the target domain directory.

For example, I own http://www.asslickingsites.com which I redirect to kissmycrack.com. I am just using Moniker's URL forwarding, and if you type in http://www.asslickingsites.com/439845839489353454.html it still works.

No hosting company is involved, although I don't know if Moniker maybe creates some sort of thing within their DNS servers that can catch 404's.

Their URL forwarding automatically catches 404's, different subdomains, etc. etc. Whereas enom and their resellers do not have it setup like that.

[Head Boy]

Well Moniker will have to have a host to run the DNS redirects, that was what I meant.

It makes sense to pick up 404s because of the old links that may be around for a dropped name. I started to do it myself, but it takes longer to activate a name that way. It's another reason for me to start doing my own programming.

[slaxxx]

Originally Posted by Head Boy

Well Moniker will have to have a host to run the DNS redirects, that was what I meant.

oh yeah hehe, i see what you're saying now. i guess they do run a host of sorts so they can do the dns redirects.