pkgsrc - [no description]

Age	Commit message (Collapse)	Author	Files	Lines
2012-02-06	Update to 1.9. Notable changes:	shattered	2	-6/+6
	1.9: - With the rollout of IPv6 for a.root-servers.net, it always took the IPv6 address even if you used the -4 option. - Fix false lame server issues with domains which have the higher domain in it (command.com for example). 1.8: - Warnings are printed if you receive a different RR type than the one you asked for (for example when you ask for an A record and receive a CNAME) - Fixed problems when records received in the authority field are shorter than the domain the nameserver is authoritative for. - When compiled without IPv6 support on an IPv6 capable machine the machine tried to query the IPv6 translated IPv4 address anyway.
2011-04-15	Use USE_FEATURES=inet6 for requirement of IPv6 support, instead of unusual usage	obache	1	-6/+2
	of PKG_OPTIONS.
2008-06-12	Add DESTDIR support.	joerg	1	-1/+3

2006-03-04	Point MAINTAINER to pkgsrc-users@NetBSD.org in the case where no	jlam	1	-2/+2
	developer is officially maintaining the package. The rationale for changing this from "tech-pkg" to "pkgsrc-users" is that it implies that any user can try to maintain the package (by submitting patches to the mailing list). Since the folks most likely to care about the package are the folks that want to use it or are already using it, this would leverage the energy of users who aren't developers.
2006-01-02	Add hack to fix build on OS X with BIND9 system resolver.	schmonz	1	-0/+9

2005-11-03	Force requiring IPv6 support. (--disable-ipv6 is nowhere near enough;	tv	1	-1/+6
	it still uses AF_INET6, sockaddr_in6, and getaddrinfo().)
2005-04-11	Remove USE_BUILDLINK3 and NO_BUILDLINK; these are no longer used.	tv	1	-2/+1

2005-02-24	Add RMD160 digests.	agc	1	-1/+2

2004-04-25	Convert to buildlink3 and correct a typo in DESCR.	snj	2	-3/+3

2003-07-21	COMMENT should start with a capital letter.	martti	1	-2/+2

2003-07-17	s/netbsd.org/NetBSD.org/	grant	1	-2/+2

2003-07-10	Initial import of dnstracer.	jtb	4	-0/+28
	Dnstracer determines where a given Domain Name Server (DNS) gets its information from, and follows the chain of DNS servers back to the servers which know the data. Its behaviour is similair to ntptrace(8), which does it for the NTP protocol.