[Info-vax] duplicated DNS domain name (was: Re: stupid network tricks)

[BillPedersen]

On Monday, March 9, 2015 at 12:58:54 PM UTC-4, Stephen Hoffman wrote:
> On 2015-03-09 16:40:49 +0000, <lists at openmailbox.org> said:
> 
> > On Mon, 9 Mar 2015 09:23:36 -0700 (PDT)
> > BillPedersen via Info-vax <info-vax at rbnsn.com> wrote:
> >> Do you have the log of the last run of the TCPIP$CONFIG?  It would be 
> >> interesting to see what happened there.
> > 
> > I went through TCPIP$CONFIG several times just now and I don't know 
> > which one(s) would be worth looking at.
> 
> Use the core settings (1) or All settings (A) in the TCP/IP Services 
> TCPIP$CONFIG tool, and enter all of the details requested, and avoid 
> trying the DHCP path.
> 
> The documentation on the installation and configuration is detailed, 
> and available via the TCP/IP Services shelf at the 
> <http://www.hp.com/go/openvms/doc> site.
> 
> > If you can tell me the name of the file and where to find it I will try 
> > to paste it here after sanitizing.
> 
> Usual approach here is to capture the full run of the configuraion tool 
> using your terminal emulator.
> 
> > How/where should DNS server names be specified? It appears on UNIX the 
> > DHCP client code sets up resolv.conf from info the DHCP server sends. 
> > That didn't seem to happen on OpenVMS because I could not resolve any 
> > external names until I pointed BIND at my router (which is anyway not a 
> > BIND server but does resolve names)
> 
> How to specify that?  Asking that question implies you are probably not 
> using the core (1) or All (A) setting in the configuration tool, as 
> those prompt for these details.
> 
> VMS does not use /etc/resolv.conf, and I'd tend to avoid using the 
> local version of /etc/hosts in preference to using a DNS server.  But 
> the local equivalent of /etc/hosts is the TCPIP> SET HOST stuff, and 
> that does work.  But you do need to configure the resolver through the 
> menus (easier to explain) or through the command line.
> 
> Again, OpenVMS is not very good at being a DHCP client.  It would not 
> surprise me that trying to use VMS as a DHCP client is at the core of 
> this mess.
> 
> -- 
> Pure Personal Opinion | HoffmanLabs LLC

I fully agree with Hoff - stay away from DHCP for VMS.  Never have used it.  Not well supported and messes with other portions of the networking.

Bill.