LO70588: Notes Client 8.5.3 (Notebook) moves to another network location, where the home mail server can only be resolved withit

APAR status

• Closed as fixed if next.

Error description

• Notes Client 8.5.3 (Notebook) moves to another network
  location, where the home mail server can only be resolved with
  its FQDN.  Client is unable to find it's home mail server and
  all other servers within the domain after using the Best
  practices for "Ensuring DNS resolves in NRPC" as stated in the
  Admin help. Which involves Adding FQDN to Secondary TCPIP Notes
  Name server field in location document (Advance Tab secondary
  TCIP), still client does not find home mail server or any other
  servers within the domino domain.
  Customer tries to ping the server, it works. Although he could
  only FQDN successfully if he pings but could not ping using
  Notes common name. Using trace in Notes Client does resolve to
  any server.
  If the client has successfully connected to mail server within
  the domain before moving it to another location (Domain) then
  there might be a cache of the server name in the dollar fields.
  if this cache is not cleared out, this will use the cache to
  connect to the server. So when this cache is cleared out and
  add the FDQN in the secondary TCIP Notes Name server field,
  this does not resolve to any server at all.
  If he mis-types host mail server address (incorrect) on Server
  Tab of the location document to the nameserver, this seems to
  work as Notes trace tries to resolves to the mail server.
  Trace files showed that DNS wasn't able to connect to the
  server. If the server is not reachable at TCPIP level, then
  Notes will not be able to access it.  Researching if Secondary
  Names can be used in such configuration, the only case I'm sure
  Secondary Names is used is at Notes workstation setup. There is
  no documentation, internal nor external, that showed the
  secondary names can be used to resolved server address that the
  DNS cannot resolved.
  

Local fix

Problem summary

• Secondary Name Server mechanism does not work as designed.
  

Problem conclusion

Temporary fix

Comments

• This APAR is associated with SPR# MLEY8WKAT4.
  Secondary Name Server mechanism does not work as designed.
  

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels

• R853 PSN

     UP