devdns
It does one thing: maps a custom TLD (like .dev) to an IP (like 127.0.0.1).
## Use
sudo devdns sudo devdns test sudo devdns dev 192.168.1.110
By default devdns maps the dev TLD to 127.0.0.1. This is probably all most people will need. The first argument, if specified will set a custom TLD like test (www.myserver.test). The second argument allows you to specify an IP address, for example the address of a server on your LAN.
You need to run it as root because it uses port 53, the standard DNS port. Also you’ll want to add localhost (127.0.0.1) to the top of your DNS server list. I recommend adding google’s DNS addresses (8.8.8.8 and 8.8.4.4) as backup servers.

## Credits
Much of this code was adopted from [minidns](https://code.google.com/p/minidns/) which itself borrowed heavily from [Francisco’s recipe](http://code.activestate.com/recipes/491264-mini-fake-dns-server/).
Metadata
Release files for devdns 0.1.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| devdns-0.1.2.tar.gz | 2.4 kB | Without provenance | Details for devdns-0.1.2.tar.gz |
Release files / devdns-0.1.2.tar.gz
| Download URL | devdns-0.1.2.tar.gz |
|---|---|
| Size | 2.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
80ee76e8a262777c39e379330ef3032c33cbc3fef90c769d700eaa392d5ef434
|
|
BLAKE2b-256 checksum How to use checksums |
05d56f3fb3102e493252919299299298e4deb048ae1b38235adc64b888461d6b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for devdns 0.1.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.