:: Re: [DNG] [OT] problem with quemu d…
Forside
Slet denne besked
Besvar denne besked
Skribent: Steve Litt
Dato:  
Til: dng
Emne: Re: [DNG] [OT] problem with quemu dnsmasq vs unbound
al3xu5 via Dng said on Fri, 21 Jan 2022 12:55:04 +0100

>Please, I would ask for your advices about the situation described
>below.
>
>Excuse me if this could be OT in this list.
>
>On my chimaera system, I am using unbound as a local recursive caching
>DNS (not authoritative) server. More, I have uninstalled dnsmasq, as I
>do not need it and want to avoid it interfering with unbound.
>
>But QEMU/KVM requires dnsmasq to start the 'default' virt network.


Here's a data point. My Void Linux physical machine Daily Driver Desktop
(DDD) has both unbound and dnsmasq installed, and if there's any
interference, I'm not aware of it.

=====================================================
[slitt@mydesk nq]$ time dig @192.168.0.102 masterblaster.com

; <<>> DiG 9.16.22 <<>> @192.168.0.102 masterblaster.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 25686
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;masterblaster.com.        IN    A


;; ANSWER SECTION:
masterblaster.com.    3600    IN    A    52.128.23.153


;; Query time: 228 msec
;; SERVER: 192.168.0.102#53(192.168.0.102)
;; WHEN: Fri Jan 21 13:48:40 EST 2022
;; MSG SIZE rcvd: 62


real    0m0.293s
user    0m0.005s
sys    0m0.008s
[slitt@mydesk nq]$ time dig @192.168.0.102 masterblaster.com


; <<>> DiG 9.16.22 <<>> @192.168.0.102 masterblaster.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 4685
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;masterblaster.com.        IN    A


;; ANSWER SECTION:
masterblaster.com.    3590    IN    A    52.128.23.153


;; Query time: 0 msec
;; SERVER: 192.168.0.102#53(192.168.0.102)
;; WHEN: Fri Jan 21 13:48:50 EST 2022
;; MSG SIZE rcvd: 62


real    0m0.019s
user    0m0.004s
sys    0m0.005s
[slitt@mydesk nq]$ 
=====================================================


As you can see, it took 0.3 seconds to look up a domain via recursion.
It took 0.02 seconds to look it up in the cache. These timings don't
seem inconvenient to me.

SteveT

Steve Litt
Spring 2021 featured book: Troubleshooting Techniques of the Successful
Technologist http://www.troubleshooters.com/techniques