This is often done with a web redirect. That is, the web server at e.g. free.ly
would be setup to pass any requests it receives along to ex. freely.com
.
For DNS, the other method that might accomplish this goal is to use a CNAME record (though the freely.com
web server would still need to be configured to handle requests it received for free.ly
).
Non-DNS (Web Redirect) Method Examples
Independently set up the DNS for freely.com
and free.ly
to point to the proper web server(s).
Setup the web server(s) for freely.com
and free.ly
, respectively (i.e. so that the server recognizes it's own domain name(s)).
Configure the web server software under free.ly
to redirect to freely.com
:
3A. Apache (Virtual Host)
<VirtualHost *:80>
ServerName free.ly
Redirect / http://freely.com
</VirtualHost>
3B. Nginx (Server Block)
server {
. . .
server_name free.ly;
rewrite ^/(.*)$ http://freely.com/$1 permanent;
. . .
}
3C. HTML Meta Refresh (free.ly
Landing Page)
<!DOCTYPE html>
<html>
<head>
<title>HTML Meta Refresh Redirect</title>
<meta http-equiv = "refresh" content = "0; url = https://freely.com" />
</head>
<body>
</body>
</html>