not necessarily -- google.com is using anycast. authoritative servers for google.com will return an IP for your request for an A for google.com with an IP that they believe is appropriate for (read: closest to) your geolocation. ssh to a few boxes in different countries and do simultaneous A lookups on google.com and you'll get single results in each case, and each will return different IPs.
Just to be clear, returning different resource records (IP addresses, A records) in the answer section of a DNS response to different clients, based on geographical location, measured latency, etc, is different from anycast routing in which there exist multiple different routes to multiple different hosts all sharing the same IP address.
Link down. I’ve been using https://mywebtools.org
I discovered https://dnsdumpster.com/ the other day and found it to be incredibly useful.
Great tool. I've following code suggestion to add gaping for form fields on small screen:
<!-- Form Section --> <div class="card shadow-sm mb-5"> <div class="card-body"> <form method="GET" action=""> <div class="row"> <div class="col-md-8 mb-3 mb-md-0"> <input type="text" name="domain" class="form-control" placeholder="Enter a domain (e.g., example.com)" required> </div> <div class="col-md-3 mb-3 mb-md-0"> <select name="record_type" class="form-select" required> <option value="ALL">All Record Types</option> <option value="A">A</option> <option value="AAAA">AAAA</option> <option value="MX">MX</option> <option value="NS">NS</option> <option value="CNAME">CNAME</option> <option value="TXT">TXT</option> <option value="SRV">SRV</option> <option value="SOA">SOA</option> <option value="PTR">PTR</option> </select> </div> <div class="col-md-1"> <button type="submit" class="btn btn-primary w-100">Query</button> </div> </div> </form> </div> </div>
I've also made a similar tool: https://doggo.mrkaran.dev/. Can be useful when you want to query with a custom nameserver.
I get a single A rec for google.com. Pretty sure there should be multiple, no?
not necessarily -- google.com is using anycast. authoritative servers for google.com will return an IP for your request for an A for google.com with an IP that they believe is appropriate for (read: closest to) your geolocation. ssh to a few boxes in different countries and do simultaneous A lookups on google.com and you'll get single results in each case, and each will return different IPs.
Just to be clear, returning different resource records (IP addresses, A records) in the answer section of a DNS response to different clients, based on geographical location, measured latency, etc, is different from anycast routing in which there exist multiple different routes to multiple different hosts all sharing the same IP address.
Or use this tool and to check globally: https://www.whatsmydns.net/#A/google.com
Some locations are returning one ip, others are returning multiple, but to your point, they're different in different regions.
Google uses GEODNS, the IP are different for different users.
Also at googles scale round robin might cause unexpected issues.
dig returns a single IP address (one IPv4 and one IPv6) as well.
similar thing - https://search.reconwave.com/ - but it's passive and includes reverse dns search (all domains for given IP)
These days any new tool should support SVCB/HTTPS query types as well.
In the results table I'd fix the width of first two columns, so that tables can be more easily compared by switching between browser tabs.
If you want to visualize DNS propagation checkout dug: https://dug.unfrl.com/