I was browsing hackernews (https://news.ycombinator.com) the other day and I noticed a broken link in one of the “Who is Hiring” monthly threads:
Specifically, the link that didn’t (doesn’t) work is:
The failure that I’m seeing is a failure to resolve a A record ‘cardinalfinancial.com’.
If I go to mxtoolbox.com and run a A record lookup, they find a result:
If I go to viewdns.info and get them to list all DNS records for cardinalfinancial.com they show an A record:
Both sets of results agree with each other: two A records exist and point to 220.127.116.11 & 18.104.22.168 respectively. If I modify my local hosts file to set ‘cardinalfinancial.com’ to point to either of these IP addresses, the website works perfectly. The web server is up, but without helping out my local machine, I can’t resolve the domain’s A record locally.
I found another public DNS checking site that agrees with my local experience:
If I request “ANY” for cardinalfinancial.com, I see all the other results (NS, MX, TXT) but no A records. I tried 8.8.8.* plus all of the NS listed as authoritative for cardinalfinancial.com
So some methods of querying DNS are bringing back A records, but others are not. I’ve never seen a situation like that before.
Can you help me understand what is going on here?
Edit for clairity: I’m not linked in any way to any of the organisations involved here, I’m just a curious observer.
Powered by WPeMatico