Detecting Users' DNS Resolvers

Published July 24, 2022 • more posts

Let's say someone has visited your website; is it possible to determine what DNS resolvers their computer is configured to use?

Well, yes. Of course you can! This blogpost wouldn't be very long if the answer was no. Let's find out how. But before we begin...

Note that if your DNS resolver uses anycast, the IPs found here will not match the ones in your configuration. This is because those resolvers send out their queries on a separate non-anycast interface, to make sure that responses from nameservers are routed correctly.

How? §

Earliest this year, I wrote an incomplete implementation of the DNS protocol in NodeJS to create a tool for tracing DNS delegations in the browser. I soon realized that I could probably create a very rudimentary DNS server with what I had. Fast-forward to this morning, when I got the idea for identifying the user's resolvers by logging requests to the DNS server. And thus, I got to coding.

The code for the server is actually remarkably simple. In fact, pretty much all the logic is contained in a single method.

server.on("message", (data, rinfo) => {

    const reader = new DNS.DNSReader(data);
    const message =;
    const response = new DNS.DNSBuilder();

    const answers = message.questions.filter(question => question.type == DNS.RECORD_TYPE.A).map(question => question.domain);

    response.writeUInt16BE(message.questions.length) // # questions
            .writeUInt16BE(answers.length) // # answers
            .writeUInt16BE(0).writeUInt16BE(); // no NS/additional records

    for(const question of message.questions) {
        DNS.Question.write(response, question);

    for(const name of answers) {
        response.writeUInt16BE(1); // class 1 (IN)
        response.writeUInt32BE(0); // 0 TTL

        const list = queries.get(name) || [];
        queries.set(name, list);

    const buf =;
    server.send(buf, 0, buf.length, rinfo.port, rinfo.address);


As you can see, this server is not very smart. The only thing it is capable of is blindly responding to all queries for A records with a fixed IP address. However, for our case, that's sufficient.

The client code is even simpler. If you open up the network tab for this page and click the button again, you can see it at work; it simply generates a long random domain name, triggers a DNS query for that domain by initiating a request via fetch, and asks our crappy DNS server about which IPs have queried for those domains.

Applications §

What could this be useful for? I have no idea, to be honest, but I would like to hear what you think in the comments :)