[solved] Unbound blockiert Webseite ohne Grund/Einstellung

Started by apn, March 04, 2025, 04:54:22 PM

Previous topic - Next topic
March 04, 2025, 04:54:22 PM Last Edit: March 06, 2025, 12:29:27 PM by apn Reason: topic changed to (quasi) solved
Hi, ich komme gerade nicht weiter.

also es geht um `business.myhermes.de` (`www.myhermes.de` funktioniert)

sobald unbound aktiviert ist, kann ich die domain nicht erreichen.
ich habe sicherheitshalber alle DNSBL entfernt und deaktiviert (protokol zeigt kein laden von sperrlisten).

einstellungen sind wie folgt aktiv geblieben

unter allgemein:
- Flush DNS Cache during reload
- Register DHCP Static Mappings
unter überschreibungen:
- eine lokale domain und ein host, beide keinerlei ähnlichkeit mit myhermes.de oder hc.de hat 
unter erweitert:
- Aggressive NSEC (testweise deaktivieren hat nicht geholfen)
query forwarding und dns over tls
- eingeschaltet (aufgelistetet dns server sind: 1.1.1.3, 1.0.0.3)

unter schnittstelle-diagnose-dns abfrage bekomme ich oft unterschiedliche antworten:
A business.myhermes.de. 85432 IN CNAME gkp.prd.a0562.prd.hc.de.
        gkp.prd.a0562.prd.hc.de. 60 IN A 34.149.95.23                 1.1.1.3 53 msec
AAAA business.myhermes.de. 83940 IN CNAME gkp.prd.a0562.prd.hc.de. 1.1.1.3 33 msec
MX business.myhermes.de. 83171 IN CNAME gkp.prd.a0562.prd.hc.de. 1.1.1.3 127 msec
TXT business.myhermes.de. 83165 IN CNAME gkp.prd.a0562.prd.hc.de. 1.1.1.3 34 msec

A business.myhermes.de. 85321 IN CNAME gkp.prd.a0562.prd.hc.de.
        gkp.prd.a0562.prd.hc.de. 43 IN A 34.149.95.23                  1.1.1.3 28 msec
AAAA business.myhermes.de. 85318 IN CNAME gkp.prd.a0562.prd.hc.de.
        gkp.prd.a0562.prd.hc.de. 50 IN AAAA ::                        127.0.0.1 0 msec
TXT business.myhermes.de. 83053 IN CNAME gkp.prd.a0562.prd.hc.de. 1.0.0.3 9 msec

A business.myhermes.de. 85101 IN CNAME gkp.prd.a0562.prd.hc.de.   127.0.0.1 15 msec
AAAA business.myhermes.de. 82847 IN CNAME gkp.prd.a0562.prd.hc.de.   1.1.1.3 7 msec
MX business.myhermes.de. 82845 IN CNAME gkp.prd.a0562.prd.hc.de.   1.0.0.3 44 msec

unter berichterstattung-unbound DNS scheint es normal zu laufen..
2025-03-04 16:42:10 PC-**.**.**.com A business.myhermes.de. Pass Cache    NOERROR 4
2025-03-04 16:42:09 PC-**.**.**.com A business.myhermes.de. Pass Recursion NOERROR 5
nur wenn ich bei opnsense die dns diagnose (wie oben) mehrmals durchlaufe, kommt das
2025-03-04 16:44:49 localhost A business.myhermes.de. Pass Recursion NOERROR 5
2025-03-04 16:44:49 localhost AAAA business.myhermes.de. Pass Recursion NOERROR 60
2025-03-04 16:44:07 localhost A business.myhermes.de. Pass Recursion NOERROR 5
2025-03-04 16:44:07 localhost AAAA business.myhermes.de. Pass Cache    NOERROR 17
2025-03-04 16:44:07 localhost MX business.myhermes.de. Drop Local    SERVFAIL 0
2025-03-04 16:43:24 localhost A business.myhermes.de. Pass Recursion NOERROR 5
2025-03-04 16:43:24 localhost AAAA business.myhermes.de. Pass Recursion NOERROR 60
2025-03-04 16:43:24 localhost TXT business.myhermes.de. Drop Local    SERVFAIL 0

weiss jemand rat? ich dachte ich frag mal hier, nicht dass das ein unbound problem ist.
danke.

bin etwas weiter

hab je ein ping an `business.myhermes.de` geschickt, während ich den externe dns server jedesmal gewechselt hab.
unbound protokol hat dann aufschluss gegeben:

1.1.1.3 und 1.0.0.3 filtern raus, während 1.1.1.1 und 8.8.8.8 antworten.
übergehe ich lokal den opnsense als dns server und setzte direkt auf einen der vier, funktionieren alle.

wieso antworten 1.1.1.3 und 1.0.0.3 mit 0.0.0.0 wenn unbound fragt, aber beim client antworten sie mit der richtige ip (34.149.95.23)?
weiss dazu jemand was, oder kann es verifizieren?
danke



hier noch die logs:

mit 1.0.0.3
2025-03-05T13:14:42    Informational    unbound    [23866:0] info: finishing processing for business.myhermes.de. A IN   
2025-03-05T13:14:42    Informational    unbound    [23866:0] info: query response was nodata ANSWER   
2025-03-05T13:14:42    Informational    unbound    [23866:0] info: reply from <.> 1.0.0.3#53   
2025-03-05T13:14:42    Informational    unbound    [23866:0] info: response for business.myhermes.de. A IN   
2025-03-05T13:14:42    Debug    unbound    [23866:0] debug: sanitize: removing public name with private address <gkp.prd.a0562.prd.hc.de.> 0.0.0.0#53   
2025-03-05T13:14:42    Informational    unbound    [23866:0] info: iterator operate: chased to gkp.prd.a0562.prd.hc.de. A IN   
2025-03-05T13:14:42    Informational    unbound    [23866:0] info: iterator operate: query business.myhermes.de. A IN   
2025-03-05T13:14:42    Debug    unbound    [23866:0] debug: iterator[module 1] operate: extstate:module_wait_reply event:module_event_reply   
2025-03-05T13:14:42    Debug    unbound    [23866:0] debug: cache memory msg=302347 rrset=301303 infra=11659 val=0   
2025-03-05T13:14:42    Debug    unbound    [23866:0] debug: sending to target: <.> 1.0.0.3#53   
2025-03-05T13:14:42    Informational    unbound    [23866:0] info: sending query: gkp.prd.a0562.prd.hc.de. A IN   
2025-03-05T13:14:42    Informational    unbound    [23866:0] info: processQueryTargets: business.myhermes.de. A IN   
2025-03-05T13:14:42    Informational    unbound    [23866:0] info: reply from <.> 1.0.0.3#53   
2025-03-05T13:14:42    Informational    unbound    [23866:0] info: response for business.myhermes.de. A IN   
2025-03-05T13:14:42    Debug    unbound    [23866:0] debug: sanitize: removing public name with private address <gkp.prd.a0562.prd.hc.de.> 0.0.0.0#53   
2025-03-05T13:14:42    Informational    unbound    [23866:0] info: iterator operate: chased to gkp.prd.a0562.prd.hc.de. A IN   
2025-03-05T13:14:42    Informational    unbound    [23866:0] info: iterator operate: query business.myhermes.de. A IN   
2025-03-05T13:14:42    Debug    unbound    [23866:0] debug: iterator[module 1] operate: extstate:module_wait_reply event:module_event_reply   
2025-03-05T13:14:42    Debug    unbound    [23866:0] debug: cache memory msg=302347 rrset=301303 infra=11659 val=0   
2025-03-05T13:14:42    Debug    unbound    [23866:0] debug: sending to target: <.> 1.0.0.3#53   
2025-03-05T13:14:42    Informational    unbound    [23866:0] info: sending query: gkp.prd.a0562.prd.hc.de. A IN   
2025-03-05T13:14:42    Informational    unbound    [23866:0] info: processQueryTargets: business.myhermes.de. A IN   
2025-03-05T13:14:42    Informational    unbound    [23866:0] info: resolving business.myhermes.de. A IN   
2025-03-05T13:14:42    Informational    unbound    [23866:0] info: resolving business.myhermes.de. A IN   
2025-03-05T13:14:42    Debug    unbound    [23866:0] debug: iterator[module 1] operate: extstate:module_state_initial event:module_event_pass   
2025-03-05T13:14:42    Informational    unbound    [23866:0] info: 192.168.168.168 business.myhermes.de. A IN
mit 1.1.1.3
2025-03-05T13:17:52    Informational    unbound    [61334:0] info: finishing processing for business.myhermes.de. A IN   
2025-03-05T13:17:52    Informational    unbound    [61334:0] info: query response was nodata ANSWER   
2025-03-05T13:17:52    Informational    unbound    [61334:0] info: reply from <.> 1.1.1.3#53   
2025-03-05T13:17:52    Informational    unbound    [61334:0] info: response for business.myhermes.de. A IN   
2025-03-05T13:17:52    Debug    unbound    [61334:0] debug: sanitize: removing public name with private address <gkp.prd.a0562.prd.hc.de.> 0.0.0.0#53   
2025-03-05T13:17:52    Informational    unbound    [61334:0] info: iterator operate: chased to gkp.prd.a0562.prd.hc.de. A IN   
2025-03-05T13:17:52    Informational    unbound    [61334:0] info: iterator operate: query business.myhermes.de. A IN   
2025-03-05T13:17:52    Debug    unbound    [61334:0] debug: iterator[module 1] operate: extstate:module_wait_reply event:module_event_reply   
2025-03-05T13:17:52    Debug    unbound    [61334:0] debug: cache memory msg=76839 rrset=79735 infra=9545 val=0   
2025-03-05T13:17:52    Debug    unbound    [61334:0] debug: sending to target: <.> 1.1.1.3#53   
2025-03-05T13:17:52    Informational    unbound    [61334:0] info: sending query: gkp.prd.a0562.prd.hc.de. A IN   
2025-03-05T13:17:52    Informational    unbound    [61334:0] info: processQueryTargets: business.myhermes.de. A IN   
2025-03-05T13:17:52    Informational    unbound    [61334:0] info: reply from <.> 1.1.1.3#53   
2025-03-05T13:17:52    Informational    unbound    [61334:0] info: response for business.myhermes.de. A IN   
2025-03-05T13:17:52    Debug    unbound    [61334:0] debug: sanitize: removing public name with private address <gkp.prd.a0562.prd.hc.de.> 0.0.0.0#53   
2025-03-05T13:17:52    Informational    unbound    [61334:0] info: iterator operate: chased to gkp.prd.a0562.prd.hc.de. A IN   
2025-03-05T13:17:52    Informational    unbound    [61334:0] info: iterator operate: query business.myhermes.de. A IN   
2025-03-05T13:17:52    Debug    unbound    [61334:0] debug: iterator[module 1] operate: extstate:module_wait_reply event:module_event_reply   
2025-03-05T13:17:52    Debug    unbound    [61334:0] debug: cache memory msg=76839 rrset=79735 infra=9545 val=0   
2025-03-05T13:17:52    Debug    unbound    [61334:0] debug: sending to target: <.> 1.1.1.3#53   
2025-03-05T13:17:52    Informational    unbound    [61334:0] info: sending query: gkp.prd.a0562.prd.hc.de. A IN   
2025-03-05T13:17:52    Informational    unbound    [61334:0] info: processQueryTargets: business.myhermes.de. A IN   
2025-03-05T13:17:52    Informational    unbound    [61334:0] info: resolving business.myhermes.de. A IN   
2025-03-05T13:17:52    Informational    unbound    [61334:0] info: resolving business.myhermes.de. A IN   
2025-03-05T13:17:52    Debug    unbound    [61334:0] debug: iterator[module 1] operate: extstate:module_state_initial event:module_event_pass   
2025-03-05T13:17:52    Informational    unbound    [61334:0] info: 192.168.168.168 business.myhermes.de. A IN
mit 8.8.8.8
2025-03-05T13:21:00    Informational    unbound    [45214:1] info: finishing processing for business.myhermes.de. A IN   
2025-03-05T13:21:00    Informational    unbound    [45214:1] info: query response was ANSWER   
2025-03-05T13:21:00    Informational    unbound    [45214:1] info: reply from <.> 8.8.8.8#53   
2025-03-05T13:21:00    Informational    unbound    [45214:1] info: response for business.myhermes.de. A IN   
2025-03-05T13:21:00    Informational    unbound    [45214:1] info: iterator operate: chased to gkp.prd.a0562.prd.hc.de. A IN   
2025-03-05T13:21:00    Informational    unbound    [45214:1] info: iterator operate: query business.myhermes.de. A IN   
2025-03-05T13:21:00    Debug    unbound    [45214:1] debug: iterator[module 1] operate: extstate:module_wait_reply event:module_event_reply   
2025-03-05T13:21:00    Debug    unbound    [45214:1] debug: cache memory msg=71353 rrset=74909 infra=9097 val=0   
2025-03-05T13:21:00    Informational    unbound    [45214:1] info: 192.168.168.168 business.myhermes.de. A IN   
2025-03-05T13:21:00    Debug    unbound    [45214:1] debug: cache memory msg=71353 rrset=74909 infra=9097 val=0   
2025-03-05T13:21:00    Debug    unbound    [45214:1] debug: sending to target: <.> 8.8.8.8#53   
2025-03-05T13:21:00    Informational    unbound    [45214:1] info: sending query: gkp.prd.a0562.prd.hc.de. A IN   
2025-03-05T13:21:00    Informational    unbound    [45214:1] info: processQueryTargets: business.myhermes.de. A IN   
2025-03-05T13:21:00    Informational    unbound    [45214:1] info: resolving business.myhermes.de. A IN   
2025-03-05T13:21:00    Informational    unbound    [45214:1] info: query response was CNAME   
2025-03-05T13:21:00    Informational    unbound    [45214:1] info: reply from <.> 8.8.8.8#53   
2025-03-05T13:21:00    Informational    unbound    [45214:1] info: response for business.myhermes.de. A IN   
2025-03-05T13:21:00    Informational    unbound    [45214:1] info: sanitize: removing extraneous answer RRset: gkp.prd.a0562.prd.hc.de. A IN   
2025-03-05T13:21:00    Informational    unbound    [45214:1] info: iterator operate: query business.myhermes.de. A IN   
2025-03-05T13:21:00    Debug    unbound    [45214:1] debug: iterator[module 1] operate: extstate:module_wait_reply event:module_event_reply   
2025-03-05T13:21:00    Debug    unbound    [45214:1] debug: cache memory msg=71353 rrset=74684 infra=9097 val=0   
2025-03-05T13:21:00    Debug    unbound    [45214:1] debug: sending to target: <.> 8.8.8.8#53   
2025-03-05T13:21:00    Informational    unbound    [45214:1] info: sending query: business.myhermes.de. A IN   
2025-03-05T13:21:00    Informational    unbound    [45214:1] info: processQueryTargets: business.myhermes.de. A IN   
2025-03-05T13:21:00    Informational    unbound    [45214:1] info: resolving business.myhermes.de. A IN   
2025-03-05T13:21:00    Debug    unbound    [45214:1] debug: iterator[module 1] operate: extstate:module_state_initial event:module_event_pass   
2025-03-05T13:21:00    Informational    unbound    [45214:1] info: 192.168.168.168 business.myhermes.de. A IN
mit 1.1.1.1
2025-03-05T13:29:03    Informational    unbound    [52995:1] info: finishing processing for business.myhermes.de. A IN   
2025-03-05T13:29:03    Informational    unbound    [52995:1] info: query response was ANSWER   
2025-03-05T13:29:03    Informational    unbound    [52995:1] info: reply from <.> 1.1.1.1#53   
2025-03-05T13:29:03    Informational    unbound    [52995:1] info: response for business.myhermes.de. A IN   
2025-03-05T13:29:03    Informational    unbound    [52995:1] info: iterator operate: chased to gkp.prd.a0562.prd.hc.de. A IN   
2025-03-05T13:29:03    Informational    unbound    [52995:1] info: iterator operate: query business.myhermes.de. A IN   
2025-03-05T13:29:03    Debug    unbound    [52995:1] debug: iterator[module 1] operate: extstate:module_wait_reply event:module_event_reply   
2025-03-05T13:29:03    Debug    unbound    [52995:1] debug: cache memory msg=71486 rrset=73732 infra=9545 val=0   
2025-03-05T13:29:03    Informational    unbound    [52995:1] info: 192.168.168.168 business.myhermes.de. A IN   
2025-03-05T13:29:03    Debug    unbound    [52995:1] debug: cache memory msg=71486 rrset=73732 infra=9545 val=0   
2025-03-05T13:29:03    Debug    unbound    [52995:1] debug: sending to target: <.> 1.1.1.1#53   
2025-03-05T13:29:03    Informational    unbound    [52995:1] info: sending query: gkp.prd.a0562.prd.hc.de. A IN   
2025-03-05T13:29:03    Informational    unbound    [52995:1] info: processQueryTargets: business.myhermes.de. A IN   
2025-03-05T13:29:03    Informational    unbound    [52995:1] info: resolving business.myhermes.de. A IN   
2025-03-05T13:29:03    Informational    unbound    [52995:1] info: query response was CNAME   
2025-03-05T13:29:03    Informational    unbound    [52995:1] info: reply from <.> 1.1.1.1#53   
2025-03-05T13:29:03    Informational    unbound    [52995:1] info: response for business.myhermes.de. A IN   
2025-03-05T13:29:03    Informational    unbound    [52995:1] info: sanitize: removing extraneous answer RRset: gkp.prd.a0562.prd.hc.de. A IN   
2025-03-05T13:29:03    Informational    unbound    [52995:1] info: iterator operate: query business.myhermes.de. A IN   
2025-03-05T13:29:03    Debug    unbound    [52995:1] debug: iterator[module 1] operate: extstate:module_wait_reply event:module_event_reply   
2025-03-05T13:29:03    Debug    unbound    [52995:1] debug: cache memory msg=71486 rrset=73507 infra=9545 val=0   
2025-03-05T13:29:03    Debug    unbound    [52995:1] debug: sending to target: <.> 1.1.1.1#53   
2025-03-05T13:29:03    Informational    unbound    [52995:1] info: sending query: business.myhermes.de. A IN   
2025-03-05T13:29:03    Informational    unbound    [52995:1] info: processQueryTargets: business.myhermes.de. A IN   
2025-03-05T13:29:03    Informational    unbound    [52995:1] info: resolving business.myhermes.de. A IN   
2025-03-05T13:29:03    Debug    unbound    [52995:1] debug: iterator[module 1] operate: extstate:module_state_initial event:module_event_pass   
2025-03-05T13:29:03    Informational    unbound    [52995:1] info: 192.168.168.168 business.myhermes.de. A IN


Laut dem Log
Quote2025-03-05T13:14:42    Debug    unbound    [23866:0] debug: sanitize: removing public name with private address <gkp.prd.a0562.prd.hc.de.> 0.0.0.0#53   
bekommt Unbound eine private IP zurück, und diese gibt er nicht freiwillig weiter.

Wenn ich 1.1.1.3 direkt abfrage (nicht über Unbound), bekomme ich auch 0.0.0.0 zurück. Von 1.0.0.3 bekomme ich aber 34.149.95.23.

Woher die Antwort tatsächlich kommt, lässt sich schwer feststellen, wenn du unverschlüsselte DNS Uplooks nutzt. Die Anfragen könnte bspw. der ISP einfach auf einen anderen Server umleiten.

Ich bekomme von diesen Cloudflare-Servern auch nur komplett blödsinnige Ergebnisse:

# nslookup business.myhermes.de 1.1.1.3
Server:         1.1.1.3
Address:        1.1.1.3#53

Non-authoritative answer:
business.myhermes.de    canonical name = gkp.prd.a0562.prd.hc.de.
Name:   gkp.prd.a0562.prd.hc.de
Address: 34.149.95.23
Name:   gkp.prd.a0562.prd.hc.de
Address: ::

Diese Server sind offenbar funktional kaputt, denn die Antwort "::" würde zu einer Blockade führen, wenn man (per Default) zuerst IPv6 verwendet.
Bezeichnenderweise liefert die "nicht-filternde" Version 1.1.1.1 nur eine IPv4, was korrekt ist, denn für den Alias existiert kein IPv6-Eintrag.
Intel N100, 4 x I226-V, 16 GByte, 256 GByte NVME, ZTE F6005

1100 down / 800 up, Bufferbloat A+

danke viragomann und meyergru.

war doch keine gute idee vorgefilterte dns server zu nutzen, bin wieder auf 1.1.1.1 und DNSBLs aktiviert.

obwohl es in der konsole keine probleme gibt und ich immer die gleichen antworten bekomme, egal welchen dns server ich wähle.


hier ein finaller lookup vergleich zwischen client pc und opnsense (vorsicht lang.. leider gibts kein [spoiler][/spoiler] tag)

- 5 gesetzte server: ohne, 8.8.8.8, 1.1.1.1, 1.1.1.3, 1.0.0.3
    da bei allen immer die gleiche antworten kamen, nur mit 1.1.1.3
- 3 gesetzte query types: ohne, A und AAAA
= keine Fehler und keine ipv6 ip


## opnsense
# --------------------------------------------------------------------------------
# -------------------- drill business.myhermes.de @1.1.1.1
;; ->>HEADER<<- opcode: QUERY, rcode: NOERROR, id: 34853
;; flags: qr rd ra ; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;; business.myhermes.de.        IN      A

;; ANSWER SECTION:
business.myhermes.de.   82904   IN      CNAME   gkp.prd.a0562.prd.hc.de.
gkp.prd.a0562.prd.hc.de.        60      IN      A       34.149.95.23

;; AUTHORITY SECTION:

;; ADDITIONAL SECTION:

;; Query time: 32 msec
;; SERVER: 1.1.1.1
;; WHEN: Thu Mar  6 11:37:28 2025
;; MSG SIZE  rcvd: 89


# --------------------------------------------------------------------------------
# -------------------- drill business.myhermes.de @1.1.1.3 A
;; ->>HEADER<<- opcode: QUERY, rcode: NOERROR, id: 59864
;; flags: qr rd ra ; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;; business.myhermes.de.        IN      A

;; ANSWER SECTION:
business.myhermes.de.   83785   IN      CNAME   gkp.prd.a0562.prd.hc.de.
gkp.prd.a0562.prd.hc.de.        60      IN      A       34.149.95.23

;; AUTHORITY SECTION:

;; ADDITIONAL SECTION:

;; Query time: 33 msec
;; SERVER: 1.1.1.3
;; WHEN: Thu Mar  6 11:22:45 2025
;; MSG SIZE  rcvd: 89

# --------------------------------------------------------------------------------
# -------------------- drill business.myhermes.de @1.1.1.3 AAAA
;; ->>HEADER<<- opcode: QUERY, rcode: NOERROR, id: 53527
;; flags: qr rd ra ; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;; business.myhermes.de.        IN      AAAA

;; ANSWER SECTION:
business.myhermes.de.   77014   IN      CNAME   gkp.prd.a0562.prd.hc.de.

;; AUTHORITY SECTION:
a0562.prd.hc.de.        188     IN      SOA     ns-cloud-a1.googledomains.com. cloud-dns-hostmaster.google.com. 1 21600 3600 259200 300

;; ADDITIONAL SECTION:

;; Query time: 7 msec
;; SERVER: 1.1.1.3
;; WHEN: Thu Mar  6 11:22:48 2025
;; MSG SIZE  rcvd: 166


# --------------------------------------------------------------------------------
# -------------------- host business.myhermes.de 1.1.1.3
Using domain server:
Name: 1.1.1.3
Address: 1.1.1.3#53
Aliases:

business.myhermes.de is an alias for gkp.prd.a0562.prd.hc.de.
gkp.prd.a0562.prd.hc.de has address 34.149.95.23

# --------------------------------------------------------------------------------
# -------------------- host -t A business.myhermes.de 1.1.1.3
Using domain server:
Name: 1.1.1.3
Address: 1.1.1.3#53
Aliases:

business.myhermes.de is an alias for gkp.prd.a0562.prd.hc.de.
gkp.prd.a0562.prd.hc.de has address 34.149.95.23

# --------------------------------------------------------------------------------
# -------------------- host -t AAAA business.myhermes.de 1.1.1.3
Using domain server:
Name: 1.1.1.3
Address: 1.1.1.3#53
Aliases:

business.myhermes.de is an alias for gkp.prd.a0562.prd.hc.de.

## client
> set debug=true
> --------------------------------------------------------------------------------
> -------------------- business.myhermes.de. 1.1.1.3
Server:  [1.1.1.3]
Address:  1.1.1.3

------------
Got answer:
    HEADER:
        opcode = QUERY, id = 2, rcode = NOERROR
        header flags:  response, want recursion, recursion avail.
        questions = 1,  answers = 2,  authority records = 0,  additional = 0

    QUESTIONS:
        business.myhermes.de, type = A, class = IN
    ANSWERS:
    ->  business.myhermes.de
        canonical name = gkp.prd.a0562.prd.hc.de
        ttl = 84226 (23 hours 23 mins 46 secs)
    ->  gkp.prd.a0562.prd.hc.de
        internet address = 34.149.95.23
        ttl = 60 (1 min)

------------
Nicht autorisierende Antwort:
------------
Got answer:
    HEADER:
        opcode = QUERY, id = 3, rcode = NOERROR
        header flags:  response, want recursion, recursion avail.
        questions = 1,  answers = 1,  authority records = 1,  additional = 0

    QUESTIONS:
        business.myhermes.de, type = AAAA, class = IN
    ANSWERS:
    ->  business.myhermes.de
        canonical name = gkp.prd.a0562.prd.hc.de
        ttl = 77459 (21 hours 30 mins 59 secs)
    AUTHORITY RECORDS:
    ->  a0562.prd.hc.de
        ttl = 300 (5 mins)
        primary name server = ns-cloud-a1.googledomains.com
        responsible mail addr = cloud-dns-hostmaster.google.com
        serial  = 1
        refresh = 21600 (6 hours)
        retry   = 3600 (1 hour)
        expire  = 259200 (3 days)
        default TTL = 300 (5 mins)

------------
Name:    gkp.prd.a0562.prd.hc.de
Address:  34.149.95.23
Aliases:  business.myhermes.de

> --------------------------------------------------------------------------------
> -------------------- set type=A
> -------------------- business.myhermes.de. 1.1.1.3
Server:  [1.1.1.3]
Address:  1.1.1.3

------------
Got answer:
    HEADER:
        opcode = QUERY, id = 4, rcode = NOERROR
        header flags:  response, want recursion, recursion avail.
        questions = 1,  answers = 2,  authority records = 0,  additional = 0

    QUESTIONS:
        business.myhermes.de, type = A, class = IN
    ANSWERS:
    ->  business.myhermes.de
        canonical name = gkp.prd.a0562.prd.hc.de
        ttl = 84217 (23 hours 23 mins 37 secs)
    ->  gkp.prd.a0562.prd.hc.de
        internet address = 34.149.95.23
        ttl = 51 (51 secs)

------------
Nicht autorisierende Antwort:
Name:    gkp.prd.a0562.prd.hc.de
Address:  34.149.95.23
Aliases:  business.myhermes.de

> --------------------------------------------------------------------------------
> -------------------- set type=AAAA
> -------------------- business.myhermes.de. 1.1.1.3
Server:  [1.1.1.3]
Address:  1.1.1.3

------------
Got answer:
    HEADER:
        opcode = QUERY, id = 5, rcode = NOERROR
        header flags:  response, want recursion, recursion avail.
        questions = 1,  answers = 1,  authority records = 1,  additional = 0

    QUESTIONS:
        business.myhermes.de, type = AAAA, class = IN
    ANSWERS:
    ->  business.myhermes.de
        canonical name = gkp.prd.a0562.prd.hc.de
        ttl = 85216 (23 hours 40 mins 16 secs)
    AUTHORITY RECORDS:
    ->  a0562.prd.hc.de
        ttl = 300 (5 mins)
        primary name server = ns-cloud-a1.googledomains.com
        responsible mail addr = cloud-dns-hostmaster.google.com
        serial  = 1
        refresh = 21600 (6 hours)
        retry   = 3600 (1 hour)
        expire  = 259200 (3 days)
        default TTL = 300 (5 mins)

------------
Nicht autorisierende Antwort:
Name:    business.myhermes.de