1

This is our scenario:

  • Our DNS is hosted by a company. They don't manage the DNS.
  • We use Zoneedit (www.zoneedit.com) to manage the DNS such as nameservers, CNAMEs, etc...
  • Then we have our web host where we just have our files hosted.

We have a subdomain created on zoneedit. We would like to do a URL rewrite so that subdomain.ourdomain.com is displayed as www.ourdomain.com/subdomain.

Do I use Zoneedit to do the URL rewrite or the web host or the DNS host?

I checked the Zoneedit docs but I could not find a way to do a URL rewrite. Need some advice.

Thanks

3

DNS only handles domain resolution to IP addresses (and back). It doesn't even know about HTTP.

URL rewriting can only be done on the web server.

2

URL rewriting is not possible with a DNS (even ZoneEdit).

The closest results you could achieve with them is using the WebForwards feature to forward any call to subdomain.ourdomain.com to www.ourdomain.com/subdomain (or to any other URL).

If you target a true URL rewriting then it must be configured at your web server level. Check the wikipedia page for the most common URL Rewriting web framework.

  • I think Web Forwards is a totally different feature... I think I'll have to call my web host to let them do the rewrite for me... – chilly-child May 3 '10 at 21:45
  • I use web forward to automatically forward a URL subdomain.ourdomain.com to a totally different URL www.anotherdomain.com/specificpage. Works fine. – Veynom May 4 '10 at 8:26
  • Are subdomain.ourdomain.com and www.anotherdomain.com/specificpage pointing to the same content? I just wanted subdomain.ourdomain.com to be rewritten (renamed) as www.anotherdomain.com/specificpage in the browser url. I think that's what URL rewrite does, whereas web forward simply takes you to a different location. Correct me if I am wrong. – chilly-child May 6 '10 at 8:00
0

Url rewrite should be done on the webserver...

0

These Answers are wrong...

From the horses mouth (zoneEdit)...

Q: My ISP blocked port 80. How can I run a web server?

A: Don't worry, you can still run one!

Sign up and get started with ZoneEdit. Make your web server listen on port number like "6000" or "5000" Check to see if your web server works in a browser by using a URL: http://3.4.5.6:6000/. Use the port number that you're listening on and the real IP address of your machine. Add the "IP Address" for your web server in ZoneEdit: "ww2.domainname.com" points to "ip address". Add a Web Forward entry for your domain called "www.domainname.com" that points to http://ww2.domainname:6000/ We recommend turning cloaking off in this case, letting people know thay are going to http://ww2.domainname.com:6000 is usually OK, and it allows the browser to perform better.

The example they gave simple redirects the port.. But it can be used to rewrite and aspect of the URL.. Even to cloak it! Amazing for a free service level... Frankly I have no idea how / why they do it, lol.

0

So you're wanting a rewrite rather than a redirect, correct? This means the user will see the original URL and not the destination URL in their browser address bar.

Many DNS providers (including ZoneEdit) offer URL forwarding features these days - these can work as a simple 301/302 HTTP redirect (most commonly) or there is sometimes the option to enable "URL cloaking" which usually works by loading the destination page inside an HTML frame, keeping the original address in the address bar.

I doubt that ZoneEdit will be able to enable the forwarding/cloaking for only a subfolder, however - it's usually done for the entire domain.

The best solution would be to create your own HTML frame file on the main domain's web server that then loads the subdomain into itself.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy