- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: DNS issue
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
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
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
01-26-2016 09:28 AM
01-26-2016 09:28 AM
I am trying to do:
$set host servername
I get %SYSTEM-F-NOSUCHNODE, remote node is unknown
but if i do....
$set host servername.fqdn.com
it works.
My BIND settings seem to be correct I can ping servername and get responses. So how do I get the SET HOST command to know it's fully qualified domain name?
FYI: I am a VMS newbie, please explain it to me like I am 4 years old. Thanks!
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-26-2016 10:07 AM
01-26-2016 10:07 AM
Re: DNS issue
Greetings, Just Add the /TELNET qualifier and the SET HOST should connect fine with a login prompt -- Username:
Here's a snippit from Set Host Help:
{ IPhostname }
SET HOST/TELNET { IPaddress }
{ }
NOTE
You can specify the IPhostname or the IPaddress
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-26-2016 10:41 AM
01-26-2016 10:41 AM
Re: DNS issue
That works, but for our scripts to run properly we need just set host servername to work.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-26-2016 11:11 AM
01-26-2016 11:11 AM
Re: DNS issue
Presuming you are running a fairly recent Version of the OpenVMS native TCPIP stack...
Please Post the results of the following:
$ TCPIP SH HOSTS
$ TCPIP SH NAME_SERV
Regards
Kip
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-26-2016 11:20 AM - edited 01-26-2016 11:23 AM
01-26-2016 11:20 AM - edited 01-26-2016 11:23 AM
Re: DNS issue
Due to the nature of my network I can't post exact results. But I can say the only difference between my working machine and my non working one w/ those two commands is of course it's own hostname and the working one has stuff in Path: when executing the tcpip sh name_serv but the non working one does not. I have attempted to remedy that, assuming it was the problem but I have had no luck. The TCPIP> Set name_service/system/path=(xxx) will set it there but if I go to @sys$manager:tcpip$config and look at the the Bind Resolver Configuration it is not there. So I know I am doing something wrong...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-26-2016 02:01 PM
01-26-2016 02:01 PM
Re: DNS issue
Okay, I get that you shoul not post those exact results - After-all we run vital and secure systems with OpenVMS. Look at option (3) below (a snippet from TCPIP help on set host) (different context from os level set host)) and adjust it for your site - be sure to do on all nodes of the cluster and that set host should work fine:
1.TCPIP> SET HOST MOA /ADDRESS=11.33.33.8 -
_TCPIP> /ALIAS=("moa","bigbrd","nofly")
Sets the IP address of host MOA to 11.33.33.8 and establishes
moa, bigbrd, and nofly as aliases for host MOA.
2.TCPIP> SET HOST MOA /ALIAS="MOA_2"
Establishes MOA_2 as an alias for host MOA.
3.TCPIP> SET HOST MOA /ADDRESS = 128.33.33.9 <-------- name it as to what you want to do the $ Set Host to...
Establishes a second IP address for host MOA.
4.TCPIP> SET HOST MOA /ADDRESS = 128.33.33.9 /ALIAS="MOA_3"
Regards,
Kip
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-26-2016 02:16 PM
01-26-2016 02:16 PM
Re: DNS issue
Actually just focus on deploying Option 1. I was thinking of somethingelse for using Option 3.
Regards
Kip
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-26-2016 04:07 PM
01-26-2016 04:07 PM
Re: DNS issue
Justin,
You only changed the active systemwide name resolution. TPCIP$CONFIG is probably showing you the permanent name service configuration. To make your name resolver changes permanent:
$ tcpip set configuration name_serivce /path=(xxx)
That still may not resolve your name resolution problem though. Most of us associate the usage of "set host" with DECnet, not TCP/IP. Are you using DECnet over IP by chance? If you aren't sure, try the following:
$ show network
Product: TCP/IP Node: host.subdomain.domain.com Address(es): xxx.xxx.xxx.xxx
Product: DECNET Node: HOST Address(es): yy.yyyy
if you see DECnet then:
$ mcr ncl show implementation
If the ncl command completes successfully, you are running some version of DECnet phase V (aka DECnet PLus, DECnet/OSI), which can be configured to use TCPIP for routing DECnet.
$ mcr ncl show osi transport template osit$rfc1006*
If it returns something like the following you have DECnet over IP configured:
Node 0 OSI Transport Template osit$rfc1006
at 2016-01-26-17:39:21.344-06:00Iinf
Identifiers
Name = osit$rfc1006
Node 0 OSI Transport Template osit$rfc1006plus
at 2016-01-26-17:39:21.344-06:00Iinf
Identifiers
Name = osit$rfc1006plus
And you should have the PWIP driver configured in TCPIP$CONFIG and running if expecting DECnet over IP to work:
$show system/process=TCPIP$PWIP_ACP
Unfortunately, DECnet Phase V grabs the TCPIP name resolver configuration at boottime and will not recognize your changes to the name resolver until you reboot.
An alternative to rebooting is to change DECnet Plus's "NAMING SEARCH PATH". Have a look at the NCL procedure SYS$MANAGER:NET$SEARCHPATH_STARTUP.NCL. Add another directory service entry to add your subdomain that is not being resolved.
[DIRECTORY SERVICE = DOMAIN, TEMPLATE = "*.subdomain.domain.com"]
Then excute it with $mcr ncl @sys$MANAGER:NET$SEARCHPATH_STARTUP.NCL
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-27-2016 08:42 AM
01-27-2016 08:42 AM
SolutionCo-Worker found a fix. We had to disable BIND do @sys$MANAGER:NET$CONFIGURE BASIC and then set our fully qualified host name for DNS/BIND. Then re-enable BIND.