v-m: Update jobs for new Loki server

*loki1.pyrocufflink.blue* is a regular Fedora machine, a member of the
AD domain, and managed by Ansible.  Thus, it does not need to be
explicitly listed as a scrape target.

For scraping metrics from Loki itself, I've changed the job to use
DNS-SD because it seems like `vmagent` does _not_ re-resolve host names
from static configuration.

victoria-metrics/scrape.yml

@@ -76,7 +76,6 @@ scrape_configs:
   static_configs:
   - targets:
     - gw1.pyrocufflink.blue
-    - loki0.pyrocufflink.blue
     - nut0.pyrocufflink.blue
     - nvr2.pyrocufflink.blue
     - unifi3.pyrocufflink.blue
@@ -251,7 +250,6 @@ scrape_configs:
   metrics_path: /bridge?selector=zincati
   static_configs:
   - targets:
-    - loki0.pyrocufflink.blue
     - nut0.pyrocufflink.blue
     - unifi3.pyrocufflink.blue
   kubernetes_sd_configs:
@@ -279,14 +277,21 @@ scrape_configs:
   scheme: https
   tls_config:
     ca_file: /run/dch-ca/dch-root-ca.crt
-  static_configs:
+  dns_sd_configs:
-  - targets:
+  - names:
     - loki.pyrocufflink.blue
+    type: A
+    port: 443
+  relabel_configs:
+  - source_labels: [__meta_dns_name, __meta_dns_srv_record_port]
+    separator: ':'
+    target_label: __address__
+  - source_labels: [__address__]
+    target_label: instance
 
 - job_name: promtail
   static_configs:
   - targets:
-    - loki0.pyrocufflink.blue
     - nut0.pyrocufflink.blue
     - nvr2.pyrocufflink.blue
     - unifi3.pyrocufflink.blue