- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Name résolution
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-28-2004 02:10 AM
09-28-2004 02:10 AM
Name résolution
During test we changed the name of a server and after we came back to its original name.
Since this operation when we do a telnet to another server, on some of them, a "sho user/full" shows something like:
username _TNA4458: 00041EAB TNA4458: (Host: old name Port: 3749 )
a "set host" shows the right name for the source.
The configuration of TCPIP seems to be good
Any idea
regards
Steph
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-28-2004 02:16 AM
09-28-2004 02:16 AM
Re: Name résolution
It could be a name translation cache needs flushing to remove the incorrect translation.
Purely Personal Opinion
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-28-2004 02:29 AM
09-28-2004 02:29 AM
Re: Name résolution
This behaviour is seen only with a telnet connection not with a set host.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-28-2004 02:34 AM
09-28-2004 02:34 AM
Re: Name résolution
Purely Personal Opinion
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-28-2004 02:44 AM
09-28-2004 02:44 AM
Re: Name résolution
Did you check the host database on the server?
TCPIP SHOW HOST /LOCAL
Maybe some stale data was left in there.
Greetz,
Kris
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-28-2004 03:21 AM
09-28-2004 03:21 AM
Re: Name résolution
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-28-2004 03:23 AM
09-28-2004 03:23 AM
Re: Name résolution
Purely Personal Opinion
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-28-2004 03:50 AM
09-28-2004 03:50 AM
Re: Name résolution
My oppinion is the same a s Ians. The old name is cached somewhere.
Did you try to do a
TCPIP> SET NAME_SERVICE/INITIALIZE
on all nodes which are running DNS? This command reloads the BIND database.
Bojan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-28-2004 04:18 AM
09-28-2004 04:18 AM
Re: Name résolution
We use DNS implemented on Unix server, so a set name/init doesn't help.
I tried to stop and restart the UCX/TCPIP service on the server which received the connection, the problem seems to "run away".
The wrong information seems to be cached, but where?
Is there a TCPIP/UCX command to "flush" this cache like in Decnet/OSI?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-28-2004 04:40 AM
09-28-2004 04:40 AM
Re: Name résolution
UCX
SET NAME/SYSTEM/DISABLE
SET NAME/SYSTEM/ENABLE
I'm not aware of a command to flush the name resolver cache.
Do you mean the first DNS server listed for each system (UCX SHOW NAME) is the same?
Purely Personal Opinion
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-28-2004 05:08 AM
09-28-2004 05:08 AM
Re: Name résolution
Just curiosity, have you try to do a telnet old_name from the server which shows the old name?
Bojan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-28-2004 09:10 AM
09-28-2004 09:10 AM
Re: Name résolution
Purely Personal Opinion
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-29-2004 01:50 AM
09-29-2004 01:50 AM
Re: Name résolution
a telnet old name gives "%TELNET-E-IVHOST, Invalid or unknown host"
all the entry concerning the old name were removed from the dns
Hi Ian
enabling/disabling doesn't solve the problem
Thanks for your help I will stop/start the ucx/tcpip service to correct my problem
Steph.