--dig should ignore +noall in ~/.digrc
See original GitHub issueI have a ~/.digrc file to make using it a little less verbose where I specify +noall
and +answer
. Because of this, jc --dig
always outputs []
unless I use +all
explicitly.
~/.digrc
can be ignored with the -r
option as mentioned in the manpage.
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
dig show only answer - Server Fault
WIth the "+noall +noanswer" options I still must apply some string processing if I want to use the result in a script. –...
Read more >dig Command in Linux with Useful Examples - TecAdmin
We can use dig command to query various dns servers to fetch records like address record, CNAME, TXT, ... cat ~/.digrc +nocmd +noall...
Read more >Useful Linux Dig Examples for the Network Admin
DiG would use the +noall +answer flags from the ~/.digrc file even if you didn't append any flags when you ran the dig...
Read more >Dig Command in Linux (DNS Lookup)
Dig is a powerful command-line tool for querying DNS name servers. With dig you can query information about various DNS records including ...
Read more >10 Linux DIG Command Examples for DNS Lookup
Using dig command you can query DNS name servers for your DNS lookup ... we can disable all sections using +noall (this turns...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Works great. Thanks.
I have added support for
+noall +answer
in thedev
branch: https://github.com/kellyjonbrazil/jc/blob/dev/jc/parsers/dig.pyYou can place that file in your custom parser plugin directory to test it out. See https://github.com/kellyjonbrazil/jc#custom-parsers for details.
Let me know if that works for you. If so, I can package it into the next release.
Thanks!