I need help collecting some sort of proof of what might be wrong here
Ping <domain.net> Ping request could not find host <domain.net>. Please check the name and try again.
Ping <domain.net> Pinging <domain.net> [1XX.62.173.xxx] with 32 bytes of data: Reply from 1XX.62.173.xxx: bytes=32 time=73ms TTL=57 Reply from 1XX.62.173.xxx: bytes=32 time=70ms TTL=57 Reply from 1XX.62.173.xxx: bytes=32 time=73ms TTL=57 Reply from 1XX.62.173.xxx: bytes=32 time=72ms TTL=57
location 1 seems to be not limited to my own network but several isp's in sweden
location 2 is work place via vpn which comes out somewhere in uk.
is managed through registrar that points to nameservers of a cloud hosting company Both companies do not see the problem from their location, from their perspective this problem does not exist.
When problem started:
I switch registrar and changed the nameservers, the domain has propogated fully and it has passed more than 72hours.
if I do
dig SOA @g.root-servers.net net
.. it resolves all they way down to the domain.net correctly.
My gut feeling is some dns server is not updating and I want to find out which one so that I can take this further. So far I have been able to rule out the registrar and the host of the nameservers,based on their claim. I need help troubleshooting. I'm trying not to give away the domain name and servers involved as far as possible.
I have also read related threads and none of them really express the same issue or have any response to solve my problem. If this post is not right for this forum/section please let me know.
Update I have reduced the problem scope slightly by using the registrar nameservers, and using A records to point directly to the server ip. Again I can ping the domain from location 2 when it has fully propogated and not from location 1.
atdns01.citynetwork.se atdns02.citynetwork.se atdns03.citynetwork.se
instead of the cloud nameservers on digital ocean
ns1.digitalocean.com ns2.digitalocean.com ns3.digitalocean.com
I think you can ping these and see that they have different ip's @Andrew B.
http://www.whatsmydns.net looks ok, this is the main tool I use to verify the propagation most of the time.
Update2 Doing the last modification, I was able to ask the registrar why I was not able to ping domain.net, without them being able to easily blame it on someone else.
So far they have found that domain.net was missing zone file in their system. Having fixed that they discovered that DNSSEC was configured and that they do not support DNSSEC. Probably a configuration that came from previous registrar when doing the transfer? I still don't get why I'm able to ping this domain from location 2 and not from location 1. This domain should have not been reachable from any location?