Dig returns incorrect DNS record, but only on specific network. What's wrong?

domain-name-system

Since you are querying the authoritative server directly, caching should not be a factor.

I see two main options:

  • ns3.he.net is anycast (which I believe is the case) and some anycast node(s) are out of sync. This would only make sense as an explanation if the record had the value 18.204.152.241 at some point, though.
  • Your ISP, you, or potentially someone else is intercepting DNS in/from your network and providing different answers.

Related

How to set NTFS permissions and preserve inherited
Spring: Returning empty HTTP Responses with ResponseEntity<Void> doesn't work
How do I create a master branch in a bare Git repository?
How can I convert an integer into its verbal representation?
pip requirements.txt with alternative index
How to get current controller and action from inside Child action?
Wrap link <a> around <div>
Custom Bad Gateway Page with Nginx
Does the size used with NVARCHAR matter?
Accessing the query string in ASP.Net Web Api?
Choose bower install directory
HTTPS redirect from root domain (i.e. apex or 'naked') to 'www' subdomain without browser throwing up?