Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!



Last Active
Administrator, Moderator


  • Correct. Those are our IPs. As I stated before, the variation in responses is due to the nature of Anycast. We do not have any further information on Intex or where that name came from, you would need to ask the site that is providing that respons…
  • In the image you posted above, the IP address ending in 228.74
  • According to ARIN, the IP range in "What is my IP" is assigned to BAKINTER-NET-XDSL. Browserleaks may have interpreted that as INTEX-NET, but you would need to reach out to them for further information. We have no affiliation with that site and no…
  • Additionally, using public geolocation databases, the IPs that dnsleaktest is reporting as US based are actually located in the Netherlands.
  • Verisign's recursive DNS service is Anycast, so destination is determined based on several factors, such as which is the nearest, lowest cost, healthiest, with the least congested route. As neither of these tools are administered by Verisign, we c…
  • Verisign Public DNS is a free DNS service. Configuration instructions can be found at https://publicdnsforum.verisign.com/discussion/13/verisign-public-dns-set-up-configuration-instructions#latest
    in Public DNS Comment by jcraft February 7
  • Sean, At Verisign we are always reviewing the latest updates and security measures. We are currently reviewing both DNS over TLS and DNS over HTTPS, but we do not have specific implementation dates at this time. We will update when more information…
  • Sean, we are reviewing your inquiry and will follow up when we have more information. Regards, Jason C
  • Hello WSR, our public DNS has no ACL, so no whitelisting is required. Our recursive servers are EDNS enabled. Does that answer your question?
  • Our Public DNS is anycast , so destination is determined based on several factors, such as which is the nearest, lowest cost, healthiest, with the least congested route, or some other distance measure.
  • The traffic from your location is routing to the nearest site and the level of latency experienced is expected behavior from your location.
  • Yes, the issue was discovered and resolved yesterday.
  • Thank you for the information. We are reviewing at this time.
  • After further review we are not seeing abnormal behavior from our recursive server. The routing and different geographic responses may be a result of configuration setting at the destination which determines where queries are coming in from and as…
  • Simon, thanks for your continued patience as we are still reviewing the data you provided.
  • Doing some DIGs it appears there is an issue with a broken chain of trust for your domain. You can see the errors at http://dnsviz.net/d/sfasu.edu/dnssec/ You will need to ensure that your domain is signed at both the registry and on your name ser…