Can't connect to Rod Elliott's site

[Netlist]

I'm unable to reach Rod Elliott's site for more than a week now on a Win10 PC.
Tried different browsers: Firefox, Chrome, Edge with the following error: DNS_PROBE_FINISHED_NXDOMAIN
I restarted the PC, all updates are in place, no other sites are affected.

Causes:

You typed the site name incorrectly into the search bar. I clicked the links in Google so no typing errors.
There is an internet connection error preventing your access. All other sites work.
Your firewall is blocking access to the website. Disabling it doesn't help.
An antivirus or a VPN is interfering with your network settings. AV= standard Windows defender, I do not use VPN
The domain has expired or is not registered. ??? I believe others can access the site.
Your DNS settings are not configured the right way.

I tried all options here: https://kinsta.com/knowledgebase/dns_probe_finished_nxdomain/

I'm out of ideas, reaching out to the smart(er) guys.

Hugo

 

[AllenB]

I’d start by saying I can reach the site. https://sound-au.com/

Perhaps there’s a geographical or IP address based reason, but this isn’t the first time I’ve heard of this.

 

[mbrennwa]

https://sound-au.com works fine for me. Would be a bummer if that site would stop working!

 

[Netlist]

Perhaps there’s a geographical or IP address based reason.

Might...
It's been erratic for many weeks and now stopped completely.
I can ping 163.47.74.1 but when typed in the browser I get this error page:

 

[Jeffh01]

Not just you https://www.diyaudio.com/community/threads/the-audio-pages.411450/post-7654505

 

[Netlist]

I tried Google DNS servers but it didn't stick. (my error)
I retried 8.8.8.8 and 8.8.4.4 and now it works.

Thanks a lot!

Hugo

 

[Indiglo]

On a windows machine open up a command prompt and type -
tracert sound-au.com
This will hopefully give an indication on where in the routing chain from your pc to the sound-au website fails, be mindful some internet routers may not respond to ping or tracert.
The first hop will be your router at home, the next couple of hops or so will be your ISP internal network
The end destination site should be - ipa32f4a01.ipv4.syd02.ds.network [163.47.74.1]

 

[Netlist]

Different and very erratic tracert with IPv6 but the connection to sound-au.com is nevertheless good and very fast.
I guess I need to disable IPv6 to get an IPv4 result?
I changed the IPv6 DNS to:

 

[stv]

I experienced repeated connection problems with rod's site during the last weeks.
But it usually works again after some time.

 

[Indiglo]

You can force tracert to use either ipv4 or ipv6 -
help - tracert /?
To force ipv4 - tracert -4 sound-au.com
To force ipv6 - tracert -6 sound-au.com
ipv6 may fail if your computer network settings is not set to use ipv6

 

[Netlist]

Thanks, network can do both but I wasn't aware of the tracert options.

I experienced repeated connection problems with rod's site during the last weeks.
But it usually works again after some time.

Yes, weird..

 

[UniQ]

Works here (can't direct access ipv4 # though, get the same error page), and ok according to the following 3 is-it-down sites below.
https://issitedownrightnow.com/status/sound-au.com
https://www.isitdownrightnow.com/sound-au.com.html
https://www.freshworks.com/website-monitoring/is-it-down/sound-au.com/

Server test seems ok too.
https://www.ssllabs.com/ssltest/analyze.html?d=sound-au.com

 

[Netlist]

Server test says this, so there might be something wrong on Rod's side:

 

[UniQ]

Clicking on the ipv6 # takes to a detailed page, it only complains because they use outdated TLS 1.1 and therefore receives Grade B.
https://blog.qualys.com/product-tech/2018/11/19/grade-change-for-tls-1-0-and-tls-1-1-protocols

ipv4 on the other hand doesn't support anything less than TLS 1.2.

edit: the other threads attached snapshot also indicated DNS_PROBE_FINISHED_NXDOMAIN hinting it's a DNS server problem.
Try this DNS: https://adblock.dns.mullvad.net/dns-query

 

[jamesfeline]

I cannot connect either from the UK

 

[Netlist]

the other thread had a DNS_PROBE_FINISHED_NXDOMAIN hinting it's a DNS server problem.

Its is a DNS problem, see my first post.
I cured it with Google's DNS servers.
https://www.diyaudio.com/community/threads/cant-connect-to-rod-elliotts-site.411460/post-7654525

 

[Terry2000]

I have experienced accessing the site difficult since Rod's March Index page update. For a week or so few links from index worked so a DNS only issue is doubtful as mobile phone browser access and and FireFox on a PC s mostly impossible. I can access only using Edge. I'll give Rod a heads-up by email. Sometimes the server's admin posting panel can break things!

 

[Netlist]

For people who don't know how to change the DNS settings (that cured my problem, others seem to exist):
Control panel-> Network-> Change Adapter Settings-> Select Properties on your currently connected adapter-> Select Internet Protocol Version 4 -> Properties-> Fill the boxes with 8.8.8.8 and 8.8.4.4 and check 'Validate settings upon exit'-> OK

 

[Dieter Geissel]

I am using a pi-hole dns server. I never had problems to reach the side.

 

[Terry2000]

I have experienced accessing the site difficult since Rod's March Index page update. For a week or so few links from index worked so a DNS only issue is doubtful as mobile phone browser access and and FireFox on a PC s mostly impossible. I can access only using Edge. I'll give Rod a heads-up by email. Sometimes the server's admin posting panel can break things!

Typo - meant to write Hosting Panel.