Deezfluffybutternutz
Allowing Ads
C:\>ping http://subclub.org
Ping request could not find host http://subclub.org. Please check the name and try agai
n.
C:\>ping https://subclub.org
Ping request could not find host https://subclub.org. Please check the name and try aga
in.
C:\>ping https://www.subclub.org
Ping request could not find host https://www.subclub.org. Please check the name and try
again.
C:\>ping www.subclub.org
Ping request could not find host www.subclub.org. Please check the name and try again.
C:\>ping subclub.org
Ping request could not find host subclub.org. Please check the name and try again.
Code:C:\>ping http://subclub.org Ping request could not find host http://subclub.org. Please check the name and try agai n. C:\>ping https://subclub.org Ping request could not find host https://subclub.org. Please check the name and try aga in. C:\>ping https://www.subclub.org Ping request could not find host https://www.subclub.org. Please check the name and try again. C:\>ping www.subclub.org Ping request could not find host www.subclub.org. Please check the name and try again. C:\>ping subclub.org Ping request could not find host subclub.org. Please check the name and try again.
Just some more info for you if it helps. I haven't tried using a VPN yet. Near San Jose, CA at the moment. AT&T is my Internet provider.
Yup. Btw, I get perfectly fine DNS resolution with ping on www.subclub.orgPing is increasingly a poor tool for this as so many hosting providers block icmp requests at the gate. The error is hostname resolution, you could try querying some common name servers (dig and nslookup are examples of tools for this)
> ping www.subclub.org
Pinging www.subclub.org [69.49.101.19] with 32 bytes of data:
Request timed out.
>ping subclub.org
Pinging subclub.org [69.49.101.19] with 32 bytes of data:
Request timed out.
You could give that a shot.I haven't tried using a VPN yet.
This is a routine task for which virtually all hosting providers will have a how-to guide set up. If you have little/no experience setting these things up, it's still a routine question for them and with a little back & forth with them, it should take less than 48 hrs to fix this. If you're capable of following a user guide, it should be fixable within an hour. This is just to let you know that it's not very complicated or a daunting task. You can do this.I'm still working with the NEW host company to figure out the problem
tracert
An error occurred during a connection to 37.16.0.118. Peer reports it experienced an internal error.
Error code: SSL_ERROR_INTERNAL_ERROR_ALERT
The page you are trying to view cannot be shown because the authenticity of the received data could not be verified.
Please contact the website owners to inform them of this problem.
ping
C:\>ping subclub.com
Pinging subclub.com [37.16.0.118] with 32 bytes of data:
Reply from 37.16.0.118: bytes=32 time=8ms TTL=54
Reply from 37.16.0.118: bytes=32 time=8ms TTL=54
Reply from 37.16.0.118: bytes=32 time=8ms TTL=54
Reply from 37.16.0.118: bytes=32 time=8ms TTL=54
Ping statistics for 37.16.0.118:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 8ms, Maximum = 8ms, Average = 8ms
We use cookies and similar technologies for the following purposes:
Do you accept cookies and these technologies?
We use cookies and similar technologies for the following purposes:
Do you accept cookies and these technologies?