Little late for the QnA but here it is. DNS is often fetched by intermediate servers. Your system is configured to use say 192.168.1.1 (your router), which in turn uses your ISP's DNS, which in-turn could be using n number of intermediate DNS servers. DNS is also cached, and TTL is sometimes not respected by intermediaries. Even if TTL was respected, due to the dynamic nature of requests and responses the caching mechanism in the intermediate DNS servers are going to be overwhelmed. All these systems would be designed with assumption that responses are short, TXT queries are rare, records, especially potentially long ones like TXT are not going to change that often. The whole caching mechanism will be optimized for the "normal" DNS use case. So widespread adoption of this technique could cause some chaos.
Little late for the QnA but here it is. DNS is often fetched by intermediate servers. Your system is configured to use say 192.168.1.1 (your router), which in turn uses your ISP's DNS, which in-turn could be using n number of intermediate DNS servers. DNS is also cached, and TTL is sometimes not respected by intermediaries. Even if TTL was respected, due to the dynamic nature of requests and responses the caching mechanism in the intermediate DNS servers are going to be overwhelmed. All these systems would be designed with assumption that responses are short, TXT queries are rare, records, especially potentially long ones like TXT are not going to change that often. The whole caching mechanism will be optimized for the "normal" DNS use case. So widespread adoption of this technique could cause some chaos.
so cool !
lol i love this.
im making use of this in my next project (i exactly needed something like this hahahha)
Learning about DNS from someone else's cool side project 😅
not all queries are for that TXT , bot probing