%TCPIP-E-NAMEERROR seen booting v9.2-2

All types of networks, network stacks, and protocols supported by OpenVMS.
Post Reply
User avatar

Topic author
imiller
Master
Posts: 147
Joined: Fri Jun 28, 2019 8:45 am
Reputation: 0
Location: South Tyneside, UK
Status: Offline
Contact:

%TCPIP-E-NAMEERROR seen booting v9.2-2

Post by imiller » Thu Mar 14, 2024 1:19 pm

$ ucx show version

VSI TCP/IP Services for OpenVMS x86_64 Version V6.0
on an innotek GmbH VirtualBox running OpenVMS V9.2-2

I've just noticed this error during booting

$ TCPIP SET NAME/SYSTEM/SERVER=GOOGLEDNS/DOMAIN="name.local"/ENABLE !
%TCPIP-E-NAMEERROR, error processing name service request
-TCPIP-E-BINDENABLE, BIND resolver is enabled

I noticed booting after installing the V9.2-2 UPDATE V1 kit but it did happen on the previous boot too.
Ian Miller
[ personal opinion only. usual disclaimers apply. Do not taunt happy fun ball ].


sms
Master
Posts: 349
Joined: Fri Aug 21, 2020 5:18 pm
Reputation: 0
Status: Offline

Re: %TCPIP-E-NAMEERROR seen booting v9.2-2

Post by sms » Sat Mar 16, 2024 11:31 am

Code: Select all

> $ TCPIP SET NAME/SYSTEM/SERVER=GOOGLEDNS/DOMAIN="name.local"/ENABLE !

   I have a real domain (antinode.info), and run a DNS server (BIND) for
it on my main VMS system, so my situation is different, and it's not
obvious to me that any such command is used here.  Do you know where
that one is?  (Someplace under SYS$STARTUP?  I saw nothing similar here
outside of SYS$MANAGER:TCPIP$BINDSETUP.COM, which I wouldn't expect to
be run automatically.)

   "GOOGLEDNS" means approximately nothing to me.  Is it defined as a
(local) host?  (8.8.8.8?)

      tcpip show host GOOGLEDNS

      tcpip show name_service

User avatar

Topic author
imiller
Master
Posts: 147
Joined: Fri Jun 28, 2019 8:45 am
Reputation: 0
Location: South Tyneside, UK
Status: Offline
Contact:

Re: %TCPIP-E-NAMEERROR seen booting v9.2-2

Post by imiller » Mon Mar 18, 2024 6:44 am

I found the command
$ TCPIP SET NAME/SYSTEM/SERVER=GOOGLEDNS/DOMAIN="name.local"/ENABLE
being called from SYSTARTUP_VMS and am trying to work out why.
Ian Miller
[ personal opinion only. usual disclaimers apply. Do not taunt happy fun ball ].


sms
Master
Posts: 349
Joined: Fri Aug 21, 2020 5:18 pm
Reputation: 0
Status: Offline

Re: %TCPIP-E-NAMEERROR seen booting v9.2-2

Post by sms » Mon Mar 18, 2024 8:35 pm

Code: Select all

> [...] being called from SYSTARTUP_VMS and am trying to work out why.

   Leave better notes for yourself when adding such things?  It could be
just my ignorance showing, but I see no reason for such a command in
SYSTARTUP_VMS.COM.  I'd expect the TCPIP NAME_SERVICE settings to
persist.

   Pending questions remain pending.

User avatar

Topic author
imiller
Master
Posts: 147
Joined: Fri Jun 28, 2019 8:45 am
Reputation: 0
Location: South Tyneside, UK
Status: Offline
Contact:

Re: %TCPIP-E-NAMEERROR seen booting v9.2-2

Post by imiller » Tue Mar 19, 2024 5:53 am

I've commented out the command with a note to myself.
googledns is a a defined host with address 8.8.8.8 and the name resolver has it defined as a server.
Ian Miller
[ personal opinion only. usual disclaimers apply. Do not taunt happy fun ball ].

Post Reply