Can't access specific website

Rogatien
Contributor

I manage a small WordPress website. Earlier today I connected to the site and everything seemed fine, but then suddenly I couldn't do anything with it.

I disconnected from the site and then found I could not access it at all--not even as a visitor to the site.

The problem extends to the several computers on my WiFi network, but I have checked with the hosting provider and a couple of other people outside my network, and they see the site just fine.

I bounded the router (HH300) and that didn't help.

In fact, I can see it too, from my phone, when I turn off WiFi.

Anyone got any ideas about what may be happening and how I might proceed? 

1 48 20K
48 REPLIES 48

Vanadiel
Community All-Star
Community All-Star

What does a traceroute show?

I am a Community All-Star and customer. I'm here to help by sharing my knowledge and experience. My views on Bell and the Community Forum are my own and not the views of Bell or any of its affiliates.

eltopo
Visitor

"traceroute: unknown host"

The error message on the browser is "octopodes.biz’s DNS address could not be found."

Vanadiel
Community All-Star
Community All-Star

There's something odd with your configuration.

 

octopodes.biz resolves to 95.179.180.177. 

If you put the IP in a web browser you get a different page than when you put octopodes.biz in.

If you run a tracert to 95.179.180.177

Tracing route to 95.179.180.177.vultrusercontent.com [95.179.180.177]
over a maximum of 30 hops:

The DNS there shows up as 95.179.180.177.vultrusercontent.com

 

That is on a non-Bell connection. I would say something is wrong with your DNS record.

 

I am a Community All-Star and customer. I'm here to help by sharing my knowledge and experience. My views on Bell and the Community Forum are my own and not the views of Bell or any of its affiliates.

eltopo
Visitor

I do have several domains that go that IP address. 

Prior to just now I was only using the DNS configuration provided to me through DHCP, and it didn't work. However since the moment I added the Google public DNS to my /etc/resolv.conf file (on the client/browser side) it is working normally. So, if there's an issue, it's on the Bell side.