[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[LDM #RVC-520134]: Reverse DNS Lookup Oddity

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: [LDM #RVC-520134]: Reverse DNS Lookup Oddity
  • Date: Wed, 31 Jan 2018 10:21:57 -0700
Robert,

Our systems administrator suggests that you heck your "/etc/hosts" file for 
conflicting entries.

> I talked to one of the admins.  It seems the most relevant change might be 
> the fact that we no longer have NIS running in our network.  I guess my 
> question is where will gethosbyaddr seek out the hostname if "named" is not 
> running locally, "/etc/hosts" contains no entry, and NIS is unavailable?  
> Will it check the nameservers in /etc/resolv.conf?  In the mean time, unless 
> you have any other thoughts (or we stumble upon a DNS configuration issue), I 
> think the easiest thing for us to do is retain a couple entries in the 
> /etc/hosts file -- in any case, this will resolve the hostname.

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: RVC-520134
Department: Support LDM
Priority: Normal
Status: Closed
===================
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata 
inquiry tracking system and then made publicly available through the web.  If 
you do not want to have your interactions made available in this way, you must 
let us know in each email you send to us.