Wildcard DNS?

MrLeN · #1 (**permalink**) 06-19-2005, 12:30 PM

I recently got this reply from my hosting provider:

Quote:

When we have setup a wildcard dns for you the respected entries were made in the httpd.conf file, so that *.domain.com resolves to domain.com. What happens when you add subdomain now, Then entry for subdomain is added below the wildcard entry.

As per Apache rules the first accurance is given preferance and hence *.domain.com gets qualified and the main site is shown though the subdomain is added from cpanel . Fix for the problem is , you just have to email us at support so that we can move the wildcard entry below the subdomain entry.

I have installed a redirection service at http://www.triorbit.com/myred - How on earth is this script supposed to work if the sudomain has to be set up manually?

What I want is Wildcard DNS on my domains, but if I create a new subdomain (or if myred (the script)) creates a new subdomain, then I need it to work.

My host is telling me I have to contact support every time I create a new subdomain. Currently if I create a subdomain in cPanel or WHM, the main TLD loads in the browser.

That can't be right.

What's going on here? Can anyone show me the light?

MrLeN

**brian.mark** · #2 (**permalink**) 06-19-2005, 01:07 PM

If you're going to create them in cpanel, then why did you need the wildcard? Maybe I'm not following the logic here.

Brian.

MrLeN · #3 (**permalink**) 06-19-2005, 01:12 PM

Oh I don't know. Just because I felt like it. Let's just throw up "Redirection service" for example. That'll do for a reason. Maybe it was because of that. Sorry, I must have forgot to mention it.

MrLeN

**brian.mark** · #4 (**permalink**) 06-19-2005, 01:21 PM

If you're setting them up manually in cpanel, then why would you want wildcard? Just have them get rid of the wildcard entry in httpd.conf and it would be fine. You wanted wildcard DNS, not wildcard domains.

The wildcard DNS works fine. Wildcard in the httpd.conf is what's causing problems. I understood the redirection service... which is why I don't understand why you would ever want a wildcard in the httpd.conf, unless you are looking to create a ton of duplicate content from misspelled links. That's just plain goofy.

This is something your ISP will most likely have to fix. Doesn't sound like they understood your first request, so good luck with getting it fixed. That's why we host our own sites where I'm from. I always understand what I'm asking myself for.

:-)

Brian.

MrLeN · #5 (**permalink**) 06-19-2005, 01:29 PM

lol :)

Yeah, well I don't understand how it works.

All I know is that myred needs Wildcard DNS because it has an index.php which compares subdomain.triorbit.com with users in a database. If the user exists, then subdomain.triorbit.com needs to load with the users frame. For this to work, Wildcard DNS needs to be in effect.

However, when users sign up and go to theiraccount.triorbit.com - www.triorbit.com loads, and not theiraccount.triorbit.com

So what do I ask of them? One guy actually had what I want working (as I explained in the request to my provider), but my other domains weren't working the same. So I emailed them again and they set up all the Wildcard DNS's for all my domains again. I said that has already been done, but what I want is for subdomains to work when they are created my myself or the myred script.

By this point the domain that was working right was no longer working. It's all getting annoying.

It MUST me configurable, because the dude who wrote the redirection script wouldn't have wrote it in such a way if it wouldn't work.

The instructions in the script say that I need Wildcard DNS. More than that I don't know.

MrLeN