Bind expanding domain query using search path?

[David Botham]

> -----Original Message-----
> From: bind-users-bounce at isc.org [mailto:bind-users-bounce at isc.org] On
> Behalf Of Erik Enge
> Sent: Tuesday, October 01, 2002 4:09 PM
> To: bind-users at isc.org
> Subject: Bind expanding domain query using search path?
> 
> 
> 
> Hi.
> 
> I have two domains; office1.co office2.co
> 
> I have two machines; machine1 (in office1.co) machine2 (in office2.co)
> 
> I'm running RedHat 7.2 (x86) and bind 9.2.1.
> 
> Everything seems to be working as it should, but I have a question of
> whether or not I can make this work:
> 
>   dig machine1
> 
> At the moment, it gives this output:
> 
>   eenge at eenge:~$ dig machine1
> 
>   ; <<>> DiG 9.2.1 <<>> machine1
>   ;; global options:  printcmd
>   ;; Got answer:
>   ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 20766
>   ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
> 
>   ;; QUESTION SECTION:
>   ;machine1.                         IN      A
> 
>   ;; AUTHORITY SECTION:
>   .                       7812    IN      SOA     A.ROOT-SERVERS.NET.
> NSTLD.VERISIGN-GRS.COM. 2002100100 1800 900 604800 86400
> 
>   ;; Query time: 82 msec
>   ;; SERVER: 192.168.1.1#53(192.168.1.1)
>   ;; WHEN: Tue Oct  1 14:38:10 2002
>   ;; MSG SIZE  rcvd: 98
> 
> It would be great if it (bind) could try
> machine1.[office1.co,office2.co] before going to the root-servers.


It is not bind that is responsible for this action, it is your dns
client(resolver).  See the man page for resolv.conf, specifically the
domain and search directives.

Dave...

> 
> Is there a way I can do this?  I understand there would be stupidity
> happening if I rename machine2 in office2.co to machine1.q
> 
> Thanks,
> 
> Erik.