HPE Community read-only access December 15, 2018
This is a maintenance upgrade. You will be able to read articles and posts, but not post or reply.
Hours:
Dec 15, 4:00 am to 10:00 am UTC
Dec 14, 10:00 pm CST to Dec 15, 4:00 am CST
Dec 14, 8:00 pm PST to Dec 15, 2:00 am PST
cancel
Showing results for 
Search instead for 
Did you mean: 

DNS issue.

 
kpatel786
Frequent Advisor

DNS issue.

We have added on HPUX 11.11 server a new DNS server entry (windows 2003) in /etc/resolv.conf file.

We are able to ping the server:
(hqb) [SU] # ping 10.5.3.180
PING 10.5.3.180: 64 byte packets
64 bytes from 10.5.3.180: icmp_seq=0. time=0. ms
64 bytes from 10.5.3.180: icmp_seq=1. time=0. ms
64 bytes from 10.5.3.180: icmp_seq=2. time=0. ms
64 bytes from 10.5.3.180: icmp_seq=3. time=0. ms
64 bytes from 10.5.3.180: icmp_seq=4. time=0. ms
64 bytes from 10.5.3.180: icmp_seq=5. time=0. ms
64 bytes from 10.5.3.180: icmp_seq=6. time=0. ms

----10.5.3.180 PING Statistics----
7 packets transmitted, 7 packets received, 0% packet loss
round-trip (ms) min/avg/max = 0/0/0


But the nslookup is not able to resolve the the dns server name.

(hqb) [SU] # nslookup hpi.dhq.lr.org
*** Can't find server name for address 10.5.3.180: Non-existent domain
*** Default servers are not available
Using /etc/hosts on: hqb

looking up FILES
Trying DNS
*** can't find hpi.dhq.lr.org: No response from server

The same ip is getting resolved for other Linux and windows servers withing our network, however the same is failing for all the hpux boxes. Kindly provide suggestion/inputs to resolve the same. Thanking you in advance.
13 REPLIES
Jose Mosquera
Honored Contributor

Re: DNS issue.

Hi,

What is the content of /etc/resolv.conf file?

Rgds.
kpatel786
Frequent Advisor

Re: DNS issue.

(hqb) [SU] # more /etc/resolv.conf
search internal.lr.org dhq.lr.org lr.org
nameserver 10.5.3.180
Jose Mosquera
Honored Contributor

Re: DNS issue.

Hi,

Add this first line:
domain

Rgds
kpatel786
Frequent Advisor

Re: DNS issue.

(hqb) [SU] # more /etc/resolv.conf
search internal.lr.org dhq.lr.org lr.org
domain 10.5.3.180
===

[SU] # nslookup hpi.dhq.lr.org
Using /etc/hosts on: hqb

looking up FILES
Trying DNS
*** can't find hpi.dhq.lr.org: No response from server


Getting the above output.
Jose Mosquera
Honored Contributor

Re: DNS issue.

Nop!

/etc/etc/resolv.conf:
domain
search internal.lr.org dhq.lr.org lr.org
nameserver 10.5.3.180

Also, What is the content of /etc/nsswitch.conf file?


Rgds.
kpatel786
Frequent Advisor

Re: DNS issue.

(hqb) [SU] # more /etc/nsswitch.conf
#
# /etc/nsswitch.conf
#
# This file is for use on systems that are not running DNS or NIS.
#
# In this case we request that the resolver looks in local files only.
#
# See the Adminstering Internet Services Manual and the switch(4) man
# page for more information on the name service switch.
#

hosts: files [NOTFOUND=continue] dns
kpatel786
Frequent Advisor

Re: DNS issue.

Have tried putting the entries as you said, but the same is not working.
Jim Walls
Trusted Contributor

Re: DNS issue.

Do you know if there is, in fact, and entry in the dns (located at 10.5.3.180) for the hostname hpi.dhq.lr.org ?

Jim Walls
Trusted Contributor

Re: DNS issue.

Also:
>>>[SU] # nslookup hpi.dhq.lr.org
>>>Using /etc/hosts on: hqb
>>>
>>>looking up FILES
>>>Trying DNS
>>>*** can't find hpi.dhq.lr.org: No response from server

Check with your Network administrator to see that UDP port 53 (domain) is not blocked by a firewall rule.

Bill Hassell
Honored Contributor

Re: DNS issue.

> nslookup hpi.dhq.lr.org
> *** Can't find server name for address 10.5.3.180: Non-existent domain

So this indicates that the DNS nameserver can't even identify itself. nslookup has a nifty feature: You can specify any DNS server on the command line to override nsswitch.conf and resolv.conf:

nslookup hpi.dhq.lr.org 10.5.3.180

You'll likely get the same results but it does allow you to test other DNS servers on the command line. Another useful tool is nsquery:

nsquery hosts hpi.dhq.lr.org

This gives you a step-by-step report of the attempts to resolve the name and the results.

Since you can ping the DNS server yet it does not respond to DNS requests, the port is blocked *OR* you may have subnet mask or route error that is not setup for a valid return path. Do you have multiple LAN cards on this server? nettl (HP-UX trace) or Wireshark (PC based packet trace) may help.


Bill Hassell, sysadmin
Jose Mosquera
Honored Contributor

Re: DNS issue.

Hi again,

Please comment your current "host:" line and set this one:

hosts: files [NOTFOUND=continue UNAVAIL=continue TRYAGAIN=continue] dns [NOTFOUND=continue UNAVAIL=continue TRYAGAIN=return]

And please let me know the current domain definition set at /etc/etc/resolv.conf file.

Rgds.
kpatel786
Frequent Advisor

Re: DNS issue.

Thanks all the issue has been resolved. It was related to DNS PTR records at the window servers end.

kpatel786
Frequent Advisor

Re: DNS issue.

Thanks all for your time and assistance.