1847846 Members
2644 Online
104021 Solutions
New Discussion

nslookup timed out

 
ulisse lusuardi
Advisor

Re: nslookup timed out

To Mr.Manuel Perez Ron,
And now the results of the command:
> nslookup
>> Default Name server: Localhost
>> Address : 127.0.0.1

> 193.72.242.149
>> Default Name server: Localhost
>> Address : 127.0.0.1
>> Trying DNS

>> Loking up FILES (*)
>> Name: ms_fserv
>> Address: 193.72.242.149

(*) This response appear delayed of 2-3 Minutes
The result seems correctly.

> ms_fserv
>> ==> give the same result

'search mecasoft.com' was already in resolv.conf



Manuel P. Ron
Frequent Advisor

Re: nslookup timed out

Really, your named service is not properly configured. Can you show the file named.boot?
Crash programs fail because they are based on the theory that, with nine women pregnant, you can get a baby a month. - Wernher von Braun
ulisse lusuardi
Advisor

Re: nslookup timed out

To Mr.Manuel Perez Ron,
Here I send you the file named.boot.
Good week.
ulisse lusuardi
Advisor

Re: nslookup timed out

To Mr.Manuel Perez Ron,
Here I send you the file named.boot.
Manuel P. Ron
Frequent Advisor

Re: nslookup timed out

Do some changes in your file db.mecasoft.com:
1. All CNAMES left with hostname only, e.g:
francesco CNAME nodesu
(not dot at end)
2. Replace all MX records and put this:
@ IN MX 10 ms_fserv.mecasoft.com
3. Erase first line with localhost

Now, try a resolve with ms_fserv and mecasoft_fw. Good luck!

P.S: Why all that MX records? Have you a mail server in every machine?.
Crash programs fail because they are based on the theory that, with nine women pregnant, you can get a baby a month. - Wernher von Braun
ulisse lusuardi
Advisor

Re: nslookup timed out

To Mr.Manuel Perez Ron,
I've generated all files from named.data with the HP tool: /usr/sbin/hosts_to_named -d domain_name -n network_number.
I think that the file db.mecasoft.com is correct.(In a preview installation was the same)

Mr Kofi ARTHIABAH say:" The problem is that your machine is a stand alone and you are telling it that its root name servers are on the internet (which it cannot reach ) that it why it fails. IF your server was on the internet, it probably would work. "

When I will test my installation without the internet connection, I should provisory remove the root name servers from db.cache.What you thinks? or I've other possibility
(My idea is to configure the server machine as standalone, to test it, and after that I will insert it in my network.)



Kofi ARTHIABAH
Honored Contributor

Re: nslookup timed out

You might want to check out this document on how to set up your server as a root dns server - if you are not connected to the internet.

http://docs.hp.com/hpux/onlinedocs/B2355-90759/00/00/40-con.html
nothing wrong with me that a few lines of code cannot fix!
ulisse lusuardi
Advisor

Re: nslookup timed out

To Mr. Kofi ARTHIABAH,
To test my stand alone installation I've followed the proposed hp doc:
a)I've generated the file from named.data and named.boot with
"hosts_to_named -d mecasoft.com -n 193.72.242 -r"
b)I've modified the gateway in /etc/rc.confi.d/netconf : GATEWAY[0]="".
And know the result:
By boot, before the msg "STARTUP in progress" I receive the msg "... auto_parms[10] Syntax error".
After that the msgs from "STARTUP in progress" are all OK.
c) test with nslookup:
result:
>> ***Can't find server name for address 193.72.242.149: Server failed
>> *** Default servers are not available
>> Using /etc/hosts on: ms_fserv
> ms_fserv
>> using /etc/hosts on: ms_fserv
>> looking up FILES
>> Name: ms_fserv
>> Address: 193.72.242.149
To complete I attach the result file "syslog.log".
Maybe with this configuration I don't have other results?

With bests regards
ulisse