DigitalOcean Kubernetes: new control plane is faster and free, enable HA for 99.95% uptime SLA

Question

How to enable .dev domain name?

I have already configured a domain name to map to digital ocean droplet. The IP url is working fine. But when i navigate to kitika.dev i get a timeout. Is it because dev only allow https? It is not working over http

Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Want to learn more? Join the DigitalOcean Community!

Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.

Sign up now

Matt Cowley • June 18, 2019

Posting a top-level final answer to this:

Using a service such as mxtoolbox, you can verify that the DNS had propagated correctly, so that is not the issue: https://mxtoolbox.com/SuperTool.aspx?action=a%3Akitika.dev&run=toolpage

Using curl, you can fetch the contents of the page correctly, which indicates the content is being served.

However, as stated on Google’s page for the .dev domain, every .dev domain is on the HSTS preload list, which makes HTTPS required on all connections when the website is accessed on a modern browser that follows this list (Chrome, Firefox etc.)

The issue here was that the website was not configured to serve content on HTTPS correctly, which was resulting in a request for the webpage timing-out in most browsers.

Hopefully, this can help others in the future!

Codinkelvin • June 18, 2019

When I check on https://dnschecker.org. It seems to have been resolved. But it is still not working. Its been more than 8 hours.

baraboom • June 18, 2019

Hi,

If you recently made changes to the domain it is possible that DNS caches have not expired. For instance, if I curl your domain I receive this response:

curl kitika.dev
<!DOCTYPE html>
<html>
<head>
<title>Welcome to nginx!</title>
<style>
    body {
        width: 35em;
        margin: 0 auto;
        font-family: Tahoma, Verdana, Arial, sans-serif;
    }
</style>
</head>
<body>
<h1>Welcome to nginx!</h1>
<p>If you see this page, the nginx web server is successfully installed and
working. Further configuration is required.</p>

<p>For online documentation and support please refer to
<a href="http://nginx.org/">nginx.org</a>.<br/>
Commercial support is available at
<a href="http://nginx.com/">nginx.com</a>.</p>

<p><em>Thank you for using nginx.</em></p>
</body>
</html>

The old DNS was not cached for my ISP so I am able to resolve the domain and am connecting to your droplet (presumably).

Sometimes DNS caches and propagation can take up to 48H although its usually no more than 4-8 hours these days.

Hope this helps and good luck - reach back out if the problem has not cleared up soon.

Try DigitalOcean for free

Click below to sign up and get $100 of credit to try our products over 60 days!

Sign up