Menu
Reply
Highlighted
  • 24
  • 0
  • 4
On our wavelength
693 Views
Message 81 of 96
Flag for a moderator

Re: Unable to access https://www.evanscycles.com/


@Lucy_B wrote:

Hi all, 

Thanks for getting back to me so quickly about this issue. 

I'm going to pass all of this information back onto the networks team so that we can continue our investigations. 

As soon as I have a further update I'll be back in touch on this thread. 

Thanks

Lucy_B


Thanks for chasing this up Lucy_B.

Regards,

Simon

0 Kudos
Reply
Highlighted
  • 18.6K
  • 1.09K
  • 8K
Very Insightful Person
Very Insightful Person
677 Views
Message 82 of 96
Flag for a moderator

Re: Unable to access https://www.evanscycles.com/


@sjforster wrote:

 

I also tried your dig command at the beginning of your post 

 

 

 

dig +trace +nodnssec a sni.ssl.evanscycles.com.c.footprint.net.

 

 

 

 

Not sure if its an issue with the switches with dig on macOS, or the version of dig or if it symptomatic of the problem I've got but the response I received was:

 

 

 

dig +trace +nodnssec a sni.ssl.evanscycles.com.c.footprint.net.

; <<>> DiG 9.10.6 <<>> +trace +nodnssec a sni.ssl.evanscycles.com.c.footprint.net.
;; global options: +cmd
;; connection timed out; no servers could be reached

 

 

 

 

Regards,

Simon


It's handling DNS lookups normally so I'd say it's something to do with the way DIG is setup on the Mac.  I'll see if I can DIG up more info but I'll respond in a unique thread, as I don't want to derail this one.

Tim

Edit - try this one:

dig +trace +nodnssec a sni.ssl.evanscycles.com.c.footprint.net. @1.1.1.1

Tim

I'm a Very Insightful Person, I'm here to share knowledge, I don't work for Virgin Media. Learn more

Have I helped? Click Mark as Helpful Answer or use Kudos to say thanks

0 Kudos
Reply
Highlighted
  • 24
  • 0
  • 4
On our wavelength
668 Views
Message 83 of 96
Flag for a moderator

Re: Unable to access https://www.evanscycles.com/

Hi Tim,

Thanks for the quick reply.

Response from dig to 1.1.1.1 command below:

dig +trace +nodnssec a sni.ssl.evanscycles.com.c.footprint.net. @1.1.1.1

; <<>> DiG 9.10.6 <<>> +trace +nodnssec a sni.ssl.evanscycles.com.c.footprint.net. @1.1.1.1
;; global options: +cmd
.			5370	IN	NS	d.root-servers.net.
.			5370	IN	NS	e.root-servers.net.
.			5370	IN	NS	f.root-servers.net.
.			5370	IN	NS	g.root-servers.net.
.			5370	IN	NS	h.root-servers.net.
.			5370	IN	NS	i.root-servers.net.
.			5370	IN	NS	j.root-servers.net.
.			5370	IN	NS	k.root-servers.net.
.			5370	IN	NS	l.root-servers.net.
.			5370	IN	NS	m.root-servers.net.
.			5370	IN	NS	a.root-servers.net.
.			5370	IN	NS	b.root-servers.net.
.			5370	IN	NS	c.root-servers.net.
;; Received 431 bytes from 1.1.1.1#53(1.1.1.1) in 44 ms

net.			172800	IN	NS	f.gtld-servers.net.
net.			172800	IN	NS	b.gtld-servers.net.
net.			172800	IN	NS	e.gtld-servers.net.
net.			172800	IN	NS	j.gtld-servers.net.
net.			172800	IN	NS	k.gtld-servers.net.
net.			172800	IN	NS	g.gtld-servers.net.
net.			172800	IN	NS	c.gtld-servers.net.
net.			172800	IN	NS	l.gtld-servers.net.
net.			172800	IN	NS	d.gtld-servers.net.
net.			172800	IN	NS	h.gtld-servers.net.
net.			172800	IN	NS	m.gtld-servers.net.
net.			172800	IN	NS	a.gtld-servers.net.
net.			172800	IN	NS	i.gtld-servers.net.
;; Received 861 bytes from 192.112.36.4#53(g.root-servers.net) in 75 ms

footprint.net.		172800	IN	NS	ns100.footprint.net.
footprint.net.		172800	IN	NS	ns101.footprint.net.
footprint.net.		172800	IN	NS	ns102.footprint.net.
footprint.net.		172800	IN	NS	ns103.footprint.net.
footprint.net.		172800	IN	NS	ns105.footprint.net.
;; Received 332 bytes from 192.43.172.30#53(i.gtld-servers.net) in 38 ms

c.footprint.net.	86400	IN	NS	usa-e.dns.footprint.net.
c.footprint.net.	86400	IN	NS	eu-b.dns.footprint.net.
c.footprint.net.	86400	IN	NS	eu-c.dns.footprint.net.
c.footprint.net.	86400	IN	NS	usa-c.dns.footprint.net.
c.footprint.net.	86400	IN	NS	apac-a.dns.footprint.net.
c.footprint.net.	86400	IN	NS	eu-a.dns.footprint.net.
c.footprint.net.	86400	IN	NS	usa-a.dns.footprint.net.
c.footprint.net.	86400	IN	NS	usa-b.dns.footprint.net.
c.footprint.net.	86400	IN	NS	eu-d.dns.footprint.net.
c.footprint.net.	86400	IN	NS	usa-f.dns.footprint.net.
c.footprint.net.	86400	IN	NS	usa-d.dns.footprint.net.
;; Received 1025 bytes from 8.254.14.2#53(ns105.footprint.net) in 40 ms

sni.ssl.evanscycles.com.c.footprint.net. 230 IN	A 8.241.5.122
c.footprint.net.	86400	IN	NS	eu-a.dns.footprint.net.
c.footprint.net.	86400	IN	NS	eu-b.dns.footprint.net.
c.footprint.net.	86400	IN	NS	eu-c.dns.footprint.net.
c.footprint.net.	86400	IN	NS	eu-d.dns.footprint.net.
;; Received 164 bytes from 8.254.93.27#53(eu-a.dns.footprint.net) in 39 ms

I also tried it using the routers IP address which gave the timed out error experienced earlier.

dig +trace +nodnssec a sni.ssl.evanscycles.com.c.footprint.net. @192.168.0.1

; <<>> DiG 9.10.6 <<>> +trace +nodnssec a sni.ssl.evanscycles.com.c.footprint.net. @192.168.0.1
;; global options: +cmd
;; connection timed out; no servers could be reached

Also tried Virgin Media primary DNS server which also worked with the following response:

dig +trace +nodnssec a sni.ssl.evanscycles.com.c.footprint.net. @194.168.4.100

; <<>> DiG 9.10.6 <<>> +trace +nodnssec a sni.ssl.evanscycles.com.c.footprint.net. @194.168.4.100
;; global options: +cmd
.			294157	IN	NS	h.root-servers.net.
.			294157	IN	NS	e.root-servers.net.
.			294157	IN	NS	i.root-servers.net.
.			294157	IN	NS	f.root-servers.net.
.			294157	IN	NS	c.root-servers.net.
.			294157	IN	NS	g.root-servers.net.
.			294157	IN	NS	j.root-servers.net.
.			294157	IN	NS	d.root-servers.net.
.			294157	IN	NS	m.root-servers.net.
.			294157	IN	NS	k.root-servers.net.
.			294157	IN	NS	b.root-servers.net.
.			294157	IN	NS	l.root-servers.net.
.			294157	IN	NS	a.root-servers.net.
;; Received 811 bytes from 194.168.4.100#53(194.168.4.100) in 37 ms

net.			172800	IN	NS	a.gtld-servers.net.
net.			172800	IN	NS	b.gtld-servers.net.
net.			172800	IN	NS	c.gtld-servers.net.
net.			172800	IN	NS	d.gtld-servers.net.
net.			172800	IN	NS	e.gtld-servers.net.
net.			172800	IN	NS	f.gtld-servers.net.
net.			172800	IN	NS	g.gtld-servers.net.
net.			172800	IN	NS	h.gtld-servers.net.
net.			172800	IN	NS	i.gtld-servers.net.
net.			172800	IN	NS	j.gtld-servers.net.
net.			172800	IN	NS	k.gtld-servers.net.
net.			172800	IN	NS	l.gtld-servers.net.
net.			172800	IN	NS	m.gtld-servers.net.
;; Received 861 bytes from 198.41.0.4#53(a.root-servers.net) in 30 ms

footprint.net.		172800	IN	NS	ns100.footprint.net.
footprint.net.		172800	IN	NS	ns101.footprint.net.
footprint.net.		172800	IN	NS	ns102.footprint.net.
footprint.net.		172800	IN	NS	ns103.footprint.net.
footprint.net.		172800	IN	NS	ns105.footprint.net.
;; Received 332 bytes from 192.12.94.30#53(e.gtld-servers.net) in 54 ms

c.footprint.net.	86400	IN	NS	usa-d.dns.footprint.net.
c.footprint.net.	86400	IN	NS	usa-b.dns.footprint.net.
c.footprint.net.	86400	IN	NS	usa-f.dns.footprint.net.
c.footprint.net.	86400	IN	NS	apac-a.dns.footprint.net.
c.footprint.net.	86400	IN	NS	usa-c.dns.footprint.net.
c.footprint.net.	86400	IN	NS	eu-d.dns.footprint.net.
c.footprint.net.	86400	IN	NS	usa-e.dns.footprint.net.
c.footprint.net.	86400	IN	NS	eu-b.dns.footprint.net.
c.footprint.net.	86400	IN	NS	eu-c.dns.footprint.net.
c.footprint.net.	86400	IN	NS	eu-a.dns.footprint.net.
c.footprint.net.	86400	IN	NS	usa-a.dns.footprint.net.
;; Received 1025 bytes from 8.254.13.2#53(ns103.footprint.net) in 33 ms

sni.ssl.evanscycles.com.c.footprint.net. 230 IN	A 8.241.5.122
c.footprint.net.	86400	IN	NS	eu-a.dns.footprint.net.
c.footprint.net.	86400	IN	NS	eu-b.dns.footprint.net.
c.footprint.net.	86400	IN	NS	eu-c.dns.footprint.net.
c.footprint.net.	86400	IN	NS	eu-d.dns.footprint.net.
;; Received 164 bytes from 8.254.35.153#53(eu-d.dns.footprint.net) in 54 ms

Regards,

Simon

0 Kudos
Reply
Highlighted
  • 14.74K
  • 620
  • 1.42K
Alessandro Volta
655 Views
Message 84 of 96
Flag for a moderator

Re: Unable to access https://www.evanscycles.com/

Come on VM its a CDN or routing issue your side for give VM WAN IP's

site runs fine for me

Question:
Name=www.evanscycles.com, QTYPE=A, QCLASS=INET

Answer Section:
* Name=www.evanscycles.com
Type=CNAME, Class=INET, TTL=3397( 56 Minutes 37 sec), RDLENGTH=41
CNAME=sni.ssl.evanscycles.com.c.footprint.net

* Name=sni.ssl.evanscycles.com.c.footprint.net
Type=A, Class=INET, TTL=27( 27 sec), RDLENGTH=4
IP Address=67.26.42.112

* Name=sni.ssl.evanscycles.com.c.footprint.net
Type=A, Class=INET, TTL=27( 27 sec), RDLENGTH=4
IP Address=8.238.10.122

* Name=sni.ssl.evanscycles.com.c.footprint.net
Type=A, Class=INET, TTL=27( 27 sec), RDLENGTH=4
IP Address=8.238.11.122

---------------------------------------------------------------
0 Kudos
Reply
Highlighted
  • 1.66K
  • 57
  • 159
Moderator
Moderator
621 Views
Message 85 of 96
Flag for a moderator

Re: Unable to access https://www.evanscycles.com/

Hi All, 

 

I just wanted to let you all know that this issue is still being investigated. 

 

It is currently with our network management team who are continuing to investigate this matter. 

 

Sadly I don't have any further update just yet, but rest assured we're continuing to work to see this resolved as soon as possible. 

 

Thanks

Lucy_B

The do's and don'ts. Keep the community welcoming for all. Follow the house rules


0 Kudos
Reply
Highlighted
  • 5.87K
  • 1.11K
  • 1.55K
Very Insightful Person
Very Insightful Person
618 Views
Message 86 of 96
Flag for a moderator

Re: Unable to access https://www.evanscycles.com/

Hello

Just to let you all know it is now working from my connection.

Regards Mike

I'm a Very Insightful Person, I'm here to share knowledge, I don't work for Virgin Media. Learn more

Have I helped? Click Mark as Helpful Answer or use Kudos to say thanks

Highlighted
  • 18.6K
  • 1.09K
  • 8K
Very Insightful Person
Very Insightful Person
600 Views
Message 87 of 96
Flag for a moderator

Re: Unable to access https://www.evanscycles.com/

 Can you DIG to see what the IP address that comes back is?

Tim

I'm a Very Insightful Person, I'm here to share knowledge, I don't work for Virgin Media. Learn more

Have I helped? Click Mark as Helpful Answer or use Kudos to say thanks

0 Kudos
Reply
Highlighted
  • 5.87K
  • 1.11K
  • 1.55K
Very Insightful Person
Very Insightful Person
598 Views
Message 88 of 96
Flag for a moderator

Re: Unable to access https://www.evanscycles.com/

Hello Tim

Latest dig

; <<>> DiG 9.11.5-P4-5.1ubuntu2.1-Ubuntu <<>> 8.249.255.248
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 12711
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;8.249.255.248. IN A

;; Query time: 25 msec
;; SERVER: 127.0.0.53#53(127.0.0.53)
;; WHEN: Tue Dec 17 12:52:50 GMT 2019
;; MSG SIZE rcvd: 42

sysadmin@carrot:~$

These are from a linux box default DNS is OpenDNS for my network.

And nslookup

Server: diskworld.redwood.com
Address: xxx.xxx.xxx.xxx

Non-authoritative answer:
Name: sni.ssl.evanscycles.com.c.footprint.net
Addresses: 8.238.11.250
8.238.10.250
8.238.11.122
Aliases: www.evanscycles.com

Regards Mike

I'm a Very Insightful Person, I'm here to share knowledge, I don't work for Virgin Media. Learn more

Have I helped? Click Mark as Helpful Answer or use Kudos to say thanks

0 Kudos
Reply
Highlighted
  • 18.6K
  • 1.09K
  • 8K
Very Insightful Person
Very Insightful Person
592 Views
Message 89 of 96
Flag for a moderator

Re: Unable to access https://www.evanscycles.com/

Your DIG query looks wrong.  But the nslookup shows you’re not being given the problematic IP as an answer.

Tim

I'm a Very Insightful Person, I'm here to share knowledge, I don't work for Virgin Media. Learn more

Have I helped? Click Mark as Helpful Answer or use Kudos to say thanks

0 Kudos
Reply
Highlighted
  • 1.66K
  • 57
  • 159
Moderator
Moderator
579 Views
Message 90 of 96
Flag for a moderator
Helpful Answer

Re: Unable to access https://www.evanscycles.com/

Hi All, 

 

Our network management team have made some changes, which they are hoping will now resolve this issue. 

 

Could you possible test this again, including running a traceroute and let me know the outcome please?

 

Hopefully you'll all be able to view the site as normal moving forward. 

 

Thanks

Lucy_B

The do's and don'ts. Keep the community welcoming for all. Follow the house rules