Website Issue

[vorlon1]

52 minutes ago, MikeOH said:

What @N201MKTurbo posted...this is NOT a browser problem.

Yes, this was added for another "data point" indicating same. Agreed.

But where/what is the source of the problem? I think it's in the DNS entry for mooneyspace.com. That could mean though other OS'es are handling the 'error' in other ways.

Here is the command output from my desktop that CAN access mooneyspace:

C:\Users\LAdmin>tracert mooneyspace.com
Unable to resolve target system name mooneyspace.com.

C:\Users\LAdmin>ping google.com

Pinging google.com [142.250.31.113] with 32 bytes of data:
Reply from 142.250.31.113: bytes=32 time=44ms TTL=102
Reply from 142.250.31.113: bytes=32 time=51ms TTL=102
Reply from 142.250.31.113: bytes=32 time=49ms TTL=102
Reply from 142.250.31.113: bytes=32 time=58ms TTL=102

Ping statistics for 142.250.31.113:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 44ms, Maximum = 58ms, Average = 50ms

C:\Users\LAdmin>ping mooneyspace.com
Ping request could not find host mooneyspace.com. Please check the name and try again.

 

[MikeOH]

10 minutes ago, vorlon1 said:

Yes, this was added for another "data point" indicating same. Agreed.

Not sure what you mean by 'another data point'??

10 minutes ago, vorlon1 said:

But where/what is the source of the problem? I think it's in the DNS entry for mooneyspace.com

A DNS 'looks up' human readable websites and 'finds' their IP address in order to allow routing to the site's server.  There are many DNS servers.  If the one your system is set to use does NOT have an entry for mooneyspace.com, then it can't 'resolve' the name into an IP address and you get the 'not found' error.  You need to 'tell' (manually set) your system to use a specific DNS server that has a valid entry for mooneyspace.com.  I suggested Cloudfire (1.1.1.1), but there are others (e.g. Google, 8.8.8.8)

[Thedude]

Anyone investigating why this is happening? I'm just using the default Verizon DNS settings on my phone, but I haven't heard of them having any broader issues. If changing DNS servers gets around the issue, that's great, but it would be good to understand what's actually wrong.

[hammdo]

When Frontier did that mess on me, i went into my home router and changed the DNS servers myself to Googles and set Frontiers as second. Frontier was controlling the whitelist and I didn’t want that. You can lookup lists of DNS servers and if tech savvy, modify your home router DNS source…

Google 

google DNS servers

also

-Don

[eman1200]

Holy sht, back on mooneyspace after like 2 weeks which in social media time is a lifetime.

[Flyler]

2 hours ago, eman1200 said:

Holy sht, back on mooneyspace after like 2 weeks which in social media time is a lifetime.

Dude we are all flying pipers now, where have you been

[DCarlton]

As another data point, I can get in reliably using Norton Private Browser on an Apple desktop but can no longer get in reliably using Safari (which I've used for years).  Been like this a few weeks.  Continuing today.  

[Ragsf15e]

3 hours ago, DCarlton said:

As another data point, I can get in reliably using Norton Private Browser on an Apple desktop but can no longer get in reliably using Safari (which I've used for years).  Been like this a few weeks.  Continuing today.  

Is this on your home network safari?  If you change the dns on your router, safari should work.  It’s not a problem with safari, it’s a dns issue.  Using a vpn will generally use a different dns.

[DCarlton]

12 hours ago, Ragsf15e said:

Is this on your home network safari?  If you change the dns on your router, safari should work.  It’s not a problem with safari, it’s a dns issue.  Using a vpn will generally use a different dns.

Yes at home.  It's only happening with the Mooneyspace web site.  No issues finding any other web site. 

MS ERROR.pdf

[Ragsf15e]

36 minutes ago, DCarlton said:

Yes at home.  It's only happening with the Mooneyspace web site.  No issues finding any other web site. 

MS ERROR.pdf 27.01 kB · 0 downloads

Yep, that’s what happened to me as well. Nobody has really figured out why, but there is a fix.  If you can login to your internet modem, you should be able to find DNS Server.  Set that to 1.1.1.1 (for cloudflare) or 8.8.8.8 (google). Either one works fine.

[DCarlton]

7 minutes ago, Ragsf15e said:

Yep, that’s what happened to me as well. Nobody has really figured out why, but there is a fix.  If you can login to your internet modem, you should be able to find DNS Server.  Set that to 1.1.1.1 (for cloudflare) or 8.8.8.8 (google). Either one works fine.

Appreciate the help but it's not a good time for me to create a self-inflicted wider IT issue at home.  One tweak often leads to hours of grief.  I'm in now on both browsers.  Will see if anyone else reports more issues.  

[vorlon1]

For Firefox app:

Select three "dots" in upper right corner of browser to open drop down and select settings/DNS over HTTPS. Select MAX protection, and use drop down to select NextDNS. Savel changes. Restart (just to be sure) This has worked for me.

 

 

[mooniac58]

Just an update for everyone - it looks like after a few days of working with my hosting company they FINALLY a) admitted this was a problem with their top level DNS servers and b) they managed to fix the issues.  I am not sure what exactly was wrong but it was something with the SOA (start of authority) DNS records for the domain and something that is outside of my control.

So users that were not able to access the site with certain ISPs (Verizon and CenturyLink are ones I am aware of) should now be able to find our site again.  This also fixed the email delivery issues we were having with Yahoo (and their subsidiaries like AOL and SBCGlobal) and Apple as far as I can tell looking at logs over the past 12 hours the emails seem to be going through now.

If you do have any issues I would appreciate you letting me know by shooting me a message here at @mooniac58

Thank you for your patience!

Craig

[NickG]

Thanks! It works again!