How to resolve host record

[Luca]

Hi,

Perhaps a silly question... Is there a way that I can get our DNS
server to resolve a simple computer name, and not a FQDN?

Say the computer name I want to add is called "host". I have already
created host.domain.com, which resolves fine, providing:

- one types the FQDN
- the client has the correct 'DNS domain' or 'DNS suffix' or 'Domain
name' (each OS calls it in a different way)
- the host name is in the client's host file

our (Novell) DHCP servers do provide the correct Domain name, but I
guess that the local (wrong) setting takes priority on the DHCP one.

Any help would be greatly appreciated.

TIA
luca

 

[Kevin D. Goodknecht [MVP]]

In

Hi,

Perhaps a silly question... Is there a way that I can get our DNS
server to resolve a simple computer name, and not a FQDN?

Say the computer name I want to add is called "host". I have already
created host.domain.com, which resolves fine, providing:

- one types the FQDN
- the client has the correct 'DNS domain' or 'DNS suffix' or 'Domain
name' (each OS calls it in a different way)
- the host name is in the client's host file

our (Novell) DHCP servers do provide the correct Domain name, but I
guess that the local (wrong) setting takes priority on the DHCP one.

Any help would be greatly appreciated.

Have the host record for the computer in a domain forward lookup zone that
matches the DNS suffix search list in TCP/IP properties.
DNS does not really do this, it is up to the TCP/IP stack to append suffixes
to be searched.
Be careful about what name you have in the DNS suffix search list, every
suffix you have increases the time for the query, it is best that you only
have local domains in your search list. I've actually seen cases where there
was a public name in the search list that caused a query for what should
have been a local name resolve to a public host, because the stack appended
the public DNS suffix.