summaryrefslogtreecommitdiff
path: root/dns-ready-check.service
diff options
context:
space:
mode:
authorAki <please@ignore.pl>2024-01-19 23:19:11 +0100
committerAki <please@ignore.pl>2024-01-19 23:19:11 +0100
commitd90b97acaff16a751d0b0153dc4a405bfceb462c (patch)
tree9f7c533e65d0964e1b9265017f87a44128a8950f /dns-ready-check.service
downloadsystemd-dns-ready-d90b97acaff16a751d0b0153dc4a405bfceb462c.zip
systemd-dns-ready-d90b97acaff16a751d0b0153dc4a405bfceb462c.tar.gz
systemd-dns-ready-d90b97acaff16a751d0b0153dc4a405bfceb462c.tar.bz2
Created target marking readiness of a net DNS resolverHEADmaster
The whole purpose is to have something that can recognize if systemd-resolved is ready, because it complained before it. I was unable to determine better method so here we are. The dependency on host(1) from bind9/named is annoying and writing a simple getaddrinfo(3) checker could be a good step forward.
Diffstat (limited to 'dns-ready-check.service')
-rw-r--r--dns-ready-check.service12
1 files changed, 12 insertions, 0 deletions
diff --git a/dns-ready-check.service b/dns-ready-check.service
new file mode 100644
index 0000000..a945739
--- /dev/null
+++ b/dns-ready-check.service
@@ -0,0 +1,12 @@
+[Unit]
+Description=Check if Domain Name System resolver is ready
+DefaultDependencies=no
+Requires=network-online.target
+After=network-online.target
+
+[Service]
+Type=oneshot
+ExecStart=/usr/bin/host example.com
+Restart=on-failure
+RestartSec=1
+StandardOutput=null