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

[BillPedersen]

On Monday, March 9, 2015 at 12:45:04 PM UTC-4, li... at openmailbox.org wrote:
> Hi,
> 
> 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.
> 
> If you can tell me the name of the file and where to find it I will try to
> paste it here after sanitizing.
> 
> > How did you specify the host hame when you set up TCPIP?  Did you do it
> > as a fully qualified name or as just the host name for the interface did
> > you?  This should just be the host name without the domain name.
> 
> For the domain name I used example.com at first and then changed it after
> reading the replies to example.com. (with a trailing .)
> 
> For the node name I specified only mynode.
> 
> I think it was Paul Sture's suggestion to clear out the tcp/ip config and
> start over again. I can do that but if it is something I'm doing wrong I
> will probably do it again since I've been through the config many times
> already and see nothing obvious to my untrained VMS eye.
> 
> 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)
> 
> Thanks.

Well, TCPIP$CONFIG does not create its own log.  I was hoping your had done a log with whatever terminal emulator you used to access the console of the emulator.

I have never used a trailing period on a domain name in the configuration process.  Not sure how that might confuse TCPIP of this vintage. Nor would I enter the host name when configuring the interface with a trailing period.

I would go into TCPIP$CONFIG, either with logging enable in the terminal emulator or with the terminal emulator configured with as sufficiently large buffer to be able to then capture the run and save it.

Then I would go and make sure the DOMAIN and INTERFACE configuration are clean. Then restart TCPIP from the configuration utility.

Then post the log of the operations.

I have no guarantee here that this will solve your problem but the data may give us remote folks a bit more information to work with.

Bill.