Bug 18193

Summary:	Bogus diagnostics by nslookup(1)
Product:	Base System	Reporter:	Mikhail Teterin <mi>
Component:	bin	Assignee:	freebsd-bugs (Nobody) <bugs>
Status:	Closed FIXED
Severity:	Affects Only Me
Priority:	Normal
Version:	1.0-RELEASE
Hardware:	Any
OS:	Any

Description Mikhail Teterin 2000-04-24 14:00:00 UTC

	When the  requested type of  record for a domain  is not
	available, nslookup will say: "Non-existent host/domain"
	even though the domain is known...

How-To-Repeat: 
	For example, this spammer's domain does not have the RP
	record:

	mi@misha:~ (148) nslookup -type=RP TURNKEYCASINO.NET
	Server:  .....
	Address:  .....

	*** .... find TURNKEYCASINO.NET: Non-existent host/domain

	But the domain is known:

	mi@misha:~ (149) nslookup -type=ANY TURNKEYCASINO.NET
	Server:  .....
	Address:  .....

	Non-authoritative answer:
	TURNKEYCASINO.NET       nameserver = NS2.WORLD-SERVICES.COM
	TURNKEYCASINO.NET       nameserver = NS1.WORLD-SERVICES.COM

	Authoritative answers can be found from:
	TURNKEYCASINO.NET       nameserver = NS2.WORLD-SERVICES.COM
	TURNKEYCASINO.NET       nameserver = NS1.WORLD-SERVICES.COM
	NS2.WORLD-SERVICES.COM  internet address = 204.71.166.62
	NS1.WORLD-SERVICES.COM  internet address = 204.71.166.61

Comment 1 Jeroen Ruigrok van der Werven freebsd_committer

2000-04-30 14:44:12 UTC

Responsible Changed
From-To: gnats-admin->freebsd-bugs

Misfiled PR. 

Notes: This domain name is severly botched in its set-up. 

Also, nslookup is a command provided with the BIND package, 
so any change/feature requests are best asked on the ISC lists. 

Also, given the parameters to nslookup it does make sense.  It tries to 
find the domain/host using only the type of query you specified, which 
logically leads to non-existant host/domain.  A -type=any will of course 
always match.

Comment 2 Poul-Henning Kamp freebsd_committer

2001-06-02 10:02:58 UTC

State Changed
From-To: open->closed

Take this up with the BIND developers.