@REPLY: 2:203/910 6a6927fc
@MSGID: 2:382/736 6a692e9a
@CHRS: CP866 2
@TZUTC: 0200
Hello Alexey!

29 Jul 26 00:04, you wrote to me:

 AM> map@rsrv:~ $ time host f0.n39.z39.binkp.net
 AM> ;; communications error to 192.168.100.1#53: timed out
 AM> real    0m10.210s
 AM> map@rsrv:~ $ time host f736.n382.z2.binkp.net
 AM> f736.n382.z2.binkp.net is an alias for ftn.jegor.net.
 AM> ftn.jegor.net has address 188.93.124.39
 AM> ftn.jegor.net has IPv6 address 2a07:de80:0:1::1:22
 AM> real    0m1.680s

 So it`s lagging for 10s on non-existing hosts instead of quickly
giving NXDOMAIN. And even 1.6s for existing ones is way too long.

 Since it looks like you`re on Linux, does it get any faster if
you set your nameservers to, say, 8.8.8.8 and 8.8.4.4 using your
distro`s config tool or directly in /etc/resolv.conf?

Yegor

--- GoldED+/LNX 1.1.5-b20260304
 * Origin:   (2:382/736)
SEEN-BY: 30/0 124/5016 203/0 221/0 1 230/0 240/12
1120 1512 1634 4075 5832
SEEN-BY: 240/8002 8005 250/1 263/1 275/100 280/464
1043 5003 5006 5555 292/789
SEEN-BY: 292/854 8125 301/1 310/31 313/41 320/219
331/51 335/364 341/66 234
SEEN-BY: 362/6 371/0 382/200 736 410/9 421/790
423/120 455/19 460/58 463/68
SEEN-BY: 467/70 469/122 492/0 530/204 550/278
712/848 5001/100 5015/46
SEEN-BY: 5020/290 400 545 715 921 1042 1146 2992
5452 8912 9696 5022/2 5023/24
SEEN-BY: 5030/1081 5034/13 5051/44 5055/73 5057/19
5058/104 5061/15 5075/35
SEEN-BY: 5075/128 5101/1 6035/3 6090/1
@PATH: 382/736 240/1120 280/464 292/854 5020/715