Skip to Content.
Sympa Menu

discuss - Re: [opennic-discuss] Apache2 vHost config not working when .bit resolved via OpenNIC DNS

discuss AT lists.opennicproject.org

Subject: Discuss mailing list

List archive

Re: [opennic-discuss] Apache2 vHost config not working when .bit resolved via OpenNIC DNS


Chronological Thread 
  • From: subhuman <discipline AT gmx.net>
  • To: discuss AT lists.opennicproject.org
  • Subject: Re: [opennic-discuss] Apache2 vHost config not working when .bit resolved via OpenNIC DNS
  • Date: Sun, 14 Sep 2014 06:05:09 +0200

What's in the logs?

On Sat, 13 Sep 2014 23:19:55 -0400
"Christopher D. Bartels" <chris AT christopherbartels.com> wrote:

> Hi,
>
>
>
> I have a number of .bit websites & when I navigate to them via a proxy by
> adding a .pe to the end of them, they load the correct root directory, as
> per the Apache2 vHosts configuration, which listens on port 80 & delivers
> the correct root directory based on the domain name being browsed.
>
>
>
> But when I visit the page(s) through my OpenNIC DNS servers directly, I get
> a directory listing of the webserver, as if the server isn't receiving the
> domain name the visitor is browsing somehow.
>
>
>
> How can I fix this if OpenNIC interrupts the way the vHost works?
>
>
>
> I haven't tested if I can enter a port number into each .bit name's
> configuration & configure the vHosts to use separate ports for each site.
> That's a less than ideal solution because then I couldn't register my domain
> names in bulk, each with a straight IP address configured the same across
> all domains. It would take me months to reconfigure each domain with a
> separate port number- if that even worked, I dunno.
>
>
>
> Can you configure your server so that vHosts work as intended based on
> domain name?
>
>
>
> Please advise.
>
>
>
> Thanks,
> Chris Bartels
>


--
The world is such a nasty place to be.



Archive powered by MHonArc 2.6.19.

Top of Page