The domain is held with NameCheap and is currently active. I’m using the following name severs as recommended by the Netlify admin panel/documentation.
For the both the primary domain and the www redirect I can see a coloured tick next to the Netlify DNS label.
My current DNS records with Netlify are:
carlosterly.photography 3600 IN NETLIFY cophotography.netlify.app
www.carlosterly.photography 3600 IN NETLIFY cophotography.netlify.app
Everything has been running smoothly since I intially setup the account, but I noticed today that I can’t access the site via the custom domain. I can only access it via the Netlify site name.
When I do a traceroute I get the following response:
➜ traceroute carlosterly.photography
traceroute: Warning: carlosterly.photography has multiple addresses; using 54.66.176.79
traceroute to carlosterly.photography (54.66.176.79), 64 hops max, 52 byte packets
1 192.168.1.1 (192.168.1.1) 3.350 ms 1.814 ms 1.649 ms
2 10.20.21.36 (10.20.21.36) 12.780 ms 12.876 ms 14.205 ms
3 syd-apt-ros-cdn11-be200.tpgi.com.au (203.29.134.125) 14.196 ms 14.571 ms 14.472 ms
4 99.82.178.204 (99.82.178.204) 14.882 ms 13.909 ms 13.489 ms
5 15.230.23.219 (15.230.23.219) 14.455 ms
15.230.23.221 (15.230.23.221) 15.198 ms
15.230.23.223 (15.230.23.223) 15.609 ms
6 150.222.112.143 (150.222.112.143) 13.592 ms
150.222.112.169 (150.222.112.169) 14.861 ms
150.222.112.185 (150.222.112.185) 14.486 ms
7 150.222.112.168 (150.222.112.168) 15.596 ms
150.222.112.152 (150.222.112.152) 14.752 ms
150.222.112.182 (150.222.112.182) 14.216 ms
8 52.95.38.182 (52.95.38.182) 14.092 ms
52.95.38.176 (52.95.38.176) 14.623 ms
52.95.36.95 (52.95.36.95) 14.858 ms
9 52.95.38.109 (52.95.38.109) 15.415 ms
52.95.38.105 (52.95.38.105) 19.577 ms
52.95.38.17 (52.95.38.17) 19.457 ms
10 * * *
11 * * *
I will also raise a request with NameCheap support just in case there is an issue at their end. From within the NameCheap admin panel I can see the domain is active and name severs have been configured correctly.
Any help or advice you could provide would be greatly appreciated
I also see that your Netlify name servers are configured:
dig carlosterly.photography NS +trace | tail -n 6
carlosterly.photography. 3600 IN NS dns1.p04.nsone.net.
carlosterly.photography. 3600 IN NS dns2.p04.nsone.net.
carlosterly.photography. 3600 IN NS dns3.p04.nsone.net.
carlosterly.photography. 3600 IN NS dns4.p04.nsone.net.
;; Received 141 bytes from 2620:4d:4000:6259:7:4:0:3#53(dns3.p04.nsone.net) in 41 ms
Are you seeing this only on specific networks? If you try another network and/or another computer do you have the same issue? If you are still having issues, could you tell us what happens when you visit carlosterly.photography? Do you see an error message?
My apologies for the late reply. Thanks for taking the time to complete the tests, I really appreciate it.
It turns out that I’m having a problem only accessing the site through my employers VPN. I’ve spoken with our network administrator and he says he’s not aware of any configuration issues or problems that would prevent me from accessing the site.
Having said that he is unable to access the site via our VPN, so I think there’s definitely an issue at our end.
I can access the main Netlify web site via our VPN so now I’m trying to determine why my web site which is hosted on the same Netlify infrastructure will not resolve.
Are there any test URL’s that I could provide my network administrator to demonstrate that the issue is not related to my site? Are there specific DNS or IP connectivity tests I could get the network admin to do that might narrow down the issue. Perhaps we are blocking ourselves from some or all parts of the Netlify network by accident?
I know the issue is with our VPN but I’m not sure how I’m going to go about proving this to my network admin.
Any help or advice you could provide would be greatly appreciated.
Thanks for your reply. I can access petsofnetlify.com via my work VPN. So I guess that’s a good sign. I’ll have a talk with our network administrator and see what I can work out.
