On 3/1/22 17:03, Viktor Dukhovni wrote:
On 1 Mar 2022, at 9:00 am, Kristian Vilmann
<[email protected]> wrote:
2022-03-01 10:32:28.122803 10.100.30.31 10.100.10.32 DNS Standard
query 0xc6b1 A influx.int.myzone.eu 81
2022-03-01 10:32:28.122873 10.100.10.32 10.100.30.31 DNS Standard
query response 0xc6b1 A influx.int.myzone.eu A 10.2.98.1 97
The client asked, and the server answered.
Yup
2022-03-01 10:32:29.209988 10.100.30.31 10.100.10.32 DNS Standard
query 0xe765 A influx.int.myzone.eu.myzone.org 93
2022-03-01 10:32:29.210065 10.100.10.32 10.100.30.31 DNS Standard
query response 0xe765 No such name A influx.int.myzone.eu.myzone.org SOA
ns.myzone.org 165
Since the client asked again, most likely the network lost the
reply. Your client should have "ndots" set sensibly, to avoid
this sort of search.
Yeah! It seems someone tried different options ealier, but ndots seems
to do the trick. It puts a bit more load on the cache, but probably
nothing to worry about.
We'll see what happens when we move all the servers to the new
nameserver :)
thanks
_______________________________________________
dns-operations mailing list
[email protected]
https://lists.dns-oarc.net/mailman/listinfo/dns-operations
