Git Product home page Git Product logo

dns-lookup's Introduction

dns-lookup's People

Contributors

jvns avatar nielsbom avatar veegishx avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

dns-lookup's Issues

Release Go Program as a CLI?

Hi @jvns,

Thank you for providing a great tool, love it! Thank you for always providing such great material on your blog as well!

If I may, are there any plans to release the DNS program that makes the queries as a CLI tool in the future? Definitely could use this for getting all the record types which is currently not something we can do with dig in most cases. If you know of any other programs that can do this, please let me know!

Thank you again!

Easier checking of DMARC records?

DMARC records often (always?) reside on a subdomain like _dmarc.example.com.
Using this dns-lookup we can look up the DMARC record: https://dns-lookup.jvns.ca/#_dmarc.example.com|txt
But it's a bit cumbersome having to do that for one specific record.

Would it be possible to extend this tool to also check the TXT record for the _dmarc subdomain automatically?

I've tried to run this project locally but I'm not familiar with golang or the ecosystem so I got stuck :-)

No support for IPv6

The DNS tracer does not query IPv6 DNS servers.

The IPv6 addresses of the root nameservers are not used nor shown (all of them have IPv6).

Although the IPv6 addresses of intermediate nameservers are shown in the additional section, they are not queried. Requests are only sent to the legacy addresses. If a domain is IPv6-only then the trace fails entirely.

The tracer only queries for an A record, it does not allow setting any other types.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.