[Pdns-users] Issue with SOA request PDNS server

[Frank Louwers]

Hi Jhonny,

It seems like you're looking at the wrong zone. The error you get, is about the reverse delegation of the 200.7.160.0/20 subnet.

You do have 200.7.160.0/24 correctly set up:

 ❯ dig -x 200.7.160.0 soa @200.7.160.10 +norec
...
;; AUTHORITY SECTION:
160.7.200.in-addr.arpa.	3600	IN	SOA	marte.umsa.bo. root.umsa.bo. 10101804 3600 7200 86400 86400



But not the other 15 /24 blocks in that /20:

eg for 161.7.200.in-addr.arpa:

~ ❯ dig -x 200.7.161.0 soa @200.7.160.10 +norec
...
;; AUTHORITY SECTION:
161.7.200.in-addr.arpa.	3600	IN	SOA	a.misconfigured.dns.server.invalid. hostmaster.161.7.200.in-addr.arpa. 2022041104 10800 3600 604800 3600


or even worse for others:

~ ❯ dig -x 200.7.171.0 soa @200.7.160.10 +norec

;; ->>HEADER<<- opcode: QUERY, status: REFUSED, id: 15315
;; flags: qr; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;0.171.7.200.in-addr.arpa.	IN	SOA


I would recommend adding the other in-addr.arpa zones, and trying again.


Cheers,

Frank


> On 10 May 2022, at 17:56, Jhonny Paco via Pdns-users <pdns-users at mailman.powerdns.com> wrote:
> 
> Hi Jan-Piet
> 
> Thank you for your attention, but my problem is with (Internet Addresses Registry for Latin America and the Caribbean) --> LACNIC (https://query.milacnic.lacnic.net/search?id=200.7.160.10) --> and their QREFUSED report.
> 
> They are using automated tools to validate DIG answer and verify AUTHORITY SECTION detail.
> 
> Question:
> 
> Is it possible config PDNS server to show AUTHORITY SECTION?
> 
> If not posible, exist another option to acomplish LACNIC request?
> 
> It is my last email to day, no more...
> 
> Best Regards
> _______________________________________________
> Pdns-users mailing list
> Pdns-users at mailman.powerdns.com
> https://mailman.powerdns.com/mailman/listinfo/pdns-users

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.powerdns.com/pipermail/pdns-users/attachments/20220510/47883c4c/attachment.htm>