A worldwide DNS propagation checker to your CLI

0
1

You can’t choose greater than 25 subjects
Subjects should begin with a letter or quantity, can embody dashes (‘-‘) and may be as much as 35 characters lengthy.

Build Status

The actual repository is positioned here

The GitHub repository here is used for points and stars 🌟

A strong international DNS progagation checker that may output in a wide range of codecs.

The purpose of dug is to make it simple to verify the propagation of DNS information. It’s also able to offering templated output that can be utilized in scripts for issues like monitoring.

Utilization

Till theres a wiki for this, the best technique to discover dug is thru the assistance.

  • dug assist -> Get high degree assist explaining the completely different verbs
  • dug assist run or dug run --help -> Get particulars a couple of particular verb (run, which is the default)
  • dug assist replace or dug replace --help -> Get particulars concerning the replace verb

The only technique to get began is to simply run a question towards the area whose DNS information you’re updating.
For instance: dug git.kaijucode.com:
A worldwide DNS propagation checker to your CLI

You may also do difficult issues like ask for particular report varieties, get the output as json, and pipe it into different functions: dug git.kaijucode.com -q A --output-format JSON --output-template Ipaddress,metropolis,worth,responsetime | jq:
A worldwide DNS propagation checker to your CLI

Set up

Linux Deb (Debian, Ubuntu, Mint, Pop!_os)

  1. Go to the latest release and obtain the .deb bundle.
    • It ought to appear like dug..linux-x64.deb
  2. On most distros double clicking the .deb bundle will let you set up by way of a UI, alternatively it may be put in by working sudo dpkg -i ./dug..linux-x64.deb

Linux RPM (RHEL, CentOS, Fedora)

  1. Go to the latest release and obtain the .rpm bundle.
    • It ought to appear like dug..linux-x64.rpm
  2. On most distros double clicking the .deb bundle will let you set up by way of a UI, alternatively it may be put in by working rpm -i ./dug..linux-x64.deb

OSX

Not Formally Supported But

  1. Go to the latest release and obtain the osx binary.
    • It ought to appear like dug-osx-x64
  2. You must have the ability to obtain that, make is executable, and run it from the terminal. Then you may put it someplace and replace your path so you may execute it from wherever.

Home windows

Chocolatey (choco cli)

Ready on chocolatey to approve my bundle, then I can publish there so this wont require a handbook obtain. here

  1. Go to the latest release and obtain the .nupkg bundle.
    • It ought to appear like dug..nupkg
  2. Set up by working choco set up dug..nupkg

Executable

  1. Go to the latest release and obtain the .exe binary.
    • It ought to appear like dug.exe
  2. You must have the ability to obtain that and run it from the terminal. Then you may put it someplace and replace your path so you may execute it from wherever.

NPM

EXPERIMENTAL! (At present solely helps linux-x64)

  1. Run: npm -g @unfrl/dug

Idk why I needed to publish it on npm as properly, its actually not a great way to distribute a binary…

Growth

It is a .internet 5 challenge, so so long as you’ve gotten the dotnet cli, accessible here you must have the ability to do the next: dotnet construct ./cli

The challenge was developed in VSCode so the debugger profiles that I’ve used can be found for those who’re additionally utilizing VSCode.

License

The license utilized by dug, here, may be very explicitly designed to attempt to hold capitalists from benefiting from this software. This isn’t a conventional license however it is rather easy, please learn it.

Made with ❤️ by Unfrl

Article supply :=> Read More

LEAVE A REPLY

Please enter your comment!
Please enter your name here