DNS over Discord
A 220.127.116.11 DNS resolver built in Go for Discord
I'm hosting a copy of this bot myself and you can invite it to your Discord server using this link:
This assumes you already have a working Go environment setup, with DiscordGo (github.com/bwmarrin/discordgo) and tablewriter (github.com/olekukonko/tablewriter) installed correctly on your system.
From within the 18.104.22.168-Discord project folder, run the below command to compile the Discord bot.
You can start the Discord bot by running the following, where
<token> is your Discord Bot token and
your Discord user ID to be the bot admin.
./22.214.171.124-Discord -t <token> -a <user-id>
The bot can be used in Discord by mentioning the bot and then providing a domain name to look up using 126.96.36.199. By default, if only a domain name is provided, the bot will lookup all supported record types and report them all. However, you can also provide a list of record types (space separated) after the domain name to select which to lookup.
Mentioning the bot in Discord with no additional arguments will generate the usage message as follows:
Usage: @188.8.131.52 <domain> [...types] Examples: @184.108.40.206 mattcowley.co.uk @220.127.116.11 mattcowley.co.uk A AAAA Types: If not provided, the default type of "A" will be used You can provide a type of "*" to lookup all supported types Supported types: A NS CNAME MX TXT AAAA SRV CAA Invite: https://bit.ly/1111-Discord Open-source: https://github.com/MattIPv4/18.104.22.168-Discord
As the bot admin (see the
-a argument above), this also enables two extra commands I find useful for production
deployment. These are the
pull command than runs
git pull in the bot directory to fetch updates from Github, as
exit which cleanly terminates the bot process.
Supported Record Types
The latest supported record types can be found at the top of dns.go in the types map.
Contributions are always welcome to this project!
Take a look at any existing issues on this repository for starting places to help contribute towards, or simply create your own new contribution to the project.
Please make sure to follow the existing standards within the project such as code styles, naming conventions and commenting/documentation.
When you are ready, simply create a pull request for your contribution and I will review it whenever I can!
Discussion, Support and Issues
Need support with this project, have found an issue or want to chat with others about contributing to the project?
Please check the project's issues page first for support & bugs!
Not found what you need here?
- If you have an issue, please create a GitHub issue here to report the situation, include as much detail as you can!
- or, You can join our Slack workspace to discuss any issue, to get support for the project or to chat with contributors and myself: