In DNS, propagation is based almost entirely on the serial number in the SOA record. If you don't change it, it will break. Some hosting companies let you make changes all over your domain, but then you have to click on a "publish" link of some sort to indicate that you are ready to commit those changes upon the world.
Also, by "subdomain" I assume you mean you are creating a record, not an actual subdomain. That is, you are adding an A record for testing within your domain, not a subdomain. The difference is only really important when you ask questions that DNS types like myself have to answer. A "subdomain" means NS records to delegate to another set of name servers. I am assuming you mean the misused term to mean "an A record."
For the people who can resolve the name, what do they see? The proper A record? If so, then I would think it is a propagation error; try seeing if you can bump up the serial number or add another record (foo?) and see if that also fails to propagate. If it does, well, call your DNS host.
Note that one of the three name servers serving your zone is down: ns1.compuone.com seems to not be up from where I am at least.
Technically what you're asking for is invalid. CNAME
conflicts with all other records (with a special exception for DNSSEC records), thus having CNAME xxxxx
conflicts with the SOA
, MX
, NS
etc records for the domain. My guess is that the reason the domain resolves when you use an A
there and fails when you use CNAME is because the DNS server enforces those restrictions and is unable to process your zone file.
Furthermore, based on your response to @xwincftwx's question, it's not clear that getting CNAME to work would do what you want in the first place. A CNAME
pointing to an A
record is exactly the same as an A
record in the first place. The CNAME is handled entirely internally by the DNS system and the web browser only sees the IP address. In your test with an A
record (let's say 1.2.3.4), the browser connected to 1.2.3.4
and asked it for the website example.com
. If that server isn't configured to serve a website for example.com
it typically serves a default site (in this case blogs.com
).
If you got your domain to work as a CNAME
, the browser would ask for the IP address of example.com
. DNS would see that it is a CNAME
, look up example.blogs.com
and return 1.2.3.4
. The browser would connect to 1.2.3.4
and ask it for example.com
just as it did when it was an A
record.
If you want people going to example.com
to be redirected to example.blogs.com
then you'll need to set up a basic web server that receives connections to example.com
and sends a 301 permanent redirect to the browser to tell it go to example.blogs.com
Best Answer
Your DNS seems fine,
app.dotaquiz.org
pointing to185.156.179.139
:We can see that there isn't a web page configured for that hostname on the Nginx giving error:
You should configure the Nginx
server {}
section for server nameapp.dotaquiz.org
.Also, problems with DNS configuration would have caused other kind of errors, like
ERR_NAME_NOT_RESOLVED
if the record wasn't configured at allERR_TIMED_OUT
/ERR_CONNECTION_CLOSED
in case of wrong IP without a web server404
error in case of wrong IP with a web server.The
200 OK
and404 Not Found
are HTTP Response Status Codes (RFC 7231, 6); always related to the HTTP protocol i.e. web server, not domain name service.