Why is my website not showing-up on the www ?

KingL2

Hi 

A website that I own is not visible on the www

"ERR_CONNECTION_TIMED_OUT".   

Pinging the url returns "could not find host"

'downforeveryoneorjustme.com' shows it as being down

I can ping the IP of my host server.  I can see my files on the host's control panel, but not on the www

The nameservers and IP is correct on the control panel at my domain register (a different company from the host). 

I renewed the hosting and domain registrar a few weeks ago, and their accounts/payments systems all look updated & kosher on their service pages. My website was working fine "last" year (but, until now, I hadn't checked it since doing the renewals).

At my (client) end, I see the same symptoms using three different computers (Win10, Win11 and an android phone), though they are all just wifing to the same router/ISP/broadband. 

I assume that the 'downforeveryoneorjustme.com' result suggests that the problem is not at my end (home).  

I have officially reached the end of my networking knowledge - what's my next move?  thanks

DullGreyGuy

Speak to the web hosts tech support, depending on how good they are they may tell you the problem or they may just finger point saying its the domain hosts fault as a consequence of you not having all your services with them

moneysaver1978

In the DNS settings on your hosting account, do you have 2 separate entries for both www and without www? You generally need 2 separate CNAME.

KingL2

I think so, I've got
DNS ENTRY=@; TYPE=MX; PRIORITY=10; TARGET=Nameserver1
DNS ENTRY=@; TYPE=MX; PRIORITY=20; TARGET=Nameserver2
DNS ENTRY=@; TYPE=A; Target=IP Address
DNS ENTRY=www; TYPE=A; Target=IP Address

AstonSmith

Since the host and registrar are separate, let's see which half might be playing up. In one of your Windows computers, open the command prompt/terminal and use:

nslookup your_domain_here.com

If it responds with the correct IP, the registrar settings are correct. If it says "Non-existent domain" or something like that, the registrar is wrong or somehow not propagated to your DNS (very unlikely after weeks).

Is it dedicated or shared hosting? If it's dedicated, you might be able to visit it directly using the IP in a browser's address bar (you may have to prefix https).

KingL2

Hi thanks

That returns 

[quote]

server:dsldevice.lan

Address: 192.168.x.254

non-authorative answer: 

name: <myurl>

address: 192.168.xx.110

[/quote]

if put the first IP  into a browser window, it pulls up a login dialog for a 'gpon home gateway'.  I have no idea what that is, but when I google it, it smells like something to do with a router setup.  Not sure if it is mine or theirs!

I'm on fibre broadband with a bundled (fibre) router, if that makes a difference.  


The second IP in a browser times-out

.

It's shared hosting. Somewhat cheapy; in New York.  http://IP  (also https; and no_prefix) times-out in a browser.

debitcardmayhem

Type this nslookup your_domain_here.com 8.8.8.8

this will point nslookup to googles dns server

you are poining to your local dns prob your router 

onomatopoeia99

KingL2 said:

Hi thanks

That returns 

[quote]

server:dsldevice.lan

Address: 192.168.x.254

non-authorative answer: 

name: <myurl>

address: 192.168.xx.110

[/quote]

The second IP in a browser times-out

.

It's shared hosting. Somewhat cheapy; in New York.  http://IP  (also https; and no_prefix) times-out in a browser.

Firstly, any address that begins 192.168 is private and you do not need to "hide" parts of it.

Secondly, any address that begins 192.168 is private and therefore only reachable on your local network, not from the internet. 

The first part of the output tells you the DNS server that answered the query, 192.168.x.254.  This is likely to be your router, which will have requested it from an upstream server (probably your ISP's DNS server) and should have cached it.  The second part is the answer to your query

KingL2 said:

I think so, I've got
..
DNS ENTRY=@; TYPE=A; Target=IP Address
DNS ENTRY=www; TYPE=A; Target=IP Address

Is the Target in this 192.168.xx.110 like in the output from nslookup, or something else?

Are you especially concerned about people finidng out the IP address of your website (which is probably shared with hundreds of other websites)?

KingL2

debitcardmayhem said:

Type this nslookup your_domain_here.com 8.8.8.8

this will point nslookup to googles dns server

Thanks. that gives

Server:  dns.google
Address:  8.8.8.8

Non-authoritative answer:
Name:    mydomaln.co.uk
Address:  192.161.51.110  (same as the second one from last time, 8:43pm yesterday)

that IP times out in a ping and in a browser

KingL2

onomatopoeia99 said:

KingL2 said:

I think so, I've got
..
DNS ENTRY=@; TYPE=A; Target=IP Address
DNS ENTRY=www; TYPE=A; Target=IP Address

Is the Target in this 192.168.xx.110 like in the output from nslookup, or something else?

No, it is the IP provided to me by the webhost, along with the names of the nameservers. It was keyed into the domain-registrar's portal by me.  I assume that it is the IP of the server that hosts the website (or would it be the IP of the nameservers?).  It is the only IP provided to me by the webhost and has been working fine for the last 3 years.

I'd rather not give if out publicly. There is some method in my madness.

onomatopoeia99

KingL2 said:

debitcardmayhem said:

Type this nslookup your_domain_here.com 8.8.8.8

this will point nslookup to googles dns server

Thanks. that gives

Server:  dns.google
Address:  8.8.8.8

Non-authoritative answer:
Name:    mydomaln.co.uk
Address:  192.161.51.110  (same as the second one from last time, 8:43pm yesterday)

that IP times out in a ping and in a browser

At 8.43pm yesterday you gave 192.168.xx.110 as the response from nslookup.  Note the second octet is different (161 vs 168) compared to the response when 8.8.8.8 is specified on the command line.   Which is correct?  My initial response was based on the 168 being accurate, as it makes all the difference in the world in routing terms.