Map any blog on a WordPress MU website to an external domain.
WordPress MU Domain Mapping Simplified Chinese Language
| Author: | wsnsnsns (profile at wordpress.org) |
| WordPress version required: | 2.8.6 |
| WordPress version tested: | 2.9.2 |
| Plugin version: | 0.5.1 |
| Added to WordPress repository: | 24-02-2010 |
| Last updated: | 24-02-2010
Warning! This plugin has not been updated in over 2 years. It may no longer be maintained or supported and may have compatibility issues when used with more recent versions of WordPress.
|
| Rating, %: | 0 |
| Rated by: | 0 |
| Plugin URI: | http://tuibian.com/?p=1292 |
| Total downloads: | 1 763 |
 Click to start download |
|
WordPress MU Domain Mapping Simplified Chinese Language.
Translate from Plugin WordPress MU Domain Mapping.
URL:http://wordpress.org/extend/plugins/wordpress-mu-domain-mapping/
This plugin allows users of a WordPress MU site to map their blog to another domain.
Site administrators must configure the plugin in Site Admin->Domain Mapping. You must enter the IP or IP addresses (comma deliminated) of your server on this page. The addresses are purely for documentation purposes so the user knows what they are (so users can set up their DNS correctly). They do nothing special in the plugin, they're only printed for the user to see.
Your users should go to Tools->Domain Mapping where they can add or delete domains. One domain must be set as the primary domain for the blog. When mapping a domain, (like 'example.com') your users must create an A record in their DNS pointing at that IP address. They should use multiple A records if your server uses more than one IP address. If your user is mapping a hostname of a domain (sometimes called a "subdomain") like http://www.example.com or blog.example.com it's sufficient to create a CNAME record pointing at their blog url (NOT IP address).
The login page will almost always redirect back to the original blog's domain for login to ensure the user is logged in on the original site as well as the domain mapped one.
Site admins can now choose to either allow users to setup DNS ANAME records by supplying an IP (or list of IP addresses) or set a CNAME but not both (entering a CNAME for the end user voids the use of IP's)
There is a lot of debate on the handling of DNS using CNAME and ANAME so both methods are available depending on your preference and setup.
Things to remember:
- CNAME records that point to other CNAME records should be avoided (RFC 1034 section 5.2.2) so only tell your end users to use your chosen domain name as their CNAME DNS entry if your domain name is an ANAME to an IP address (or addresses)
- Only use the CNAME method if your main domain is an ANAME of an IP address. This is very important. How do you know? Check your dns or ask your hosting company.
- Giving your user the option to just use your chosen domain name and not an IP (or list of IP's) to set as their CNAME will make administration of your WordPressMU blog platform easier, an example of this would be purchacing/deploying a new server or indeed adding more servers to use in a round robin scenario. Your end users have no need to worry about IP address changes.
- Finally, telling your end users to use an ANAME IP or CNAME domain name is up to you and how your systems are deployed.
- Further Reading: http://www.faqs.org/rfcs/rfc2219.html