HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- telnet delay issue with dns
Operating System - HP-UX
1834058
Members
2628
Online
110063
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
Forums
Discussions
Discussions
Discussions
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
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
09-28-2009 04:32 PM
09-28-2009 04:32 PM
telnet delay issue with dns
HPUX 11.23
resolv.conf:
domain mydomain
nameserver 10.0.20.16
retrans:1000
retry:1
nsswitch.conf:
hosts: files [NOTFOUND=continue TRYAGAIN=continue UNAVAIL=continue] dns
ipnodes: files [NOTFOUND=continue TRYAGAIN=continue UNAVAIL=continue] dns
i searched the forums and read 30+ threads regarding this issue and don't understand it.
i want my telnet prompt to be independent of a dns reverse lookup. i understand that its a "security" issue where before hpux send a prompt it does a reverse lookup of the source ip but if my dns server goes down we don't get a login and that’s a problem. besides how is it that if i remove the resolv.conf file i get the login right away? why can't i have it behave like that regardless of the dns servers availability?
i even tried adding a pc's name to the host file and then shutdown the dns server, but the prompt still delays.
any help would be appreciated.
thanks,
amir
resolv.conf:
domain mydomain
nameserver 10.0.20.16
retrans:1000
retry:1
nsswitch.conf:
hosts: files [NOTFOUND=continue TRYAGAIN=continue UNAVAIL=continue] dns
ipnodes: files [NOTFOUND=continue TRYAGAIN=continue UNAVAIL=continue] dns
i searched the forums and read 30+ threads regarding this issue and don't understand it.
i want my telnet prompt to be independent of a dns reverse lookup. i understand that its a "security" issue where before hpux send a prompt it does a reverse lookup of the source ip but if my dns server goes down we don't get a login and that’s a problem. besides how is it that if i remove the resolv.conf file i get the login right away? why can't i have it behave like that regardless of the dns servers availability?
i even tried adding a pc's name to the host file and then shutdown the dns server, but the prompt still delays.
any help would be appreciated.
thanks,
amir
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-28-2009 06:06 PM
09-28-2009 06:06 PM
Re: telnet delay issue with dns
> i want my telnet prompt to be independent of a dns reverse lookup.
That is hard coded into telnet and not configurable.
> how is it that if i remove the resolv.conf file i get the login right away?
That condition defines that DNS is not available and won't be consulted.
> i even tried adding a pc's name to the host file and then shutdown the dns server, but the prompt still delays.
Rather than shutdown the DNS server, just put some other IP address in resolv.conf (that is not a DNS server). However, giving the IP address of your PC a name in /etc/hosts should resolve before DNS. Use nsquery to see how the name and IP are resolved:
nsquery hosts 12.34.56.78
nsquery hosts mypcname
Note that you can also add another nsswitch.conf ruleset to nsquery:
nsquery hosts mypcname "dns [NOTFOUND=continue TRYAGAIN=return] files"
Bill Hassell, sysadmin
That is hard coded into telnet and not configurable.
> how is it that if i remove the resolv.conf file i get the login right away?
That condition defines that DNS is not available and won't be consulted.
> i even tried adding a pc's name to the host file and then shutdown the dns server, but the prompt still delays.
Rather than shutdown the DNS server, just put some other IP address in resolv.conf (that is not a DNS server). However, giving the IP address of your PC a name in /etc/hosts should resolve before DNS. Use nsquery to see how the name and IP are resolved:
nsquery hosts 12.34.56.78
nsquery hosts mypcname
Note that you can also add another nsswitch.conf ruleset to nsquery:
nsquery hosts mypcname "dns [NOTFOUND=continue TRYAGAIN=return] files"
Bill Hassell, sysadmin
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.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP