• I was all excited when I found out about networks only to find out they got rid of the old way and require the whole wildcard domain.

    When I asked my host about them they said:
    Thank you for contacting us. The httpd.conf file is a file that is only accessible with root or sudo privileges (access that customer’s don’t have). We don’t give customer’s access to that file and also wildcard sub domains are not supported through us. The only way to get wildcard DNS to work is by using a 3rd party DNS provider that does support wildcard DNS.

    Suggestions on 3rd party DNS providers? Is there any other way around this?

Viewing 2 replies - 1 through 2 (of 2 total)
  • Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    🏳️‍🌈 Advisor and Activist

    If you can manually create subdomains and point them to your public_html folder (or www, or whatever it is on your server), then you might be able to do that.

    I know you can park domains and have that work, I wonder if you can park subdomains…

    Why not choose subfolders instead?

    FWIW, the “old” mu did this the same way.

    Or put the site on a host that supports it.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Host does not allow wildcard domains’ is closed to new replies.