- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- DNS Resolver Issue
Operating System - OpenVMS
1752808
Members
5680
Online
108789
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
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
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- 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-18-2005 07:18 AM
тАО01-18-2005 07:18 AM
DNS Resolver Issue
Running OpenVMS 7.2-1 and TCP/IP Services for OpenVMS V5.1 ECO5.
I have configured a system to have 2 DNS resolvers. They are configured in TCP/IP as follows:
$tcpip show name
BIND Resolver Parameters
Local domain: scada.xom.com
System
State: Started, Enabled
Transport: UDP
Domain: SCADA.XOM.COM
Retry: 1
Timeout: 1
Servers: 158.28.105.129, 158.28.105.2
Path: No values defined
Process
State: Enabled
Transport:
Domain:
Retry:
Timeout:
Servers:
Path:
$tcpip show config name
BIND Resolver Configuration
Transport: UDP
Domain: SCADA.XOM.COM
Retry: 1
Timeout: 1
Servers: 158.28.105.129, 158.28.105.2
Path: No values defined
$
The problem is that if 158.28.105.129 is not available, then the following command hangs at the BIND database section.
$tcpip show host
A show of a specific host OR a misspelled / non-existent host works fine. It's just the above wild card show host command that seems to hang for several seconds.
Is it normal for there to be a delay when the primary DNS resolver has gone away and TCP/IP has to switch to another resolver?
I have configured a system to have 2 DNS resolvers. They are configured in TCP/IP as follows:
$tcpip show name
BIND Resolver Parameters
Local domain: scada.xom.com
System
State: Started, Enabled
Transport: UDP
Domain: SCADA.XOM.COM
Retry: 1
Timeout: 1
Servers: 158.28.105.129, 158.28.105.2
Path: No values defined
Process
State: Enabled
Transport:
Domain:
Retry:
Timeout:
Servers:
Path:
$tcpip show config name
BIND Resolver Configuration
Transport: UDP
Domain: SCADA.XOM.COM
Retry: 1
Timeout: 1
Servers: 158.28.105.129, 158.28.105.2
Path: No values defined
$
The problem is that if 158.28.105.129 is not available, then the following command hangs at the BIND database section.
$tcpip show host
A show of a specific host OR a misspelled / non-existent host works fine. It's just the above wild card show host command that seems to hang for several seconds.
Is it normal for there to be a delay when the primary DNS resolver has gone away and TCP/IP has to switch to another resolver?
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-18-2005 08:10 AM
тАО01-18-2005 08:10 AM
Re: DNS Resolver Issue
I used TCPTRACE/PORT=REMOTE=53 and did a TCPIP SHOW HOST in a similar configuration. Try it for yourself. I'm not sure of the cause of the behavior.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-18-2005 08:14 AM
тАО01-18-2005 08:14 AM
Re: DNS Resolver Issue
It looks like the wildcard request does 4 retries with 4 seconds between tries, regardless of the TCPIP SET NAME and TCPIP SET CONFIG NAME settings.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP