Home / server / Questions / 288027
In Process
DocWiki
Asked: 2011-07-08 11:16:58 +0800 CST

Reliable DNS service with url forward ability

  • 772

I have been with cloudns.net for a few weeks now. Cloudns's UI is very good. Very convenient for newbies. And it has a url redirection ability: you can do a redirect: example.com to www.example.com.

However, cloudns is VERY unstable. Its name servers are always offline with no reason. And it is always upgrading its systems. My site lost a lot of traffic due to its so-called "maintenance".

I am looking for a RELIABLE DNS service with URL Forwarding ability. I want to do a 301 redirect: example.com -----> www.example.com.

UPDATE:

I am using Google App Engine not VPS, so Apache is not an option for me. Note that Google App Engine no longer supports naked domains.

I am with www.zoneedit.com for the time being. It has the web redirection ability I need.

domain-name-system service 301-redirect

2 Answers

  1. Snarky Answer:
    DNS does not do URL forwarding. DNS has no knowledge of this "301 Redirect" of which you speak, and has no interest in your H-T-T-P verbosity over on port 80, nor these you-are-ell thingies - it only knows name, address, and maybe a few other important conversational words like "food", "bathroom" and "penicillin" .

    Non-Snarky Answer:
    You can't do what you want with DNS, and DNS probably isn't your problem (if your domain still resolves your DNS is fine - If your site isn't responding it's probably the web server. If your domain is actually falling off the internet you need to RUN, not walk, to another DNS provider. It's REALLY hard to screw up so badly that DNS entries stop resolving - that usually involves long outages...).

    Your best option is to invest in a good, reliable DNS provider (most domain registrars will host DNS for you), then invest in a good, reliable web site hosting service (registrars usually have wholly-owned hosting provider subsidiaries), and configure any 301 redirects you require on the web server.

    • 10

  2. voretaq7 has the solution. I would move the DNS configuration back to your domain registrar. You should be able to do this with their web interface. You should not need their premium service, although they will likely offer it to you if they can.

    EDIT: For google apps you will need to setup a CNAME for www.example.com pointing to the appropriate google apps domain. This is the only data you can configure for www.example.com. Many domain registrars offer redirection of the sites. Configure redirection for the bare domain according to their documentation.

    If you can't redirect with your registrar, consider not setting up an A record for your bare domain (example.com). Browsers may add a www. prefix to the the domain when they can't get an address for the bare domain. This should do the required redirection. You will only need an A record if you have a server listening on example.com. For a mail server you need an MX record pointing to the mail server (mail.example.com), but not an A record for example.com.

    A last ditch solution would be to find someone willing to run a redirect server for you. (Traffic should be minimal.) Create an A record using their IP address. Instructions for redirecting a virtual host on Apache are at the end of the following solution. DynDNS.com has a webhop service that may do what you want for a fee.

    INCORRECT: The following solution is for for hosts supporting bare domains which does not include google apps. which uses CNAMES for the user's domain(s).

    Configure example.com and www.example.com with the IP address of your web server. While you are at it you may want to configure SPF records to discourage spammers from using your domain in spam messages. www.example.com should likely have an SPF record like v=spf1 -all. If you do send email from example.com an SPF record like v=spf1 mx ~all or vspf1 mx -all should be appropriate.

    If you weren't using Configure your web server to redirect requests to example.com to www.example.com. In Apache you can use the following two lines in you virtualhost configuration:

    RewriteCond %{HTTP_HOST}   !^www\.example\.com [NC]
RewriteRule ^/(.*)         http://www.example.com/$1 [L,R=301]

    You could let them browse www.example.com as example.com. Alternatively, you can use the base tag in your page headers to redirect subsequent queries to www.example.com.

    <base href="http://www.example.com/" />
    • 0