Sendmail & Bind Problem

[Mickey.Olsberg at edwardjones.com]

The ability to resolve a non-fully-qualified (NFQ) hostname (such as 
nameserver by itself) is configured within the resolver. In Windows, 
adding an entry (ourcompany.ca) to the domain name under TCP/IP advanced 
properties adds that domain name to unknown or NFQ queries, while adding 
the line 'domain  ourcompany.ca' to a UNIX systems /etc/resolv.conf file 
will do the same for UNIX.

The relay for sendmail is usually configured in the /etc/mailertable 
file and you could hard-code this to a fully-qualified host 
(nameserver.ourcompany.ca.)...

Hope this helps!
Mickey Olsberg


-----Original Message-----
From: wayne.stewart [mailto:wayne.stewart at clerkware.ca]
Sent: Friday, July 16, 2004 5:23 AM
To: bind-users
Subject: Sendmail & Bind Problem


We have set up a simple domain.
"ourcompany.ca"

The nameserver for is 

"nameserver.ourcompany.ca"

If we run "dig nameserver" the process fails.
If we run "dig nameserver.ourcompany.ca" it succeeds.

We are having a problem with 'sendmail' because the 'smarthost' 
mailserver is also "nameserver" and sendmail reports a DNS failure for 
"relay=nameserver"

How can we get named to respond to queries on the local subnet when the 
fully qualified domain name is not supplied?