[Info-vax] Telnet DNS Problem (OpenVMS 8.4, Itanium)

[Stephen Hoffman]

On 2016-02-17 18:40:23 +0000, serfsmith at gmail.com said:

> Yes Stephen, I included the ping -4 bit merely for context (to show my 
> workstation IP address), I wanted to illustrate the fact that our 
> DNS/DHCP setup presently doesn't resolve reverse queries.  The bit that 
> actually shows this is the nslookup invocation with contextual DNS 
> record type selection (PTR) and query with my IP address.

Based on what's shown, your DNS doesn't resolve forward names quite 
right, either.     Or there's been a poor obfuscation.    example.org, 
example.net and example.com are available for that use.

Once DNS is hosed, pretty much everything else is hosed on a modern 
server, too.

OpenVMS isn't particularly modern, so it'll tend to work where newer 
systems will throw (usually) security-related errors.

> The point is: the fact that dns.acme.org (if you look at the output 
> you'll see that my attempt to obfuscate all *real* server names 
> throughout this thread was foiled there) doesn't resolve reverse 
> queries properly is a red herring; I've isolated the problem to TELNET 
> (apparently) not invoking the official means of resolving DNS records, 
> that is: NAME_SERVICE.

So either add the reverse translations via $GENERATE or otherwise, or 
ask HPE for a way to shut off reverse translations within the telnet 
server.   Or switch to ssh, as PuTTY can deal with that.

Given the inherent latency through HPE Support, establishing 
authoritative reverse translations will probably be more expedient.




-- 
Pure Personal Opinion | HoffmanLabs LLC