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. 3600IN
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 veri
dig @200.7.160.10 umsa.bo soa +norec
That server is responding authoritatively (flags: AA), which is fine.
Please, tell me How can I to change or to config PDNS to get SOA request.
by querying for the SOA request as you did above.
Running the command dig doesn't show
AUTHORITY SECTION and
Hi Jan-Piet
Thank you, for you answer.
Ok the real query is:
dig @200.7.160.10 umsa.bo soa +norec
where:
IP address 200.7.160.10 is a master public DNS server.
umsa.bo: is real domain registered in LACNIC
Running the command dig doesn't show
AUTHORITY SECTION and ADDITIONAL SECTION
L
On 10/05/2022 09:17, Jan-Piet Mens via Pdns-users wrote:
dig @127.0.0.1 zone-name.bo soa +norec
zone-name.bo is NXDOMAIN.
The longer version of that answer is here:
https://blog.powerdns.com/2016/01/18/open-source-support-out-in-the-open/
___
Pdn
dig @127.0.0.1 zone-name.bo soa +norec
zone-name.bo is NXDOMAIN.
-JP
___
Pdns-users mailing list
Pdns-users@mailman.powerdns.com
https://mailman.powerdns.com/mailman/listinfo/pdns-users
