uWSGI-local-DNS-resolver (from now on uWSGI-DNS) is a DNS server that resolves to localhost each request directed to a uWSGI-subscribed domain.
Our main intent is to let users transparently connect to their local development instances handled through a uWSGI HTTP subscription server.
uWSGI-DNS is still a work in progress. As a consequence, its APIs could be subject to changes.
- Python 2 & Python 3 compatibility.
- UNIX/Linux systems compatibility.
- Automatic domain refresh on new uWSGI subscriptions.
- Failed nodes detection and handling.
You can install uwsgi-dns through PIP with:
$ pip install uwsgidns # you could need to use sudo here, or -UAlternatively, you can clone the repository manually:
$ git clone https://github.com/20tab/uwsgi-local-dns-resolver.git
$ cd uwsgi-local-dns-resolver
$ python setup.py install # you could need sudo hereAnd if you want, you can test the server with:
$ sudo uwsgidns # we need sudo to bind on reserved port 53Once started, you should have a DNS server running on localhost:53.
Note: installing uWSGI-DNS inside a virtualenv is obviously possible, but you should use particular care while integrating it into uWSGI configuration files.
$ uwsgidns -h
usage: uwsgidns [-h] [-l {CRITICAL,ERROR,WARNING,INFO,DEBUG,NOTSET}] [-p]
[-u upstream DNS server URI] [-s uwsgi-HTTP-stats-URI]
DNS server that resolves to localhost uWSGI HTTP subscribed domains.
optional arguments:
-h, --help show this help message and exit
-l {CRITICAL,ERROR,WARNING,INFO,DEBUG,NOTSET}, --logging {CRITICAL,ERROR,WARNING,INFO,DEBUG,NOTSET}
set the logging level
-p, --proxy proxy other requests to upstream DNS server
(--upstream)
-u upstream DNS server URI, --upstream upstream DNS server URI
the URI to the upstream DNS server (with --proxy),
defaults to 8.8.8.8:53
-s uwsgi-HTTP-stats-URI, --stats uwsgi-HTTP-stats-URI
the URI (remote:port) to the uWSGI HTTP subscription
stats serveruWSGI-DNS can act as a DNS proxy (-p), forwarding each non-local request to the upstream server specified with the -u flag;
otherwise, it simply drops such requests and let the OS fallback DNS server handle them.
Setting the -s will let uWSGI-DNS poll the uWSGI subscription server periodically.
In this way uWSGI-DNS will notice failed/disappeared HTTP nodes and will remove them from the local domains.
The integration with the uWSGI emperor is simple and straightforward. We assume you use the uWSGI HTTP subscription server. To integrate uWSGI-DNS you can edit the configuration file of your emperor/subscription server as follows:
; uWSGI subscription server - ini configuration file
http = :80
http-subscription-server = 127.0.0.1:5005
http-stats-server = 127.0.0.1:5004
; resubscribe let uWSGI-DNS know about new HTTP nodes
http-resubscribe = 127.0.0.1:9696
; launch the uWSGI-DNS with the HTTP subscription server
; you can tweak the command line arguments and the path here
attach-daemon = uwsgidnsAnytime you'll launch the subscription system, the uWSGI-DNS server will launch with it.
Please note that in the following section we provide some more OS-specific examples.
TODO: other OSs integration.
The OS integration largely varies with each platforms. We provide here just a few examples, adapt them to your needs.
You can use LaunchD to automatically launch a uWSGI emperor instance on startup.
To do so, create the file it.unbit.uwsgi.emperor.plist in the /Library/LaunchDaemons/ directory and make sure it has the following content.
The same example can also be found in this repository.
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>RunAtLoad</key>
<true/>
<key>Disabled</key>
<false/>
<key>KeepAlive</key>
<dict>
<key>SuccessfulExit</key>
<false/>
</dict>
<key>Label</key>
<string>it.unbit.uwsgi.emperor</string>
<key>ProgramArguments</key>
<array>
<string>/usr/local/bin/uwsgi</string>
<string>--master</string>
<string>--die-on-term</string>
<!-- You could either need or not some more plugins,
if you're using a monolitic uWSGI build -->
<string>--plugin</string>
<string>syslog</string>
<string>--logger</string>
<string>syslog:</string>
<string>--emperor</string>
<string>/Users/*/*/vassals/*.ini</string>
<string>--emperor</string>
<string>/Users/*/vassals/*.ini</string>
<string>--emperor-tyrant</string>
<string>--http</string>
<string>:80</string>
<string>--http-subscription-server</string>
<string>127.0.0.1:5005</string>
<string>--http-resubscribe</string>
<string>127.0.0.1:9696</string>
<string>--http-stats-server</string>
<string>127.0.0.1:5004</string>
<string>--emperor-stats-server</string>
<string>127.0.0.1:5000</string>
<string>--attach-daemon</string>
<string>/usr/local/bin/uwsgidns -p</string>
</array>
</dict>
</plist>Put the vassals configuration files in your home folder and then start the uWSGI emperor with the command:
$ sudo launchctl load /Library/LaunchDaemons/it.unbit.uwsgi.emperor.plistYou can finally edit your connection parameters and set the custom DNS server pointing to 127.0.0.1.
The DNS resolver will try to solve local requests and then will proxy to upstream the others.
The default upstream is 8.8.8.8:53 and you can customize it with the -u UPSTREAM_ADDRESS:PORT flag.
Bonus: before editing your network settings, you can create a new Network Location to be specifically used while developing and edit its DNS settings.
TODO: add tests.