# "This webpage is not available ERR\_NAME\_NOT\_RESOLVED"

**URL:** https://meta.discourse.org/t/this-webpage-is-not-available-err-name-not-resolved/35136
**Category:** Self-hosting
**Created:** [2015年十月31日 14:45 UTC](https://meta.discourse.org/t/this-webpage-is-not-available-err-name-not-resolved/35136 "2015-10-31T14:45:20Z")
**Posts on this page:** 8
**Page:** 1

<div class="post-metadata">

### Author: ![Chris\_Steiger](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/chris_steiger/32/116695_2.png) [@Chris\_Steiger](https://meta.discourse.org/u/Chris_Steiger)
#### Post date: [2015年十月31日 14:45 UTC](https://meta.discourse.org/t/this-webpage-is-not-available-err-name-not-resolved/35136/1 "2015-10-31T14:45:20Z")

</div>

I’m having a lot of my users complain about being unable to access our forums, seeing the message “This webpage is not available ERR\_NAME\_NOT\_RESOLVED”.

It seems to be somehow specific to Chrome, and I know DNS flushing will work for them, but the issue will still pop up for them off and on.

One of the users thinks it has to do with post autosaves saying “For some strange reasons, when the post auto saves it has a high chance of making you get that dns error when you leave that post for later.”

We also have a thread going on here discussing it: [Forum down on chrome - Support - Dungeon Quest Forums](http://forums.dungeon-quest.com/t/forum-down-on-chrome/3287)

Any idea if there’s something I can do to help solve this issue on my end?

---

<div class="post-metadata">

### Author: ![mpalmer](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mpalmer/32/45740_2.png) [@mpalmer](https://meta.discourse.org/u/mpalmer)
#### Post date: [2015年十月31日 20:20 UTC](https://meta.discourse.org/t/this-webpage-is-not-available-err-name-not-resolved/35136/2 "2015-10-31T20:20:57Z")

</div>

The problem lies somewhere between the user and your DNS provider. The forum software itself has no control over whether or not DNS works correctly.

From a quick look, your DNS service looks _mostly_ OK, with the possible exception that the authoritative DNS servers for your domain are reporting that `ns1.linode.com` is authoritative for your domain, when it isn’t. That _shouldn’t_ be causing the problem you’re seeing, but cleaning that up is a good idea regardless.

---

<div class="post-metadata">

### Author: ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [2015年十月31日 22:09 UTC](https://meta.discourse.org/t/this-webpage-is-not-available-err-name-not-resolved/35136/3 "2015-10-31T22:09:08Z")

</div>

Isn’t there a “check my DNS for issues” website we can send people to?

For basic global propagation you can check  
[https://www.whatsmydns.net/#A/dungeon-quest.com](https://www.whatsmydns.net/#A/dungeon-quest.com)

For configuration issues you can check

> **[Pingdom Tools](https://dnscheck.pingdom.com/?domain=dungeon-quest.com)**
>
> Full Page Test Analysis

I agree, the multiple conflicting records there are a problem as @mpalmer noted.

---

<div class="post-metadata">

### Author: ![mpalmer](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mpalmer/32/45740_2.png) [@mpalmer](https://meta.discourse.org/u/mpalmer)
#### Post date: [2015年十月31日 22:16 UTC](https://meta.discourse.org/t/this-webpage-is-not-available-err-name-not-resolved/35136/4 "2015-10-31T22:16:52Z")

</div>

> [@codinghorror](#):
>
> Isn’t there a “check my DNS for issues” website we can send people to?

Well, personally, I use [Squishywishywoo: complete dns traversal checking](http://www.squish.net/dnscheck/v1.html) as my “go-to” tool for checking DNS problems, but it doesn’t catch _everything_ (the extra `NS` record in this case I found with a manual `dig`), and it’s somewhat, uh, “technically focused” (to say the least). I also use [http://dnssec-debugger.verisignlabs.com/](http://dnssec-debugger.verisignlabs.com/) if I suspect DNSSEC troubles. I don’t know of any one site you can drop a name into and have it check everything I’ve seen go wrong with DNS.

---

<div class="post-metadata">

### Author: ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [2015年十月31日 22:19 UTC](https://meta.discourse.org/t/this-webpage-is-not-available-err-name-not-resolved/35136/5 "2015-10-31T22:19:30Z")

</div>

Well the site I linked does catch the thing you brought up and it looks like a valid check.

---

<div class="post-metadata">

### Author: ![Chris\_Steiger](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/chris_steiger/32/116695_2.png) [@Chris\_Steiger](https://meta.discourse.org/u/Chris_Steiger)
#### Post date: [2015年十一月1日 02:43 UTC](https://meta.discourse.org/t/this-webpage-is-not-available-err-name-not-resolved/35136/6 "2015-11-01T02:43:49Z")

</div>

That makes sense, I’ll give solving those DNS issues a try. Thanks for the help! 😄

---

<div class="post-metadata">

### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system)
#### Post date: [2019年一月23日 17:54 UTC](https://meta.discourse.org/t/this-webpage-is-not-available-err-name-not-resolved/35136/8 "2019-01-23T17:54:18Z")

</div>



---

<div class="post-metadata">

### Author: ![zogstrip](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/zogstrip/32/512781_2.png) [@zogstrip](https://meta.discourse.org/u/zogstrip)
#### Post date: [2019年一月23日 17:56 UTC](https://meta.discourse.org/t/this-webpage-is-not-available-err-name-not-resolved/35136/9 "2019-01-23T17:56:04Z")

</div>


