From a terminal Run dig +trace www.yourdomain.com Click to expand an example $ dig +trace www.example.com ; <<>> DiG 9.11.0-P5 <<>> +trace www.example.com ;; global options: +cmd . 488165 IN NS f.root-servers.net. . 488165 IN NS g.root-servers.net. . 488165 IN NS h.root-servers.net. . 488165 IN NS i.root-servers.net. . 488165 IN NS j.root-servers.net. . 488165 IN NS k.root-servers.net. . 488165 IN NS l.root-servers.net. . 488165 IN NS m. »
The section.io platform will only respond to requests using exactly the same domain name that was used to create the application on section.io. For example, if you register your application on section.io as www.example.com but then choose to create a blog.example.com CNAME record directed at the www.example.com.c.section.io. endpoint specified on your application’s DNS page in the Aperture portal, visitors to the http://blog.example.com will receive an error page displaying HTTP 409 Conflict. »
Bare Domains are DNS records without www, also called Zone Apex, Naked Domain and Root Domain. To go live on section.io you need to setup a CNAME record pointing to the section.io platform.
Within the DNS system, you cannot use a CNAME for your bare domain (e.g. domain.com) and then define additional resource records for the same zone.
This means that if you were to setup a CNAME on your bare domain you would get unpredictable results and most likely break other records that also exist at the bare domain - such as MX records required for your email to work. »
To simplify management for your websites, section.io can provide DNS hosting. This is especially useful for pointing a zone-apex record (ie bare domain) at a section.io endpoint if your current DNS hosting provider does not support the ALIAS or ANAME record types.
Hosting your DNS with section.io also provides convenient access to DNS management within the Aperture portal.
Begin hosting DNS with section.io To enable Hosted DNS with section.io: »
To continue hosting with your current provider you’ll need to go to your domain name provider and replace any existing ‘CNAME’ or A records with the ‘CNAME’ we’ve provided for you in your account. After making the DNS change (and allowing time for your DNS ttl expiry) you will start to see metrics showing in the Production environment for your site.
If your site doesn’t send the right HTTP headers or you have other things preventing the site from caching (like [client-side cookies]) then you can modify the way your reverse proxies interact with your site using section. »