Been playing with Doggo since I like a great deal of the features. But one use case I have come across is support for type 65 lookups used by currently Draft RFC 9460 (https://datatracker.ietf.org/doc/rfc9460/)
I see that doggo has support for -t or --type queries but when attempting 65.
Queries
login.microsoftonline.com: type Unused, class IN
Name: login.microsoftonline.com
[Name Length: 25]
[Label Count: 3]
Type: Unused (0)
Class: IN (0x0001)
I get the following errors back on the CLI.
$ doggo @192.168.100.219 login.microsoftonline.com -t=TYPE65
time=2024-07-10T14:13:44.364-07:00 level=ERROR msg="Error looking up DNS records" error="context deadline exceeded"
$ doggo @192.168.100.219 login.microsoftonline.com -t=65
time=2024-07-10T14:13:55.153-07:00 level=ERROR msg="error in lookup" error="read udp 192.168.100.6:42976->192.168.100.219:53: i/o timeout"
time=2024-07-10T14:13:55.153-07:00 level=ERROR msg="Error looking up DNS records" error="context deadline exceeded"
When performing this via dig it appears to work accordingly.
Queries
login.microsoftonline.com: type HTTPS, class IN
Name: login.microsoftonline.com
[Name Length: 25]
[Label Count: 3]
Type: HTTPS (65) (HTTPS Specific Service Endpoints)
Class: IN (0x0001)```
Since this isn't for DoH using @https://x.x.x.x lookups but a record type wasn't sure if this would apply either way. Would just be helpful to have this functionality for future usage scenario testing. Since it's a current draft RFC at this time I understand if this isn't on the current roadmap.
Been playing with Doggo since I like a great deal of the features. But one use case I have come across is support for type 65 lookups used by currently Draft RFC 9460 (https://datatracker.ietf.org/doc/rfc9460/)
I see that doggo has support for -t or --type queries but when attempting 65.
doggo @192.168.100.219 login.microsoftonline.com -t=65 doggo @192.168.100.219 login.microsoftonline.com -t=TYPE65
A packet capture shows this as "type Unused,"
Queries login.microsoftonline.com: type Unused, class IN Name: login.microsoftonline.com [Name Length: 25] [Label Count: 3] Type: Unused (0) Class: IN (0x0001)
I get the following errors back on the CLI.
When performing this via dig it appears to work accordingly.
dig -t TYPE65 @192.168.100.219 login.microsoftonline.com
Queries login.microsoftonline.com: type HTTPS, class IN Name: login.microsoftonline.com [Name Length: 25] [Label Count: 3] Type: HTTPS (65) (HTTPS Specific Service Endpoints) Class: IN (0x0001)```
Output from the dig command
Since this isn't for DoH using @https://x.x.x.x lookups but a record type wasn't sure if this would apply either way. Would just be helpful to have this functionality for future usage scenario testing. Since it's a current draft RFC at this time I understand if this isn't on the current roadmap.