 | | Re: Proposal for Revised Memorial
|
|
(...) It is my understanding that that is how it works. When you type "www.lugnet.com", that request is processed by a name server, which links that name to the proper address, the 204.302.23 stuff. But all you see is lugnet.com So if memorial on (...) (26 years ago, 10-Feb-99, to lugnet.cad.dev)
|
| |
| | Re: Proposal for Revised Memorial
|
|
(...) Well, the point isd that hugin.etc thinks it's name isn't ldraw.org, but hugin.etc.. Then it returns that to the user. There are special services available with some domain-registry-services, that give you another layer in between which will (...) (26 years ago, 10-Feb-99, to lugnet.cad.dev)
|
| |
| | Re: Proposal for Revised Memorial
|
|
(...) Sorry, but hugin.risoe.dk is actually sys-323.risoe.dk (until last week it was another machine with another name). Hugin is just an alias. The HTTP daemon (aka "web server") I use can handle separate names as separate virtual servers. Play (...) (26 years ago, 10-Feb-99, to lugnet.cad.dev)
|
| |
| | Re: Proposal for Revised Memorial
|
|
(...) This isn't correct. The lugnet.com machine and the Apache software it's running can answer to anything that they're configured to answer to, without impacting performance. Currently, there is a mapping at pair.com (ISP) which associates (...) (26 years ago, 10-Feb-99, to lugnet.cad.dev)
|
| |
| | Re: Proposal for Revised Memorial
|
|
(...) Apache, or something commercial? I just hadn't thought of that. Teach me to speak on things I haven't tried to set up for myself yet :-/ Jasper (26 years ago, 10-Feb-99, to lugnet.cad.dev)
|
| |
| | Re: Proposal for Revised Memorial
|
|
[ Moving to lugnet.publish ] (...) Apache: <URL:(URL) (...) I can't remember the details, but basically you just create a catalog for the new server and add a few lines to one of the configuration files that informs Apache of the relation between (...) (26 years ago, 11-Feb-99, to lugnet.cad.dev, lugnet.publish)
|
