Title: IPv6 Support
Last modified: August 20, 2016

---

# IPv6 Support

 *  Resolved [silson](https://wordpress.org/support/users/silson/)
 * (@silson)
 * [13 years, 2 months ago](https://wordpress.org/support/topic/ipv6-support-1/)
 * I everybody,
 * I just installed a WPMU + Domain Mapping setup and everything is working as expected
   with IPv4. 😀
 * So if I enter one of my Domains I get the expected blog page. But this only works
   in a IPv4 enviroment. If I do the same on a IPv6 (or dual stack with prefered
   IPv6) enviroment I end up in some kind of redirect loop. At least this is why
   my apache says.
 * More exactly:
    * My “setup” domain is “blogs.heinrichsen.net” with a subfolder
   config.
 * The following IPv4 only mapping works:
    * [http://reisen.heinrichsen.net](http://reisen.heinrichsen.net)-
   > [http://blogs.heinrichsen.net/urlaubsblog](http://blogs.heinrichsen.net/urlaubsblog)
 * The following IPv6 mapping works partly:
    * [http://www.duschblog.de](http://www.duschblog.de)-
   > [http://blogs.heinrichsen.net/duschblog](http://blogs.heinrichsen.net/duschblog)
 * In a IPv4 enviroment this is fine. In a IPv6 enviroment it does not work. I guess
   this is because the IPv6 address of the server is not known to the mapping plugin.
   Unfortunately the plugin refuses to accept a IPv6 Address in the field “Server
   IP Address”.
 * So my question: Have I setup something wrong? Or is there simply no IPv6 support?
   Are there any plans to add it?
 * Best regards,
    Stefan
 * [http://wordpress.org/extend/plugins/wordpress-mu-domain-mapping/](http://wordpress.org/extend/plugins/wordpress-mu-domain-mapping/)

Viewing 3 replies - 1 through 3 (of 3 total)

 *  Plugin Author [Ron Rennick](https://wordpress.org/support/users/wpmuguru/)
 * (@wpmuguru)
 * [13 years, 2 months ago](https://wordpress.org/support/topic/ipv6-support-1/#post-3623489)
 * That’s something in your web server config or DNS. WP processes the requests 
   it receives from the webserver and is not really aware of the IP configuration
   involved.
 * I haven’t done much with IPv6 but it might be something related to the fact that
   your main install is configured as an IPv4 while the mapped domain is configured
   as an IPv6.
 *  Thread Starter [silson](https://wordpress.org/support/users/silson/)
 * (@silson)
 * [13 years, 2 months ago](https://wordpress.org/support/topic/ipv6-support-1/#post-3623712)
 * Hi Ron,
 * you’re right… after checking everything once more I noticed some wrong virtual
   host configurations in my apache setup. After correcting them and cleaning the
   browser cache everything works now. 😀
 * So even if you didn’t really do something you still helped me. Therefore: Thank
   you! 🙂
 *  Plugin Author [Ron Rennick](https://wordpress.org/support/users/wpmuguru/)
 * (@wpmuguru)
 * [13 years, 2 months ago](https://wordpress.org/support/topic/ipv6-support-1/#post-3623728)
 * you’re welcome 🙂

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘IPv6 Support’ is closed to new replies.

 * ![](https://s.w.org/plugins/geopattern-icon/wordpress-mu-domain-mapping.svg)
 * [WordPress MU Domain Mapping](https://wordpress.org/plugins/wordpress-mu-domain-mapping/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/wordpress-mu-domain-mapping/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/wordpress-mu-domain-mapping/)
 * [Active Topics](https://wordpress.org/support/plugin/wordpress-mu-domain-mapping/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/wordpress-mu-domain-mapping/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/wordpress-mu-domain-mapping/reviews/)

## Tags

 * [domain mapping](https://wordpress.org/support/topic-tag/domain-mapping/)
 * [ipv6](https://wordpress.org/support/topic-tag/ipv6/)
 * [wpmu](https://wordpress.org/support/topic-tag/wpmu/)

 * 3 replies
 * 2 participants
 * Last reply from: [Ron Rennick](https://wordpress.org/support/users/wpmuguru/)
 * Last activity: [13 years, 2 months ago](https://wordpress.org/support/topic/ipv6-support-1/#post-3623728)
 * Status: resolved