Support » Networking WordPress » With Subdomain, can't access '' – Workaround?

  • Resolved Captain 777


    I have 3.0 with Multisites set up – based on the subdomain approach.
    All my sites work great (,, etc). (xxx is dummy name)
    However, I get “caught” when I try to access my email server using the standard “”. It simply goes to registration “”.

    I set up a separate mail server ( and changed the MX headers to point there…with no luck.

    I tried creating a page called “mail” and using the “Page links to” plugin redirect “” to the third party server URL (google). I get an error 404 instead.

    (However, If I click on the actual page (not just type in URL)…then it does work. My solution needs to be a simple URL for mail)

    My Question (finally)…How can I get to work?


    “newbie with dangerously little info, and willing to use it!”

Viewing 12 replies - 1 through 12 (of 12 total)
  • if you’re using Plesk, I shall quote Andrea:

    Seems to be a known issue with Plesk 9.

    and a fix even:

    If not, what are you using? cPanel?

    Basically, the wildcard subdomain record is kicking in before the actual specific subdomain records, and taking priority. Gotta move ’em around.

    ipstenu – not using Plesk 9. cPanel Thanks

    Andrea_r – “Gotta move ’em around.” definitely sounds like the right thing to prioritize the “*” down…but I’m not sure what that is exactly. Is this something I should be working via WP or via cPanel (Domain management)?


    cPanel. How did you add the * one?

    I’ve got cPanel as well, and doing that (pointing * to public_html) works fine with my named subdomains. I know this ONLY works on cPanel X and up.

    I added the wildcard * in the cPanel “create a subdomain” and it’s pointing to “public_html/”.

    I wonder if the fact that I have several sites in the “public_html/” will mess things up? The setup seems to work just fine for my, etc. Just this ‘named subdomain’ issue.

    Before we get too deep into this, check what version of cPanel you’re running.

    I was about to say it should point to JUST public_html but … Detour to explain how MY sever’s setup. It may help.

    /home/ipstenu/public_html – All my wordpress files live here.
    /home/ipstenu/public_html/svn – My NAMED subdomain SVN lives here.

    In cPanel, I have two subdomains:

    1) * (pointing to public_html)
    2) svn (pointing to public_html/svn)

    So in theory, yours should look somewhat similar to that

    – Cpanel 11
    – Let me compare with my setup:
    ALL WP files are in /home/myfolder/public_html/
    NO subfolders in (other than wp-content, etc)

    In cPanel: only 1 subdomain: * (pointing to public_html/

    I thought of putting a in cPanel as a named subdomain, but I thought this would interfere with the MX header routing to the mail server.

    Any thoughts?

    Ok..I tested something.
    If I create in cPanel and point it to public_html/, it does work. When I enter in the browser, it goes straight to the folder. (not to the registration on WP, as with others.)

    So…question now is how to ‘name’ a ‘mail’ subdomain to point to the mail server?

    I thought of putting a in cPanel as a named subdomain, but I thought this would interfere with the MX header routing to the mail server.

    That might work. Won’t know till you try, right? 😀

    Are you on a VPS or a shared host?

    in cPanel…
    1. created a named subdomain ‘’
    2. Redirected the subdomain to my mail server (…etc)
    3. Now goes straight to the mail server! MX header was updated with ‘google’ mail server details…so mail is flowing there correctly.

    Thanks for getting the creative juices to flow!

    Hi all,

    I sort of have the same problem, I think! I’ve got wordpress 3.0.1 with multisite running on shared hosting with heartinternet. Basically when someone type in the site works just fine but if you use then it gets re-directed to

    The control panel is eXtend & I dont know how to access the httpd.config

    Could someone point me in the right direction as to what to do 🙂

    Cheers in advance

    This isn’t the same problem 🙂 and you posted in another thread.

Viewing 12 replies - 1 through 12 (of 12 total)
  • The topic ‘With Subdomain, can't access '' – Workaround?’ is closed to new replies.