• Hi,

    Can’t seem to learn the answer to this. It was asked by someone else but there was no complete answer.

    I want to do a multisite setup using subdomains but my host, 1&1, does not allow wildcard DNS on a shared plan.

    Is there a workaround to do this by “manually creating” them in the DNS without wildcard DNS? I was thinking that I could manually “point” (via CNAME or something?) each subdomain to the main domain…is possible?

    Thanks!

Viewing 15 replies - 16 through 30 (of 47 total)
  • Everything works, and that is what is confusing me. I have not added anything to Apache..

    that was my point, if it’s working, then your host added it when they created your account.

    Look in the /etc/conf/httpd/ folder for the http.conf file. If it Apache2 they use included and that file tells you where they are.

    Find the vhost entry for your main domain. There will be a line that says

    ServerAlias yourdomain.com *.yourdomain.com.

    That’s the wildcard record.

    Hopefully the memory usage doesn’t increase so much that DreamHost will kill me for not being on a VPS. Does anyone know if MS is as memory-intensive as WPMU?

    It’s almost exaclty the same code. the “memory intensive” part were some plugins or people having hundreds of blogs on a shared server.

    that was my point, if it’s working, then your host added it when they created your account.

    sorry I thought I made it clear, I have my own server and I setup apache php and mysql when I installed the control panel.

    I guess that line must be added automatically by the control panel. Thank you for finally telling what it is though, now I can go and check…

    thanks

    just checked and it’s not there… now I’m confused ??

    I have

    ServerAlias www.mydomain.com mydomain.com

    Like I said it is working.. Perhaps because the domain has its own IP? Should I add the wildcard anyway??

    Edit: without the https:// above. the forum seems to add that

    It’s almost exaclty the same code. the “memory intensive” part were some plugins or people having hundreds of blogs on a shared server.

    I see. Well, I’m just using it for static content so it shouldn’t be that bad, right? Thanks for the information! My nerves have calmed down a bit thanks to you :]

    Should I add the wildcard anyway??

    there might be a wildcard further up letting it through. Might as well add it anyway, it won’t break it. ??

    Thanks Andrea I will give it a try

    Hi

    I created the subdomains, but got internal 500 error. So didn’t work. Any ideas…..hertfordshire.educationrecycle.net is one of the subdomains….do I need to configure permissions?

    Thanks!

    sounds like a .htaccess problem. Double check you have got that file right.

    Looks okay, unless rewrite not enabled….how can I check? thanks!

    There is nothing under the /etc/ dir. Not a bean…..so no http.conf file. Could be the problem. Damn FVS…..

    Contact your host, is Apache not running then?

    Sorted now as my hosting people made the changes to http.conf. Curiously nothing under /etc/ and they haven’t answered where it’s kept….

    Using WP3 on new install.
    I have similar issue. BlueHost doesn’t support wildcard DNS. I created Subdomain in cpanel easily enough and it is live, but I can’t get it to show in SuperAdmin panel in WP3. If I can’t manage from WP what is the point? I looked in DNS zone editor and this line was created:

    https://www.baltimore.goessolar.org. A 69.89.31.155

    So why does WP3 not allow me to see it?

    I went thru set up of WPMU activation but did not realize wildcard DNS issue. Modified .htaccess and wp-config.php as instructed.
    Does all the subdomains need to be created before you activate WP MU features? If so that is a no go and I’ll have to find a different host.
    I don’t need users to create sites on fly, so manually creating subdomains as needed is not a problem.

    When I click create new site in SuperAdmin only option is subdirectory. I set Domains not subdirectory option when set up MU.

    So if there is a way to get this working at BlueHost sure would like step by step advice. Maybe I have to delete everything and start over. Instuctions warn that can’t change afterwards. There is not access to that screen anymore.

    Thanks in advance.

    I looked in DNS zone editor and this line was created:

    https://www.baltimore.goessolar.org. A 69.89.31.155

    So why does WP3 not allow me to see it?

    Probably because the www is stuffed in front of it?

    Edit: actually it;s not working becasue requests to the IP show no website configured at that address. There’s your problem.

    Instuctions warn that can’t change afterwards. There is not access to that screen anymore.

    You can’t change it successfully if you have working sub-blogs. If you messed up the install, you CAN change it.

    see the line in wp-config where it says subdomains true? Change it to false. bam, subfolder blogs.

    Just thought I’d chime in here. This thread was quite useful to me, as I’m a Dreamhost customer on shared hosting. I can confirm that Andrea’s instructions about the subdomain worked like a charm, but I thought I’d flesh out the details of what I did.

    While DH has a custom hosting panel, I’d imagine that cpanel on other hosts should work fine. If you are looking to run WordPress 3.0 multi-site with subdomains on a DH shared hosting account, follow these instructions (at least they worked for me):

    1. Make sure your primary domain is setup first on your host and that you have WP installed.
    2. Set up your network for multi-site and subdomains and ensure you edit wp-config and .htaccess as per the info WP 3.0 provides for you during setup.
    3. If you get the WP error message about wildcard subdomains, ignore it and continue.
    4. As Andrea said, before you set up any sites on your network, get the directory location for your primary domain as you will need to point all of your subdomains to this location on your host.
    5. Ensure you set up a subdomain on your host for any you plan on setting up through WP, and point it to your main domain directory.
    6. Allow enough time for the subdomain to propagate and then test that it resolves to your main domain first.
    7. Once your subdomain resolves successfully, set up your site with the same subdomain in WP. It should now work fine.

    The only extra hassle is that you have to set up the subdomain first on your host and then set up the same site from within WP, but it’s better than having to move to VPS and pay a lot for it if you’re only looking to have a few sites managed through WP 3.0.

Viewing 15 replies - 16 through 30 (of 47 total)
  • The topic ‘3.0 multisite as subdomains without wildcard DNS?’ is closed to new replies.