Date: Wed, 18 Jul 2001 20:18:25 +0400 From: void@void.ru To: freebsd-security@FreeBSD.ORG Subject: host(1) Message-ID: <18810307145.20010718201825@void.ru> In-Reply-To: <039301c10fa1$c1e44b40$213cd3cf@loop.com> References: <200105181518.WAA12362@bazooka.cs.ait.ac.th> <046c01c0dfc0$833e7fc0$213cd3cf@loop.com> <03a401c10efb$dd2eda60$213cd3cf@loop.com> <20010717223940.A437@blossom.cjclark.org> <039301c10fa1$c1e44b40$213cd3cf@loop.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello All, what's the principle on which host(1) works ? Recently I've denied the zone-transfer queries on the primary and secondary NS'es but command host -l myzone.dom from remote system using different nameserver still lists the zone (but incomplete(!), i.e. some records shown, some not). If it's a problem which caching, can someone explain how to initiate 'cache purging' on the nonauthoritative nameservers ? remotehost# nslookup Default Server: ns.remotens.com Address: 1.1.1.2 > ls -d myzone.dom [ns.remotens.com] *** Can't list domain myzone.dom: Unspecified error >^D remotehost# host -l myzone.dom system1.myzone.dom has address 2.2.2.3 system2.myzone.dom has address 2.2.2.4 [skip] remotehost# 10x, .d To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?18810307145.20010718201825>