# DNS Issue Ubuntu Server

**URL:** <https://meta.discourse.org/t/dns-issue-ubuntu-server/184756>\
**Category:** Product Support\
**Created:** [March 29, 2021, 2:39pm UTC](https://meta.discourse.org/t/dns-issue-ubuntu-server/184756 "2021-03-29T14:39:04Z")\
**Posts on this page:** 1\
**Showing post:** 12

<div class="post-metadata">

**Author:** ![lucasbasquerotto](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/lucasbasquerotto/32/133376_2.png) [@lucasbasquerotto](https://meta.discourse.org/u/lucasbasquerotto)\
**Post date:** [March 30, 2021, 12:12pm UTC](https://meta.discourse.org/t/dns-issue-ubuntu-server/184756/12 "2021-03-30T12:12:41Z")

</div>

First, see if your DNS register is defined coorectly, so that the domain correctly points to your server’s ip. Run:

```shell
$ host <your_domain>
<your_domain> has address <your_ip>

```

Then see if the message `<your_domain> has address <your_ip>` shows and `<your_ip>` is correct.

If the DNS record correctly points to your server’s ip, then see if there’s some firewall blocking traffic. for example, if your server is a Digital Ocean droplet, in the Digital Ocean site, go to Network → Firewalls, then see if there’s a firewall that allows traffic to ports 80 and 443 to your droplet. If you are using AWS, see if there’s a security group associated to your instance that allows inbound traffic to those ports. If you use a different cloud provider, see if you need to create a cloud firewall rule somewhere.

Also see if your server itself allows traffic to these ports (should allow by default, unless you blocked it with some iptable rule or ufw). This probably isn’t the case, unless you actually used iptables or ufw.

---

_[View the full topic](https://meta.discourse.org/t/dns-issue-ubuntu-server/184756)._