You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a wonderful library. I am curious how to structure query responses in cases where you want to authoritatively answer that this domain cannot be found.
+1. It seems it trivially works to set the last two bits of the flags bitfield in the param object passed to encode. (the last 4 bits are the rcode, and NXDOMAIN is 0x03). So e.g.:
For example, setting flags: 1 << 12 changes the opcode to STATUS and flags: 3 changes the rcode to NXDOMAIN. You can combine multiple settings using bitwise or (|) e.g. flags: (1 << 12) | 3.
This is a wonderful library. I am curious how to structure query responses in cases where you want to authoritatively answer that this domain cannot be found.
I found the following article: Know thy DNS: Understanding the four most common DNS response codes
Unless I missed something, would it be worthwhile to document how to formulate (and return) the NXDOMAIN response?
The text was updated successfully, but these errors were encountered: