> Date: Tue, 23 Jan 96 11:24:13 PST
> From: greywolf@defender.VAS.viewlogic.com (James Graham - Systems Mangler)
> Reply-To: greywolf@captech.com
> In-Real-Life: Greywolf (corporate types notwithstanding)
> X-Disclaimer: No way are these anyone else's opinions but mine.
> X-Real-Name: James Graham (*NOT* "Jim" -- that's my dad)
> X-Extension: 4214
> X-Window-System: Release 5
> X-Mailer: Mail User's Shell (7.2.5 10/14/92)
> Cc: matthew green <mrg@eterna.com.au>
> content-length: 711
> Sender: owner-current-users@NetBSD.ORG
> Precedence: list
> X-Loop: current-users@NetBSD.ORG
> 
> To contribute to the BIND issues, I find some interesting problems with
> -current BIND.
> 
> Say you live in an environment in which machines are of the form
> 
>         foo.bar.baz.quux
> 
> where foo is the machine.  Say you want to get to another machine
> in a parallel subdomain, such as
> 
> 	bar.foo.baz.quux
> 
> Under previous versions of BIND (the one under StunOS comes to mind),
> one can simply, from machine foo(.bar.baz.quux), say:
> 
> 	# ping bar.foo
> 
> and the resolver will automagically begin adding parts of the domain name
> beyond the unresolved point, i.e.
> 
> 	TRY	bar.foo.	...FAIL
> 	TRY	bar.foo.baz.	...FAIL
> 	TRY	bar.foo.baz.quux.	...OK
> 
> Why is this now broken?

Probably because you now specify exactly what you want to search in
/etc/resolv.conf.

Try putting:

	search bar.baz.quux baz.quux

in your /etc/resolv.conf file instead of

	domain bar.baz.quux

David