[RT# 44978] dig feature to print unexpected reply messages
Mark,
I was wondering how difficult it would be to have an option where dig would parse DNS replies seen from the unexpected source for debugging purposes.
Example from the IETF network:
dig @75.75.75.75 +timeout=1 +retries=1000 ;; reply from unexpected source: 69.241.23.140#53, expected 75.75.75.75#53 ;; reply from unexpected source: 69.241.23.140#53, expected 75.75.75.75#53 ;; reply from unexpected source: 69.241.23.152#53, expected 75.75.75.75#53 ;; reply from unexpected source: 69.241.23.152#53, expected 75.75.75.75#53 ;; reply from unexpected source: 69.241.23.150#53, expected 75.75.75.75#53 ;; reply from unexpected source: 69.241.23.150#53, expected 75.75.75.75#53 ;; reply from unexpected source: 69.241.23.148#53, expected 75.75.75.75#53 ;; reply from unexpected source: 69.241.23.136#53, expected 75.75.75.75#53 ;; reply from unexpected source: 69.241.23.136#53, expected 75.75.75.75#53
"Jared Mauch" jared@puck.nether.net
comment [Mark] Seems reasonable. Basically it would be a new flag then parse and print the response.
Testing would require a custom server that replies from a different address.