On Fri, Feb 23, 2018 at 3:29 PM, TG Servers <srvrs@xxxxxxxxxxxx> wrote:Am 23. Februar 2018 10:19:29 nachm. schrieb Kent West <westk@xxxxxxx>:
> On Fri, Feb 23, 2018 at 3:13 PM, TG Servers <srvrs@xxxxxxxxxxxx> wrote:
>
>> I am afraid you cannot do that then. If you have no DNS entry for
>> beta.sitename.org no browser no nothing knows how to resolve this.. it's
>> a subdomain... did not read everything but you can edit apache conf and
>> cannot edit DNS entries??
>>
>>
>>
> Well, I can on the box (/etc/hosts), but not on the network, at least not
> without buying another domain name? But changing it on the box's /etc/hosts
> file won't help when I'm browsing in from Topeka or Kalamazoo.
>
> Unless I'm still fundamentally misunderstanding what I'm supposed to be
> doing?
>If you own sitename.org already beta.sitename.org is only a subdomain. No need to buy another domain. If you want a completely different domain (change sitename.org to something completely different) you would have to of course.
In your DNS zone you just need to make an entry for beta.sitename.org which points to the ip of the server. As just written in the meantime... somebody has to take care of DNS handling
Ah, so yes, I was still fundamentally misunderstanding what I'm supposed to do.So I've gone to domains.google.com to tinker with my domain name; I've added a "Registered host", just be adding a line with the "beta." added to the front of the address, and I've added a "Custom resource record", by adding a "beta" line.But I'm still getting a "cannot find" error on the beta site.--Kent West <")))><
Westing Peacefully - http://kentwest.blogspot.com
|