-
-
Notifications
You must be signed in to change notification settings - Fork 174
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Separate result between nameserver #40
Comments
How about just adding the query and the server targeted into the reply structure, similar like other folks do? For debug you then could offer ever tiny little detail in the protocol stack section, including the protocol specific versions, packet/message size, headers, encryption algorithms, key length, session setup/expiry timestamps, etc.
Proabably it would be a good if as many packages in the DNS toolchain could align on a more strictly typed and value While the IANA DNS parameters registry is machine readable, but more than one of the parameter tables is obviously not very uniformly defined There is promising work under way to represent the IANA dns-parameters registry in a more modern model based on YANG.
It may also be useful to reuse other YANG defind models, for example for IP addressing, see |
I decided to build my own: digs |
I have a python script called digs that do multiple dig on specified nameservers.
Today I am trying dog, and I love its ability to accept multiple nameservers.
However I can't point which is wich. What if dog have a separator between them if we supply multiple nameservers ?
My current workaround is to use JSON output and filter the result:
The text was updated successfully, but these errors were encountered: