Ok, thanks cd34. Does this mean I'll need to contact my DNS server administrator and get www.mydomain.com to explicitly resolve to my IP address? If so, it seems like I'll need to do the same thing with abc.mydomain.com and def.mydomain.com. Is that true?
I was under the impression that once mydomain.com resolved to my IP I would be able to make up subdomains willy-nilly and redirect them as I pleased all through my server. With my commercial hosting plan (WebFaction) this was possible; but I guess that's because WF allowed me to edit the host records of the DNS server. Is that correct? Anyways, I'll contact my DNS admin and get that straightened out. On Oct 22, 9:43 am, cd34 <[email protected]> wrote: > Host not found usually means that you have a DNS issue, so,www.mydomain.com > is not being resolved to anything. > > Your apache config looks fine, getting the hostname to resolve to the > IP should fix your problem. -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en.
