I stand corrected.
I checked the zone files and tonybibbs.com had the
following entry:
*.tonybibbs.com IN CNAME tonybibbs.com
I didn't have a similar line for iowaoutdoors.org. I
added:
*.iowaoutdoors.org IN CNAME iowaoutdoors.org
Now I have to wait forever and a day to get it to work
;-)
Is there a way I can query my primary name server for
the zone file entry? I'm using a free DNS Service and
it doesn't give you the raw zone entry.
Now I need to figure out my ssl problem. Thanks,
--TB
--- Adrian Stovall <[EMAIL PROTECTED]> wrote:
> Perhaps I wasn't very clear, here's the deal. If
> you are getting
> "unknown host" when you attempt to go to the secure
> site, it's likely
> because DNS couldn't match the URL to an IP address.
> If your browser
> doesn't know where to go, it doesn't matter whether
> your virtual host is set
> up correctly or not.
> The quick tests are either "nslookup
> secure.mydomain.com" or "dig
> @my.dns_server.com secure.mydomain.com". If you get
> "unknown host" replies
> to those, you need to fix DNS. I tried both of
> these (assuming
> "secure.iowaoutdorrs.com" to be the URL in question)
> and got what I expected
> based on your problem description. nslookup reports
> "Non-existent
> host/domain", and dig says the same. You need to
> add an entry for the URL
> of your secure site in your nameserver
> (NS9.WORLDNIC.COM, according to dig)
> before you can surf to it.
>
> -----Original Message-----
> From: Tony Bibbs [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, August 24, 2000 11:52 AM
> To: [EMAIL PROTECTED]
> Subject: RE: Question about name-based virtual
> hosting of ssl sites
>
>
> you shouldn't need one.
>
> To be more specific:
>
> I have iowaoutdoors.org and tonybibbs.com registered
> to my box.
>
> with tonybibbs.com I did nothing special with the
> DNS
> Zone entry.
>
> I then from within httpd.conf created two virtual
> hosts:
> mp3.tonybibbs.com and downloads.tonybibbs.com
>
> Those worked (not working now...I took them out
> temporarily)
>
> Theoretically I should be able to do the same with
> iowaoutdoors.org but creating a
> secure.iowaoutdoors.org virtual host doesn't work.
>
> Assuming that is an easy fix then I still have the
> problem of why SSL isn't quite working.
>
> Does that clear things up?
>
>
> --- Adrian Stovall <[EMAIL PROTECTED]> wrote:
> > What does your "mydomain.com" zone file look like?
>
> > Do you have an A record
> > for secure.mydomain.com (or at least a cname
> entry)
> >
> > -----Original Message-----
> > From: Tony Bibbs [mailto:[EMAIL PROTECTED]]
> > Sent: Thursday, August 24, 2000 11:07 AM
> > To: [EMAIL PROTECTED]
> > Subject: Re: Question about name-based virtual
> > hosting of ssl sites
> >
> >
> > Ok figured out some of my problem. The two files
> > that
> > were included added the directives to get SSL
> > working
> > but they needed to be tweaked to fit my situation.
>
> > I
> > am now includeing mod_ssl.conf and ignoring the
> > vhost.conf file. I have also verified the Listen
> > Directives are defined for both port 80 and 443.
> >
> > I now have it where I can hit my regular website
> > using
> > http but I can't hit the other virtual host using
> > https. What bothers me is this...my https vhost
> is
> > as
> > follows:
> >
> > <VirtualHost XXX.XXX.XXX.XXX:443>
> > ServerName secure.mydomain.com
> > </VirtualHost>
> >
> > When I ping secure.mydomain.com it says "Unknown
> > Host"
> > but when I ping www.mydomain.com it works fine.
> > This
> > is wierd because it seems part of the problem is
> at
> > the DNS level (which can't be right). I feel I am
> > REALLY close...what am I missing?
> >
> > Wierder yet. I have another domain registered to
> my
> > IP, www.mydomain2.com
> >
> > If i create virtualhosts off of it (e.g.
> > test.mydomain2.com) it works fine.
> >
> > Any ideas?
> >
> > --Tony
> >
> >
> >
> >
> >
> >
> >
> > --- Owen Boyle <[EMAIL PROTECTED]> wrote:
> > > Hi Tony,
> > >
> > > Do you have a Listen directive? I kind of
> assumed
> > > you would have that
> > > already (probably should've mentioned it...).
> You
> > > don't really need it
> > > for port 80 since that is the default for HTTP
> and
> > > Apache obviously
> > > knows about it but you definately need it for
> port
> > > 443! (and any other
> > > ports you use).
> > >
> > > You must put;
> > >
> > > NameVirtualHost XXX.XXX.XXX.XXX:80
> > >
> > > Listen XXX.XXX.XXX.XXX:80
> > > <VirtualHost XXX.XXX.XXX.XXX:80>
> > > ServerName www.mydomain.com
> > > </VirtualHost>
> > >
> > > Listen XXX.XXX.XXX.XXX:443
> > > <VirtualHost XXX.XXX.XXX.XXX:443>
> > > ServerName secure.mydomain.com
> > > </VirtualHost>
> > >
> > > Hope that helps,
> > >
> > > Owen Boyle.
> > > --
> > > SWX Swiss Exchange, 10 Cours de Rive, 1211
> Geneve
> > 3
> > >
> >
> --------------------------+-------------------------
> > > Phone: +41 (0)22 849 5648 | Fax: +41 (0)22 849
> > 5643
> > >
> >
>
______________________________________________________________________
> > > Apache Interface to OpenSSL (mod_ssl)
>
> >
> > > www.modssl.org
> > > User Support Mailing List
> > > [EMAIL PROTECTED]
> > > Automated List Manager
>
> > [EMAIL PROTECTED]
> >
> >
> > =====
> >
> >
> > __________________________________________________
> > Do You Yahoo!?
> > Yahoo! Mail - Free email you can access from
> > anywhere!
> > http://mail.yahoo.com/
> >
>
______________________________________________________________________
> > Apache Interface to OpenSSL (mod_ssl)
>
> > www.modssl.org
> > User Support Mailing List
> > [EMAIL PROTECTED]
> > Automated List Manager
> > [EMAIL PROTECTED]
> >
>
______________________________________________________________________
>
=== message truncated ===
=====
__________________________________________________
Do You Yahoo!?
Yahoo! Mail - Free email you can access from anywhere!
http://mail.yahoo.com/
______________________________________________________________________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
