need help with linux Reverse dns on bind package

bathory · 05-04-2018, 12:10 PM

The trace looks "correct":

Code:

dig +trace 96.178.61.179.in-addr.arpa
<-snip->
178.61.179.in-addr.arpa. 86400	IN	NS	NS9.HOST1PLUS.COM.
178.61.179.in-addr.arpa. 86400	IN	NS	NS10.HOST1PLUS.COM.
178.61.179.in-addr.arpa. 86400	IN	NS	NS8.HOST1PLUS.COM.
178.61.179.in-addr.arpa. 10800	IN	NSEC	179.61.179.in-addr.arpa. NS RRSIG NSEC
<-snip->
96.178.61.179.in-addr.arpa. 3600 IN	NS	198.58.120.134.
;; Received 83 bytes from 179.61.195.24#53(NS9.HOST1PLUS.COM) in 200 ms

96.178.61.179.in-addr.arpa. 10800 IN	SOA	ns1.yournameserver.com. root.domain.com. 2007040301 14400 3600 604800 10800
;; Received 125 bytes from 198.58.120.134#53(198.58.120.134) in 192 ms

On the other hand

Code:

dig -x 179.61.178.96 

; <<>> DiG 9.12.1 <<>> -x 179.61.178.96
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 56574
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1
<-snip->

I used "correct" because the SOA RR is nonsense...
Use the example in post #4 along with a TTL in 1st line and a recent serial number, restart named and test!

dr.x · 05-04-2018, 12:11 PM

Guys any help ?

dr.x · 05-04-2018, 12:29 PM

here what i did :

$TTL 86400
@ IN SOA ns1.yournameserver.com. root.domain.com. (
2018050401 ;serial
14400 ;refresh
3600 ;retry
604800 ;expire
10800 ;minimum
)

96.178.61.179.in-addr.arpa. IN NS li654-134.members.linode.com.
96.178.61.179.in-addr.arpa. IN PTR li654-134.members.linode.com.

and named.conf same

same not working !

bathory · 05-04-2018, 01:17 PM

Quote:

@ IN SOA ns1.yournameserver.com. root.domain.com. (
<-snip->
96.178.61.179.in-addr.arpa. IN PTR li654-134.members.linode.com.

Why on earth don't you use the actual names? And now changed also the PTR RR!!
Use an $ORIGIN and the correct values for SOA this time:

Code:

$TTL 86400
$ORIGIN 96.178.61.179.in-addr.arpa.
@ IN SOA li654-134.members.linode.com. root.li654-134.members.linode.com. (
2018050402 ;serial ***I'VE ALREADY INCREASED IT BUT YOU MAY HAVE TO INCREASE IT FURTHER***
14400 ;refresh
3600 ;retry
604800 ;expire
10800 ;minimum
)

96.178.61.179.in-addr.arpa. IN NS li654-134.members.linode.com.
96.178.61.179.in-addr.arpa. IN PTR li654-134.members.linode.com.

Apart from that, you can run:

Code:

named-checkconf -z
named-checkzone 96.178.61.179.in-addr.arpa /var/named/178.61.179.in-addr.arpa

If it still doesn't work, perhaps you need to run a packet sniffer (tcpdump) and look for errors.

Quote:

Originally Posted by dr.x

Guys any help ?

And please don't bump your own threads.

dr.x · 05-12-2018, 12:21 PM

Guys i would like to say that i was able to have it working and i was able to setup Rdns on my own server .

i have other Question now , how can i let other sever to answer this Rdns ?

the record reach my server for Rdns check , then i will FWD it to other dns server and the other one answer the Rdns .

whats config do i need to modify ?

do i need to modify named.conf ?

or

the /var/named/xxx.in arp a file ?

regards

bathory · 05-12-2018, 05:17 PM

Quote:

Guys i would like to say that i was able to have it working and i was able to setup Rdns on my own server .

Why you say that it's working? From here looks like you made things worse!
You broke the delegation between your ISP dns and yours and now you have a loop:

Code:

dig +trace 96.178.61.179.in-addr.arpa

; <<>> DiG 9.12.1 <<>> +trace 96.178.61.179.in-addr.arpa
;; global options: +cmd
<-snip->
178.61.179.in-addr.arpa. 86400	IN	NS	NS8.HOST1PLUS.COM.
178.61.179.in-addr.arpa. 86400	IN	NS	NS10.HOST1PLUS.COM.
178.61.179.in-addr.arpa. 86400	IN	NS	NS9.HOST1PLUS.COM.
178.61.179.in-addr.arpa. 10800	IN	NSEC	179.61.179.in-addr.arpa. NS RRSIG NSEC
178.61.179.in-addr.arpa. 10800	IN	RRSIG	NSEC 5 5 10800 20180530142552 20180430142324 39315 179.in-addr.arpa. aBgCLjQOq3i9iQFLIEFo4jBuyr9iaO94YKLL+Y0kHEb8qEKmO9UuXFMa doEjHwT9ONcX4AeJZ4KsQ3ohFjC3x+SU3AFTlzHBuP86uHJwUcCIf8eo RJHStrRGSl/RzyQAoSnCJDHsi4/OvyldtBTH7crzvQA0Z/+SQn/4sKvn t3h4JIf4Of5j/2kekqwhzGghGUGve355H8EJX2WoVhbe1PchjQqvu3do Yq1CR+Wd0kknIEubOKzfuXxRXFNRvQ6YN7rgYM8m2sxq9duz3l/65SWh dCLMEArFLAlwzWsInR08Q3Yn9W+D1av3UGCrOIGx1bjJJrcquSC66zpn 8RpQCw==
;; Received 472 bytes from 200.3.13.10#53(ns.lacnic.net) in 290 ms

96.178.61.179.in-addr.arpa. 3600 IN	NS	198.58.120.134.
;; Received 83 bytes from 191.101.62.70#53(NS10.HOST1PLUS.COM) in 291 ms

96.178.61.179.in-addr.arpa. 3122 IN	NS	198.58.120.134.
;; BAD (HORIZONTAL) REFERRAL
;; Received 83 bytes from 198.58.120.134#53(198.58.120.134) in 213 ms
<-snip->
96.178.61.179.in-addr.arpa. 3117 IN	NS	198.58.120.134.
;; BAD (HORIZONTAL) REFERRAL
dig: too many lookups

dr.x · 05-13-2018, 06:39 AM

i see .
as i told you i just have the RDNS sent to my server and was able to have the PTR working 100 %

now i want to send the RDNS to other sever
i don't want to be responsible for the RDNS my side .
i will just be like transparent and send the RDNS to other server to answer it

can you help me out plz ?

i ready much much and no helping !!

I'm doing it on /24

kind regards

bathory · 05-13-2018, 10:12 AM

Quote:

now i want to send the RDNS to other sever
i don't want to be responsible for the RDNS my side .
i will just be like transparent and send the RDNS to other server to answer it

You should talk with your ISP, so he remove the delegation of that IP to your dns.