LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie
User Name
Password
Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question? If it is not in the man pages or the how-to's this is the place!

Notices


Reply
  Search this Thread
Old 08-08-2018, 04:32 AM   #1
devwratpd
LQ Newbie
 
Registered: Aug 2018
Posts: 5

Rep: Reputation: Disabled
Unhappy ** server can't find 101.190.168.172.in-addr.arpa.: NXDOMAIN


Hello Guy's

I'm able to nslookup hostname but not able to nslookup IP.

Please help.

Thanks.

[root@alpha ~]# vi /var/named/chroot/etc/named.conf
[root@alpha ~]# service named restart
Stopping named: [ OK ]
Starting named: [ OK ]
[root@alpha ~]# nslookup alpha
Server: 172.168.190.101
Address: 172.168.190.101#53

Name: alpha.server.com
Address: 172.168.190.101

[root@alpha ~]# nslookup alpha.server.com
Server: 172.168.190.101
Address: 172.168.190.101#53

Name: alpha.server.com
Address: 172.168.190.101

[root@alpha ~]# nslookup crsprod-scan
Server: 172.168.190.101
Address: 172.168.190.101#53

Name: crsprod-scan.server.com
Address: 172.168.190.110
Name: crsprod-scan.server.com
Address: 172.168.190.120
Name: crsprod-scan.server.com
Address: 172.168.190.130

[root@alpha ~]# nslookup 172.168.190.101
Server: 172.168.190.101
Address: 172.168.190.101#53

** server can't find 101.190.168.172.in-addr.arpa.: NXDOMAIN

*******************************************************************



[root@alpha ~]# cat /var/named/chroot/etc/named.conf
options
{
directory "/var/named";
listen-on port 53 { any; };
};
zone "server.com"
{
type master;
file "server.com.fwd.zone";
};
zone "localhost"
{
type master;
file "localhost.fwd.zone";
};
zone "190.168.172.in-addr.arpa"
{
type master;
file "172.168.190.rev.zone";
};
zone "0.0.127.in-addr.arpa"
{
type master;
file "localhost.rev.zone";
};

zone "." in {
type hint;
file "/dev/null";
};

[root@alpha ~]#
[root@alpha ~]#
[root@alpha ~]#
[root@alpha ~]# cat /var/named/chroot/var/named/server.com.fwd.zone
$TTL 1D
@ IN SOA alpha.server.com. root.localhost (
2011071500 ; serial
8H ; refresh
4H ; retry
1W ; expiry
1D ) ; minimum
@ IN NS alpha.server.com.
localhost IN A 127.0.0.1
alpha IN A 172.168.190.101
beta IN A 172.168.190.102
alpha-vip IN A 172.168.190.103
beta-vip IN A 172.168.190.104
crsprod-scan IN A 172.168.190.110
IN A 172.168.190.120
IN A 172.168.190.130
[root@alpha ~]#
[root@alpha ~]#
[root@alpha ~]#
[root@alpha ~]#
[root@alpha ~]#
[root@alpha ~]# cat /var/named/chroot/var/named/172.168.190.rev.zone
$TTL 1D
@ IN SOA alpha.server.com. root.localhost. (
2011071500 ; serial
8H ; refresh
4H ; retry
1W ; expiry
1D ) ; minimum
@ IN NS alpha.server.com.
1 IN PTR alpha.server.com.
2 IN PTR beta.server.com.
3 IN PTR alpha-vip.server.com.
4 IN PTR beta-vip.server.com.
[root@alpha ~]#
[root@alpha ~]#
[root@alpha ~]#
[root@alpha ~]#
[root@alpha ~]#
[root@alpha ~]# cat /var/named/chroot/var/named/localhost.fwd.zone
$TTL 1D
@ IN SOA @ root (
2011071500 ; serial
8H ; refresh
4H ; retry
1W ; expiry
1D ) ; minimum
IN NS @
IN A 127.0.0.1

[root@alpha ~]#
[root@alpha ~]#
[root@alpha ~]#
[root@alpha ~]# cat /var/named/chroot/var/named/localhost.rev.zone
$TTL 1D
@ IN SOA localhost. root.localhost. (
2011071500 ; serial
8H ; refresh
4H ; retry
1W ; expiry
1D ) ; minimum
IN NS localhost.
1 IN PTR localhost.
[root@alpha ~]#
[root@alpha ~]#
[root@alpha ~]#
[root@alpha ~]# cat /etc/resolv.conf
search server.com
nameserver 172.168.190.101
nameserver 172.168.190.102
options attempts: 3
options timeout: 3

[root@alpha ~]#
[root@alpha ~]#
[root@alpha ~]#
 
Old 08-08-2018, 04:43 AM   #2
bathory
LQ Guru
 
Registered: Jun 2004
Location: Piraeus
Distribution: Slackware
Posts: 13,163
Blog Entries: 1

Rep: Reputation: 2032Reputation: 2032Reputation: 2032Reputation: 2032Reputation: 2032Reputation: 2032Reputation: 2032Reputation: 2032Reputation: 2032Reputation: 2032Reputation: 2032
Quote:
[root@alpha ~]# nslookup 172.168.190.101
Server: 172.168.190.101
Address: 172.168.190.101#53

** server can't find 101.190.168.172.in-addr.arpa.: NXDOMAIN
Quote:
cat /var/named/chroot/var/named/172.168.190.rev.zone
$TTL 1D
@ IN SOA alpha.server.com. root.localhost. (
2011071500 ; serial
8H ; refresh
4H ; retry[root@alpha ~]# nslookup 172.168.190.101
Server: 172.168.190.101
Address: 172.168.190.101#53

** server can't find 101.190.168.172.in-addr.arpa.: NXDOMAIN
1W ; expiry
1D ) ; minimum
@ IN NS alpha.server.com.
1 IN PTR alpha.server.com.
2 IN PTR beta.server.com.
3 IN PTR alpha-vip.server.com.
4 IN PTR beta-vip.server.com.
There is no PTR record for 172.168.190.101, so you get the expected result.
Add:
Code:
101 IN PTR alpha.server.com.
increase the serial, reload zone and you'll be ok.
 
Old 08-08-2018, 05:54 AM   #3
devwratpd
LQ Newbie
 
Registered: Aug 2018
Posts: 5

Original Poster
Rep: Reputation: Disabled
Smile Solved

OMG bathory I don't have any words for you.I'm really speechless.Thank you so much.

Could you please explain me in detail ?

Please suggest some links related to my problem I really want to learn in depth.

Thanks.
 
Old 08-08-2018, 06:17 AM   #4
devwratpd
LQ Newbie
 
Registered: Aug 2018
Posts: 5

Original Poster
Rep: Reputation: Disabled
Unhappy Facing the same issue on another node

[root@beta ~]# cat /var/named/chroot/var/named/172.168.190.rev.zone
$TTL 1D
@ IN SOA beta.server.com. root.localhost. (
2011071500 ; serial
8H ; refresh
4H ; retry
1W ; expiry
1D ) ; minimum
@ IN NS beta.server.com.
1 IN PTR alpha.server.com.
2 IN PTR beta.server.com.
3 IN PTR alpha-vip.server.com.
4 IN PTR beta-vip.server.com.
101 IN PTR beta.server.com.


[root@beta ~]# service named restart
Stopping named: [ OK ]
Starting named: [ OK ]
[root@beta ~]# nslookup 172.168.190.102
Server: 172.168.190.102
Address: 172.168.190.102#53

** server can't find 102.190.168.172.in-addr.arpa.: NXDOMAIN
 
Old 08-08-2018, 06:30 AM   #5
devwratpd
LQ Newbie
 
Registered: Aug 2018
Posts: 5

Original Poster
Rep: Reputation: Disabled
Unhappy Not able to nslookup with another node ip

Hello dear

Now able to nslookup with self node IP but not able to nslookup another node IP

[root@beta ~]# cat /var/named/chroot/var/named/172.168.190.rev.zone
$TTL 1D
@ IN SOA beta.server.com. root.localhost. (
2011071500 ; serial
8H ; refresh
4H ; retry
1W ; expiry
1D ) ; minimum
@ IN NS beta.server.com.
1 IN PTR alpha.server.com.
2 IN PTR beta.server.com.
3 IN PTR alpha-vip.server.com.
4 IN PTR beta-vip.server.com.
102 IN PTR beta.server.com.
[root@beta ~]# nslookup 172.168.190.102
Server: 172.168.190.102
Address: 172.168.190.102#53

102.190.168.172.in-addr.arpa name = beta.server.com.

[root@beta ~]# nslookup 172.168.190.101
Server: 172.168.190.102
Address: 172.168.190.102#53

** server can't find 101.190.168.172.in-addr.arpa.: NXDOMAIN

[root@beta ~]#

**************************************************************************************************** ***********************


[root@alpha ~]# cat /var/named/chroot/var/named/172.168.190.rev.zone
$TTL 1D
@ IN SOA alpha.server.com. root.localhost. (
2011071500 ; serial
8H ; refresh
4H ; retry
1W ; expiry
1D ) ; minimum
@ IN NS alpha.server.com.
1 IN PTR alpha.server.com.
2 IN PTR beta.server.com.
3 IN PTR alpha-vip.server.com.
4 IN PTR beta-vip.server.com.
101 IN PTR alpha.server.com.
[root@alpha ~]# nslookup 172.168.190.101
Server: 172.168.190.101
Address: 172.168.190.101#53

101.190.168.172.in-addr.arpa name = alpha.server.com.

[root@alpha ~]# nslookup 172.168.190.102
Server: 172.168.190.101
Address: 172.168.190.101#53

** server can't find 102.190.168.172.in-addr.arpa.: NXDOMAIN

[root@alpha ~]#
 
Old 08-08-2018, 07:51 AM   #6
bathory
LQ Guru
 
Registered: Jun 2004
Location: Piraeus
Distribution: Slackware
Posts: 13,163
Blog Entries: 1

Rep: Reputation: 2032Reputation: 2032Reputation: 2032Reputation: 2032Reputation: 2032Reputation: 2032Reputation: 2032Reputation: 2032Reputation: 2032Reputation: 2032Reputation: 2032
Quote:
Please suggest some links related to my problem I really want to learn in depth.
You should start reading this



Quote:
Now able to nslookup with self node IP but not able to nslookup another node IP
I really don't understand what you mean? When you get the NXDOMAIN there is no such entry in the zonefile. E.g:
Quote:
cat /var/named/chroot/var/named/172.168.190.rev.zone
<-snip->
1 IN PTR alpha.server.com.
2 IN PTR beta.server.com.
3 IN PTR alpha-vip.server.com.
4 IN PTR beta-vip.server.com.
102 IN PTR beta.server.com. //no 172.168.190.101 in zonefile
[root@beta ~]# nslookup 172.168.190.102
Server: 172.168.190.102
Address: 172.168.190.102#53

102.190.168.172.in-addr.arpa name = beta.server.com.
[root@beta ~]# nslookup 172.168.190.101
Server: 172.168.190.102
Address: 172.168.190.102#53

** server can't find 101.190.168.172.in-addr.arpa.: NXDOMAIN //correct is there is no 172.168.190.101 in zonefile
Anyway whenever you do changes to zonefiles, you need to increase the serial number and reload the zone. Your serial is always 2011071500. Use 2018080801 (today's date) and increase it by "1" anytime you do changes to it.
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] DNS doesn't resolve reverse lookup Giving Error "server can not find x.xx.xx.in-addr.arpa.:NXDOMAIN" amulya_lky Linux - Server 1 10-31-2017 04:14 PM
error: ** server can't find 79.20.168.192.in-addr.arpa: REFUSED mamtasahai1 Linux - General 18 04-29-2017 01:23 PM
[SOLVED] RHEL 7 reverse lookup error ** server can't find x.x.x.x.in-addr.arpa.: NXDOMAIN scofieldd Red Hat 6 12-18-2016 03:16 PM
[SOLVED] nslookup 192.168.143.10 ( server can't find 10.143.168.192.in-addr.arpa.: NXDOMAIN) mferozbaig Linux - Server 2 05-11-2014 06:08 AM
[SOLVED] error "server can't find 254.0.168.192.in-addr.arpa: SERVFAIL" in dns server piyusharora420 Linux - Server 15 01-10-2011 01:06 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie

All times are GMT -5. The time now is 06:18 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration