Error access to Subdomains

[christnicolas]

Hi guys, I really need your help.
So, the problem is I cannot access Subdomains. I have installed it successfully but when accessing subdomains, it failed. Subdomain included sentora.[domain].dev., on DNS: sentora, record A, TLL 1H.

Could anyone help me? Thanks in advance!

[sparkrack]

You can not access the subdomain of your server, or you can't access subdomains hosted from your Sentora installation?

Can you either post your domain name, or send it to me in a PM so I can check the DNS routing?

[spoonman]

Hi guys, I really need your help.
So, the problem is I cannot access Subdomains. I have installed it successfully but when accessing subdomains, it failed. Subdomain included sentora.[domain].dev., on DNS: sentora, record A, TLL 1H.

Could anyone help me? Thanks in advance!

sub-domains are a CNAME record not A records.
Please supply a screenshot of the DNS Manager for the domain on the Sentora hosting panel.

What is a CNAME Record?
A CNAME, or Canonical Name record, is a record that points to another domain address rather than an IP address.
For example, say you have several subdomains, like www.mydomain.com, ftp.mydomain.com, mail.mydomain.com etc and you want these sub domains to point to your main domain name mydomain.com.

Instead of creating A records for each sub-domain and binding it to the IP address of your domain you can create CNAME records.

As you can see in the table below, in the case where the IP address of your server changes, you only need to update one A record and all the subdomains follow automatically because all the CNAMES point to the main domain with the A record:

(sub)Domain / Hostname | TTL | Record Type| Target / Destination
mydomain.com                  3600         A              111.222.333.444
www                                   3600     CNAME                   @
ftp                                       3600     CNAME                    @
mail                                    3600     CNAME                   @
test                                     3600     CNAME                   @


After you add the CNAME Wait on daemon update or run it manually and restart apache.

Code:

php -q /etc/sentora/panel/bin/daemon.php

Ubuntu

Code:

service apache2 restart

CentOS

Code:

service httpd restart

NOTE ! DNS propagation can take up to can take up to 72 hours to propagate worldwide

[bradjtrammell]

That's not at all accurate. Sub domain or sub-hosts can be an A record, or a CNAME, there is no required standard for it. As long as it points to the correct place it will work fine.

A CNAME can be used if the record shares the IP address of the main server by using the @ symbol, but again, there is no requirement to use either or.

[spoonman]

That's not at all accurate. Sub domain or sub-hosts can be an A record, or a CNAME, there is no required standard for it. As long as it points to the correct place it will work fine.

A CNAME can be used if the record shares the IP address of the main server by using the @ symbol, but again, there is no requirement to use either or.

Unfortunately i work for a domain registrar and web-hosting company.
What you are saying is a common mistake with DNS mapping.
The DNS A record is specified by RFC 1035.
Restrictions
    A CNAME record must always point to another domain name and never directly to an IP address.
    A CNAME record cannot co-exist with another record for the same name. It’s not possible to have both a CNAME and TXT record for www.example.com.
    A CNAME can point to another CNAME, although this configuration is generally not recommended for performance reasons. When applicable, the CNAME should point as closely as possible to the target name in order to avoid unnecessary performance overheads.

The structure of an A record follows the standard top-level format definition defined RFC 1035.

CNAME records can be used to alias one name to another. CNAME stands for Canonical Name.

A common example is when you have both example.com and www.example.com pointing to the same application and hosted by the same server. To avoid maintaining two different records, it’s common to create:

    An A record for example.com pointing to the server IP address
    A CNAME record for www.example.com pointing to example.com

As a result, example.com points to the server IP address, and www.example.com points to the same address via example.com. If the IP address changes, you only need to update it in one place: just edit the A record for example.com, and www.example.com automatically inherits the changes.

Now to put a SUB-domain in Sentora hosting panel properly is to use a CNAME.