Paul Thomas Posted February 4 Report Posted February 4 Multiple reports on Facebook from users who are unable to reach MooneySpace; one is getting an error that the domain is for sale.
hammdo Posted February 4 Report Posted February 4 I got that on my phone (mobile) but Wi-Fi is ok here… -Don
A64Pilot Posted February 4 Report Posted February 4 I get it when I clink on the saved link, but don’t when I type it in
Schllc Posted February 5 Report Posted February 5 This happened to my company site one time. It was an expired credit card. I had paid for the domain in a five year increment and the card had expired. You have some time to reclaim the domain so it isn’t urgent but it does cut off just like that.
Ragsf15e Posted October 29 Report Posted October 29 @mooniac58 I’m having no luck getting onto MS on my home isp (Centurylink). Is it possible you are blocking them or are they blocking me from my MS? They don’t seem to block anything else. multiple devices tried, and my phone works if I use cell isp. Thanks, Drew
mooniac58 Posted October 29 Report Posted October 29 3 hours ago, Ragsf15e said: @mooniac58 I’m having no luck getting onto MS on my home isp (Centurylink). Is it possible you are blocking them or are they blocking me from my MS? They don’t seem to block anything else. multiple devices tried, and my phone works if I use cell isp. Thanks, Drew That is odd. We are not blocking anything like that. Are you good at using a command prompt if you have a Windows system? If so you could run a tracert command to see where you are being blocked along the way...
PeteMc Posted October 29 Report Posted October 29 23 minutes ago, mooniac58 said: If so you could run a tracert command to see where you are being blocked along the way... I'm able to get to the site, but ran a tracert anyway. 1 1 ms <1 ms <1 ms 192.168.4.1 2 9 ms 10 ms 9 ms 100.93.164.66 3 12 ms 9 ms 12 ms po-313-321-rur201.spokane.wa.seattle.comcast.net [24.153.87.49] 4 10 ms 11 ms 12 ms po-2-rur202.spokane.wa.seattle.comcast.net [69.139.160.202] 5 10 ms 12 ms 10 ms po-200-xar02.spokane.wa.seattle.comcast.net [24.124.128.209] 6 26 ms 22 ms 20 ms ae-37-ar01.seattle.wa.seattle.comcast.net [68.86.96.5] 7 24 ms 20 ms 21 ms be-501-arsc1.seattle.wa.seattle.comcast.net [24.124.128.121] 8 * * * Request timed out. 9 22 ms 20 ms 20 ms be-2112-pe12.seattle.wa.ibone.comcast.net [96.110.34.130] 10 * * * Request timed out. 11 41 ms 37 ms 38 ms be2075.ccr21.sfo01.atlas.cogentco.com [154.54.0.233] 12 41 ms 38 ms 39 ms be3096.ccr81.sjc13.atlas.cogentco.com [154.54.40.41] 13 46 ms 48 ms 47 ms be3097.ccr41.lax01.atlas.cogentco.com [154.54.40.158] 14 57 ms 57 ms 57 ms be2931.ccr31.phx01.atlas.cogentco.com [154.54.44.85] 15 58 ms 56 ms 56 ms be3407.rcr21.b023003-0.phx01.atlas.cogentco.com [154.54.28.142] 16 58 ms 58 ms 56 ms 38.142.106.98 17 59 ms 57 ms 59 ms e1-1.AZ1-C1-2.503.1.1.0-18.a2webhosting.com [69.48.137.17] 18 * * * Request timed out. 19 64 ms 58 ms 63 ms server.mooneyspace.com [190.92.188.98]
mooniac58 Posted October 29 Report Posted October 29 I got there in a similar time: 1 6 ms 4 ms 5 ms 192.168.4.1 2 15 ms 23 ms 12 ms 100.92.207.66 3 16 ms 16 ms 15 ms po-304-321-rur01.santafe.nm.albuq.comcast.net [96.216.21.177] 4 16 ms 16 ms 14 ms po-100-xar01.santafe.nm.albuq.comcast.net [162.151.13.129] 5 16 ms 17 ms 16 ms be-3-arsc1.albuquerque.nm.albuq.comcast.net [96.108.43.109] 6 26 ms 25 ms * be-36831-cs03.champa.co.ibone.comcast.net [96.110.44.25] 7 30 ms 31 ms * be-3311-pe11.910fifteenth.co.ibone.comcast.net [96.110.33.122] 8 * * * Request timed out. 9 25 ms 27 ms 25 ms den-bb2-link.ip.twelve99.net [62.115.137.152] 10 48 ms 49 ms 47 ms kanc-bb2-link.ip.twelve99.net [62.115.137.115] 11 44 ms 47 ms 43 ms 62.115.139.189 12 64 ms 71 ms 64 ms phx-b6-link.ip.twelve99.net [62.115.125.55] 13 66 ms 66 ms 69 ms phx-b9-link.ip.twelve99.net [62.115.137.121] 14 64 ms 65 ms 63 ms a2hosting-ic-369258.ip.twelve99-cust.net [213.248.73.249] 15 66 ms 68 ms 65 ms e1-2.AZ1-C1-2.503.1.1.0-18.a2webhosting.com [190.92.146.5] 16 * * * Request timed out. 17 68 ms 68 ms 64 ms server.mooneyspace.com [190.92.188.98]
mooniac58 Posted October 29 Report Posted October 29 Also worth noting that it could just be a DNS issue and whichever DNS service you are using (most likely the one from your ISP) is for whatever reason not resolving our domain to the proper IP address. Another command prompt test or this would be: nslookup mooneyspace.com (it should return 190.92.188.98) If it does not work one solution would be to update your DNS settings in your network configuration to instead of getting it automatically from your ISP to instead use Google's open DNS servers which are 8.8.8.8 and 8.8.4.4 - I have done this on a few occasions to fix DNS issues.
Ragsf15e Posted October 29 Report Posted October 29 37 minutes ago, mooniac58 said: Also worth noting that it could just be a DNS issue and whichever DNS service you are using (most likely the one from your ISP) is for whatever reason not resolving our domain to the proper IP address. Another command prompt test or this would be: nslookup mooneyspace.com (it should return 190.92.188.98) If it does not work one solution would be to update your DNS settings in your network configuration to instead of getting it automatically from your ISP to instead use Google's open DNS servers which are 8.8.8.8 and 8.8.4.4 - I have done this on a few occasions to fix DNS issues. Excellent, thanks. I think I have the Google dns set up but I’ll check. I’ll also run a tracer and see what happens. Thanks for your input!
Ragsf15e Posted October 30 Report Posted October 30 1 hour ago, mooniac58 said: Also worth noting that it could just be a DNS issue and whichever DNS service you are using (most likely the one from your ISP) is for whatever reason not resolving our domain to the proper IP address. Another command prompt test or this would be: nslookup mooneyspace.com (it should return 190.92.188.98) If it does not work one solution would be to update your DNS settings in your network configuration to instead of getting it automatically from your ISP to instead use Google's open DNS servers which are 8.8.8.8 and 8.8.4.4 - I have done this on a few occasions to fix DNS issues. Thanks again. Appears my DNS wasn't set to the google one. Centurylink/qwest/lumen was blocking MS for some reason or not resolving the IP correctly. The google DNS seems to have fixed my issue. Drew
PeteMc Posted October 30 Report Posted October 30 3 minutes ago, Ragsf15e said: The google DNS seems to have fixed my issue. If you were having DNS issues, in the Cmd/Terminal window you might also use the ipconfig /flushdns command to clean out any incorrect addresses that have been pulled down from your ISP. 1
toto Posted October 30 Report Posted October 30 1 hour ago, mooniac58 said: If it does not work one solution would be to update your DNS settings in your network configuration to instead of getting it automatically from your ISP to instead use Google's open DNS servers which are 8.8.8.8 and 8.8.4.4 - I have done this on a few occasions to fix DNS issues. Cloudflare has very nice servers as well: 1.1.1.1 and 1.0.0.1 ISP name servers are often terrible 1
vorlon1 Posted Wednesday at 02:45 PM Report Posted Wednesday at 02:45 PM I have been unable to access this site from my Android devices (phones and tablets with multiple browsers) for about a week now. It seems to be a DNS issue: It is weird that it works from my desktop (windows) Though Tracert works, a ping reports "server not found" Anyone else reporting this?
MikeOH Posted Wednesday at 05:04 PM Report Posted Wednesday at 05:04 PM Can you assign the DNS server manually?
vorlon1 Posted Wednesday at 05:21 PM Report Posted Wednesday at 05:21 PM Not in the Android browser/apps. 1
vorlon1 Posted Wednesday at 05:23 PM Report Posted Wednesday at 05:23 PM Note that this same error is occurs in Chrome, Firefox, and the Samsung browsers on the platform.
Ragsf15e Posted Thursday at 01:18 AM Report Posted Thursday at 01:18 AM 7 hours ago, vorlon1 said: Note that this same error is occurs in Chrome, Firefox, and the Samsung browsers on the platform. A bunch of us have been having dns issues with it for maybe two weeks. Where possible, changing dns has fixed it though.
Thedude Posted Thursday at 06:44 AM Report Posted Thursday at 06:44 AM Changing DNS to what? Adding a manual override? I've been in Montreal for the last week and have been seeing the site unreachable occasionally from my phone and some when I was in California earlier this month.
MikeOH Posted Thursday at 07:21 PM Report Posted Thursday at 07:21 PM 12 hours ago, Thedude said: Changing DNS to what? Adding a manual override? I've been in Montreal for the last week and have been seeing the site unreachable occasionally from my phone and some when I was in California earlier this month. Yes, manual override to, for example, Cloudflare at 1.1.1.1 Google AI is your friend, just ask it how do I change my DNS server on my <whatever> (e.g. iPad, Windows, etc.)
vorlon1 Posted Thursday at 07:34 PM Report Posted Thursday at 07:34 PM 13 minutes ago, MikeOH said: Yes, manual override to, for example, Cloudflare at 1.1.1.1 Google AI is your friend, just ask it how do I change my DNS server on my <whatever> (e.g. iPad, Windows, etc.) Changing the DNS in the app is not possible. I haven't --and can't--changed anything... I downloaded an app that produced the following: The last is from my phone.
MikeOH Posted Thursday at 07:36 PM Report Posted Thursday at 07:36 PM Yeah, that's the kind of error I was getting. You don't change the DNS in any app. It's a setting in your operating system. What hardware/OS are you using?
vorlon1 Posted Thursday at 07:48 PM Report Posted Thursday at 07:48 PM Phone is Samsung Galaxy S20FE w/Andriod 13, One UI version 5.1 From 31OCT2025 Tablet is Samsung Galaxy S10FE w/ Android 16, One UI version 8.0 from 16OCT2025 Both are the latest security and latest OS's applied. (BTW same error in Duck Duck Go browser)
MikeOH Posted Thursday at 10:05 PM Report Posted Thursday at 10:05 PM 2 hours ago, vorlon1 said: Phone is Samsung Galaxy S20FE w/Andriod 13, One UI version 5.1 From 31OCT2025 Tablet is Samsung Galaxy S10FE w/ Android 16, One UI version 8.0 from 16OCT2025 Both are the latest security and latest OS's applied. (BTW same error in Duck Duck Go browser) What @N201MKTurbo posted...this is NOT a browser problem. 1
Recommended Posts