<br>;; ANSWER SECTION:<br><a href=3D"http://google.com" target=3D"_blank= ">google.com</a>. 300 IN A 216.58.211.142<br><br>;; Query time: 179 msec<b=7 EDT 2020<br>;; MSG SIZE =C2=A0rcvd: 83<br></span></span></p><p class=3D"M= soNormal" style=3D"margin:0cm 0cm 8pt;line-height:107%;font-size:11pt;font-= family:"Calibri",sans-serif"><span lang=3D"EN-US"><span></span></= span></p><p class=3D"MsoNormal" style=3D"margin:0cm 0cm 8pt;line-height:107= %;font-size:11pt;font-family:"Calibri",sans-serif"><span lang=3D"= EN-US"><span>
;; SERVER: 192.168.14.10#53(192.168.14.10)<br>;; WHEN: Fri Jul 17 15:03:2=
86400 ; Retry<br> 2419200 ; Expire 28days<br> 604800 ; Negative=Cache TTL<br>)<br>;; name servers (NS)<br>;; only authoritative servers<br=
@ =C2=A0 =C2=A0 IN NS ns2.example.home.<br>ns2 IN A 192.168.14.20<br>;; =hosts (A)<br>ns1 =C2=A0 =C2=A0 =C2=A0 =C2=A0 IN =C2=A0A =C2=A0 192.168.14.1= 0<br>c1 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0IN =C2=A0A =C2=A0 192.168.14.1<br= ><br>;; alias (CNAME)<br>client IN CNAME c1</p><p class=3D"MsoNormal" sty=
On 18 Jul 2020, at 05:18, Weeltin <weeltinl@gmail.com> wrote:
Hello all,
I’m trying to implement a DNS structure, containing a recursive and authoritative server, but in doing so, I have run into a small problem. I can make DNS queries from a client toward the net, but when I try to do the same toward my internal domain, I get no result. I have spent days trying to figure out what is going on, but to no avail, I there for hope that someone on this list can point me in the right direction or right out tell what is wrong.
/Weeltin.
-----DIG troubleshoots
[weeltin@c1 ~]$ cat /etc/resolv.conf
# Generated by NetworkManager
nameserver 192.168.14.10
[weeltin@c1 ~]$ dig google.com
; <<>> DiG 9.11.11-RedHat-9.11.11-1.fc31 <<>> google.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 48932
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
; COOKIE: c1bc4a11c40bd755905c8c705f11f5ffe699cc0116ed8ba5 (good)
;; QUESTION SECTION:
;google.com. IN A
;; ANSWER SECTION:
google.com. 300 IN A 216.58.211.142
;; Query time: 179 msec
;; SERVER: 192.168.14.10#53(192.168.14.10)
;; WHEN: Fri Jul 17 15:03:27 EDT 2020
;; MSG SIZE rcvd: 83
[weeltin@c1 ~]$ dig c1.example.home
; <<>> DiG 9.11.11-RedHat-9.11.11-1.fc31 <<>> c1.example.home
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 62602
;; flags: qr rd ra ad; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
; COOKIE: cf8876e3b35138f47040188e5f11f64a91445aa4f8310f5a (good)
;; QUESTION SECTION:
;c1.example.home. IN A
;; AUTHORITY SECTION:
. 10800 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2020071701 1800 900 604800 86400
;; Query time: 263 msec
;; SERVER: 192.168.14.10#53(192.168.14.10)
;; WHEN: Fri Jul 17 15:04:42 EDT 2020
;; MSG SIZE rcvd: 147
[weeltin@c1 ~]$ dig @192.168.14.20 c1.example.home
; <<>> DiG 9.11.11-RedHat-9.11.11-1.fc31 <<>> @192.168.14.20 c1.example.home ; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 20704
;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; WARNING: recursion requested but not available
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
; COOKIE: 747289c94876cf349034aec35f11f794a29c6747bb6a694f (good)
;; QUESTION SECTION:
;c1.example.home. IN A
;; ANSWER SECTION:
c1.example.home. 604800 IN A 192.168.14.1
;; Query time: 0 msec
;; SERVER: 192.168.14.20#53(192.168.14.20)
;; WHEN: Fri Jul 17 15:10:12 EDT 2020
;; MSG SIZE rcvd: 88
----- informations and configurations ----
OS: Alpine 3.12
Bind: bind 9.14.12
Ns1: 192.168.14.10 (recursive)
Ns2: 192.168.14.20 (authoritative)
C1: 192.168.14.1 (client)
--- recursive config (NS1)
// recursive named.conf
//
acl trusted {
192.168.14.0/24;
localhost;
};
acl rfc1918 {
10.0.0.0/8;
172.16.0.0/12;
!192.168.14.0/24;
192.168.0.0/16;
};
acl rfc5735 {
0.0.0.0/8;
169.254.0.0/16;
192.0.0.0/24;
192.0.2.0/24;
192.88.99.0/24;
198.18.0.0/15;
198.51.100.0/24;
203.0.113.0/24;
224.0.0.0/4;
};
options {
directory "/var/bind";
listen-on {
127.0.0.1;
192.168.14.10;
};
listen-on-v6 {
none;
};
allow-query {
trusted;
};
//query-source address * port 53;
allow-query-cache {
trusted;
};
blackhole {
rfc1918;
rfc5735;
};
allow-transfer {
none;
};
pid-file "/var/run/named/named.pid";
// Changing this is NOT RECOMMENDED; see the notes above and in
// named.conf.recursive.
allow-recursion {
trusted;
};
recursion yes;
};
zone "." IN {
type hint;
file "root.cache";
};
zone "localhost" IN {
type master;
file "pri/localhost.zone";
allow-update { none; };
notify no;
};
zone "127.in-addr.arpa" IN {
type master;
file "pri/127.zone";
allow-update { none; };
notify no;
};
zone "example.home" {
type forward;
forwarders { 192.168.14.20; };
};
--- authoritative config (NS2)
// authoritative named.conf
//
acl trusted {
192.168.14.0/24;
localhost;
};
acl rfc1918 {
10.0.0.0/8;
172.16.0.0/12;
!192.168.14.0/24;
192.168.0.0/16;
};
acl rfc5735 {
0.0.0.0/8;
169.254.0.0/16;
192.0.0.0/24;
192.0.2.0/24;
192.88.99.0/24;
198.18.0.0/15;
198.51.100.0/24;
203.0.113.0/24;
224.0.0.0/4;
};
options {
directory "/var/bind";
// Configure the IPs to listen on here.
listen-on {
127.0.0.1;
192.168.14.20;
};
listen-on-v6 {
none;
};
allow-query {
trusted;
};
//query-source address * port 53;
allow-query-cache {
trusted;
};
blackhole {
rfc5735;
rfc1918;
};
allow-transfer {
none;
};
// Cryptographic authentication of DNS information
// ENABLE LATER
//dnssec-enable yes;
//dnssec-validation yes;
pid-file "/var/run/named/named.pid";
// Changing this is NOT RECOMMENDED for a authoritative nameserver
allow-recursion { none; };
recursion no;
};
zone "example.home" {
type master;
file "/etc/bind/db.example.home.zone";
};
zone "14.168.192.in-addr.arpa" {
type master;
file "/etc/bind/db.14.168.192.zone";
};
; ZONE file for example.home.
;
$TTL 604800
@ IN SOA ns2.example.home. hostmaster.example.home. (
2 ; Serial
604800 ; Refresh 1week
86400 ; Retry
2419200 ; Expire 28days
604800 ; Negative Cache TTL
)
;; name servers (NS)
;; only authoritative servers
@ IN NS ns2.example.home.
ns2 IN A 192.168.14.20
;; hosts (A)
ns1 IN A 192.168.14.10
c1 IN A 192.168.14.1
;; alias (CNAME)
client IN CNAME c1
; ZONE file for 14.168.192.in-addr.arpa.
;
$TTL 604800
@ IN SOA ns2.example.home. hostmaster.example.home. (
1 ; Serial
604800 ; Refresh 1week
86400 ; Retry
2419200 ; Expire 28days
604800 ; Negative Cache TTL
)
;; name servers (NS)
;; only authoritative servers
@ IN NS ns2.example.home.
20 IN PTR ns2.example.home.
;; pointer records (PTR)
1 IN PTR c1.example.home.
10 IN PTR ns1.example.home.
_______________________________________________
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list
ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information.
bind-users mailing list--
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
Your problem comes from the fact that BIND 9.14 has DNSSEC validationnd
enabled by default (unless disabled at configure time or in named.conf) a=
the answers from the grafted on namespace (.home) fail DNSSEC validation =as
there is not a insecure delegation for .home to break the DNSSEC chain of trust. You can use validate-except to teach there recursive server to no=t
validate parts of the namespace but it is NOT RECOMMENDED as it doesn=E2==80=99t
help validating clients.a
e.g.
validate-except { home; };
I would stop trying to use .home as it has not been delegated for home
use. Use home.arpa instead which has been reserved for home use and has =
insecure delegation to break the DNSSEC chain of trust pointing at server=s
which only return NXDOMAIN for names under home.arpa. This is the same delegation model used for the RFC 1918 reverse zone. Note that DS isEC
absent from the list of types at the delegation point in the NSEC record. There was an attempt made to delegate .home this way but it floundered on ICANN/IETF politics.
e.g.
home.arpa. 172800 IN NS blackhole-1.iana.org. home.arpa. 172800 IN NS blackhole-2.iana.org. home.arpa. 86400 IN NSEC in-addr.arpa. NS RRSIG NS=
home.arpa. 86400 IN RRSIG NSEC 8 2 86400y;=E2=80=9D as
20200731120000 20200718110000 57156 arpa. lSqLNz1E/6WkAUDAJDnvo9X248B+PAWM34s0S0PJFjPi4YLoE//6zSR6 Dgm0T+2qV2KrgvYbOzHV9Z/lRopFxSEJSSwoHgrUmfofXmIbQiKgQHBi g9dvL8yeJm0cRe6QMuM1q/D/3+AnPv5OQNBhC6+UEA+enO3JtDbvjr/H XfPPvfDfozacZkHPe+AYpJbmT7qfHv8Gw/BeeNtDex9jMoDbJ2l0BLT1 UTPKE9+Abrh3RawcKBF3BbLNWU6AhIkOLZRADGMjcZg1M/IHUk/rOWXV EMZihg1+5I4GSmaRDN0jTX9g5jr822EZfaZLmCKlcGYMMHVOkMUA7k0r +v/Zrg=3D=3D
If you are using forward zones (not recommended) set =E2=80=9Cforward onl=
you don=E2=80=99t want to fallback to querying servers on the global Inte=rnet when
grafting on namespace. If you do use a forward zone then the servers bei=ng
forwarded to need to either a) serve the *entire* namespace under thes
forward zone, or b) be configured as recursive servers.
zone home.arpa {
type forward;
forward only;
forwarders {192.168.14.20;};
};
I would recommend using secondary zone rather than forward zones for
grafting on namespaces, just ensure that the all slave servers are
receiving NOTIFY messages (use also-notify) so that they receive changes fast. Fast propagation of changes is needed in a home environment.
Secondary zone also provide a break in the DNSSEC chain of trust as far a=
the recursive server is concerned. They however do not break the DNSSEC chain of trust for any DNSSEC validating clients of the recursive server.o the
zone home.arpa {
type secondary;
primaries {192.168.14.20;};
file =E2=80=9Chome.arpa.db=E2=80=9D;
...
};
zone home.arpa {
type primary;
file =E2=80=9Chome.arpa.db=E2=80=9D;
also-notify { address list; };
...
};
Also forget any garbage that recursive servers should not also serve
zones. People have take the advice that listed authoritative servers shouldn=E2=80=99t be recursive (which is good advise when serving zones t=
public) and inverted it to come up with bad advice.and
Mark
On 18 Jul 2020, at 05:18, Weeltin <weeltinl@gmail.com> wrote:
Hello all,
I=E2=80=99m trying to implement a DNS structure, containing a recursive=
authoritative server, but in doing so, I have run into a small problem. Ihe
can make DNS queries from a client toward the net, but when I try to do t=
same toward my internal domain, I get no result. I have spent days tryingl
to figure out what is going on, but to no avail, I there for hope that someone on this list can point me in the right direction or right out tel=
what is wrong.
/Weeltin.
-----DIG troubleshoots
[weeltin@c1 ~]$ cat /etc/resolv.conf
# Generated by NetworkManager
nameserver 192.168.14.10
[weeltin@c1 ~]$ dig google.com
; <<>> DiG 9.11.11-RedHat-9.11.11-1.fc31 <<>> google.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 48932
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
; COOKIE: c1bc4a11c40bd755905c8c705f11f5ffe699cc0116ed8ba5 (good)
;; QUESTION SECTION:
;google.com. IN A
;; ANSWER SECTION:
google.com. 300 IN A 216.58.211.142
;; Query time: 179 msec
;; SERVER: 192.168.14.10#53(192.168.14.10)
;; WHEN: Fri Jul 17 15:03:27 EDT 2020
;; MSG SIZE rcvd: 83
m.[weeltin@c1 ~]$ dig c1.example.home
; <<>> DiG 9.11.11-RedHat-9.11.11-1.fc31 <<>> c1.example.home
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 62602
;; flags: qr rd ra ad; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
; COOKIE: cf8876e3b35138f47040188e5f11f64a91445aa4f8310f5a (good)
;; QUESTION SECTION:
;c1.example.home. IN A
;; AUTHORITY SECTION:
. 10800 IN SOA a.root-servers.net. nstld.verisign-grs.co=
2020071701 1800 900 604800 86400
;; Query time: 263 msec
;; SERVER: 192.168.14.10#53(192.168.14.10)
;; WHEN: Fri Jul 17 15:04:42 EDT 2020
;; MSG SIZE rcvd: 147
[weeltin@c1 ~]$ dig @192.168.14.20 c1.example.home
; <<>> DiG 9.11.11-RedHat-9.11.11-1.fc31 <<>> @192.168.14.20c1.example.home
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 20704
;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; WARNING: recursion requested but not available
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
; COOKIE: 747289c94876cf349034aec35f11f794a29c6747bb6a694f (good)
;; QUESTION SECTION:
;c1.example.home. IN A
;; ANSWER SECTION:
c1.example.home. 604800 IN A 192.168.14.1
;; Query time: 0 msec
;; SERVER: 192.168.14.20#53(192.168.14.20)
;; WHEN: Fri Jul 17 15:10:12 EDT 2020
;; MSG SIZE rcvd: 88
----- informations and configurations ----
OS: Alpine 3.12
Bind: bind 9.14.12
Ns1: 192.168.14.10 (recursive)
Ns2: 192.168.14.20 (authoritative)
C1: 192.168.14.1 (client)
--- recursive config (NS1)
// recursive named.conf
//
acl trusted {
192.168.14.0/24;
localhost;
};
acl rfc1918 {
10.0.0.0/8;
172.16.0.0/12;
!192.168.14.0/24;
192.168.0.0/16;
};
acl rfc5735 {
0.0.0.0/8;
169.254.0.0/16;
192.0.0.0/24;
192.0.2.0/24;
192.88.99.0/24;
198.18.0.0/15;
198.51.100.0/24;
203.0.113.0/24;
224.0.0.0/4;
};
options {
directory "/var/bind";
listen-on {
127.0.0.1;
192.168.14.10;
};
listen-on-v6 {
none;
};
allow-query {
trusted;
};
//query-source address * port 53;
allow-query-cache {
trusted;
};
blackhole {
rfc1918;
rfc5735;
};
allow-transfer {
none;
};
pid-file "/var/run/named/named.pid";
// Changing this is NOT RECOMMENDED; see the notes above and in
// named.conf.recursive.
allow-recursion {
trusted;
};
recursion yes;
};
zone "." IN {
type hint;
file "root.cache";
};
zone "localhost" IN {
type master;
file "pri/localhost.zone";
allow-update { none; };
notify no;
};
zone "127.in-addr.arpa" IN {
type master;
file "pri/127.zone";
allow-update { none; };
notify no;
};
zone "example.home" {
type forward;
forwarders { 192.168.14.20; };
};
--- authoritative config (NS2)
// authoritative named.conf
//
acl trusted {
192.168.14.0/24;
localhost;
};
acl rfc1918 {
10.0.0.0/8;
172.16.0.0/12;
!192.168.14.0/24;
192.168.0.0/16;
};
acl rfc5735 {
0.0.0.0/8;
169.254.0.0/16;
192.0.0.0/24;
192.0.2.0/24;
192.88.99.0/24;
198.18.0.0/15;
198.51.100.0/24;
203.0.113.0/24;
224.0.0.0/4;
};
options {
directory "/var/bind";
// Configure the IPs to listen on here.
listen-on {
127.0.0.1;
192.168.14.20;
};
listen-on-v6 {
none;
};
allow-query {
trusted;
};
//query-source address * port 53;
allow-query-cache {
trusted;
};
blackhole {
rfc5735;
rfc1918;
};
allow-transfer {
none;
};
// Cryptographic authentication of DNS information
// ENABLE LATER
//dnssec-enable yes;
//dnssec-validation yes;
pid-file "/var/run/named/named.pid";
// Changing this is NOT RECOMMENDED for a authoritativenameserver
allow-recursion { none; };
recursion no;
};
zone "example.home" {
type master;
file "/etc/bind/db.example.home.zone";
};
zone "14.168.192.in-addr.arpa" {
type master;
file "/etc/bind/db.14.168.192.zone";
};
; ZONE file for example.home.
;
$TTL 604800
@ IN SOA ns2.example.home. hostmaster.example.home. (
2 ; Serial
604800 ; Refresh 1week
86400 ; Retry
2419200 ; Expire 28days
604800 ; Negative Cache TTL
)
;; name servers (NS)
;; only authoritative servers
@ IN NS ns2.example.home.
ns2 IN A 192.168.14.20
;; hosts (A)
ns1 IN A 192.168.14.10
c1 IN A 192.168.14.1
;; alias (CNAME)
client IN CNAME c1
; ZONE file for 14.168.192.in-addr.arpa.
;
$TTL 604800
@ IN SOA ns2.example.home. hostmaster.example.home. (
1 ; Serial
604800 ; Refresh 1week
86400 ; Retry
2419200 ; Expire 28days
604800 ; Negative Cache TTL
)
;; name servers (NS)
;; only authoritative servers
@ IN NS ns2.example.home.
20 IN PTR ns2.example.home.
;; pointer records (PTR)
1 IN PTR c1.example.home.
10 IN PTR ns1.example.home.
_______________________________________________unsubscribe from this list
Please visit https://lists.isc.org/mailman/listinfo/bind-users to
ISC funds the development of this software with paid supportsubscriptions. Contact us at https://www.isc.org/contact/ for more information.
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
--
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742 INTERNET: marka@isc.org
When querying your internal domain, I see the query actually ends with =E2=80=9Crecursion requested but not available=E2=80=9D, it looks like yo=u are querying
directly against your auth server, so I would check the setting to ensure
the zone file is actually loaded correctly.
What Mark answered is assuming you are querying the recursive which then returned SERVFAIL due to DNSSEC validation, but I do not see that in the information you provided.
Can you run dig on the auth server itself, dig @ 127.0.0.1 for
example.home, and see what it returns?
;; AUTHORITY SECTION:<br>. 10800 IN SOA <a href=3D"http://a.root-servers=.net">a.root-servers.net</a>. <a href=3D"http://nstld.verisign-grs.com">nst= ld.verisign-grs.com</a>. 2020072000 1800 900 604800 86400<br><br>;; Query t= ime: 1043 msec<br>;; SERVER: 192.168.14.10#53(192.168.14.10)<br>;; WHEN: Mo=
named[4022]: insecurity proof failed resolving 'c1.example.home/A/IN=': 192.168.14.20#53<br></truncate><br><br>and there is no log ent= ries on the authoritative server</div><div dir=3D"ltr"><br></div><div>/Weel= tin<br></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail= _attr">On Sun, Jul 19, 2020 at 6:05 AM Josh Kuo <<a href=3D"mailto:josh.= kuo@gmail.com">josh.kuo@gmail.com</a>> wrote:<br></div><blockquote class= =3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rg= b(204,204,204);padding-left:1ex"><div><div dir=3D"auto">When querying your = internal domain, I see the query actually ends with =E2=80=9Crecursion requ= ested but not available=E2=80=9D, it looks like you are querying directly a= gainst your auth server, so I would check the setting to ensure the zone fi=
From what you posted, it appears when you query the recursive server NS1 (192.168.14.10), it returns no error, it gives back NXDOMAIN with the ADflag. That would indicate DNSSEC worked. That does not match the log
Hi Josh,o
Thanks for your answer, it made me go trough all the config again, just t=
make sure that it wasnt pointing to the authoritative server anywhere buthe query
in the configuration of the recursive server
I saw that "=E2=80=9Crecursion requested but not available" when i send t=
against the authoritative. Kind a expected that, since it aint allowed to
do recursion.
as requested i made the dig on the the authoritative server i get the
correct answer, so i expect it has loaded the zonefiles correctly.
ns2:/home/weeltin# dig @127.0.0.01 example.home
; <<>> DiG 9.14.12 <<>> @127.0.0.01 example.home
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 45487
;; flags: qr aa rd; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
;; WARNING: recursion requested but not available
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
; COOKIE: b9129ece5d9fbc3e6f01a2215f15a461388d4af048be37fa (good)
;; QUESTION SECTION:
;example.home. IN A
;; AUTHORITY SECTION:
example.home. 604800 IN SOA ns2.example.home. hostmaster.example.home. 2 604800 86400 2419200 604800
;; Query time: 0 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Mon Jul 20 14:04:17 UTC 2020
;; MSG SIZE rcvd: 120
just to be sure, i rand the dig command again on my client
[weeltin@c1 ~]$ dig c1.example.home
; <<>> DiG 9.11.11-RedHat-9.11.11-1.fc31 <<>> c1.example.home
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 1787
;; flags: qr rd ra ad; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
; COOKIE: 862cc48a975a32a324cd14e65f15ba5e3f2c972d1f753586 (good)
;; QUESTION SECTION:
;c1.example.home. IN A
;; AUTHORITY SECTION:
. 10800 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2020072000
1800 900 604800 86400
;; Query time: 1043 msec
;; SERVER: 192.168.14.10#53(192.168.14.10)
;; WHEN: Mon Jul 20 11:38:06 EDT 2020
;; MSG SIZE rcvd: 147
Log output from NS1 (recursive)ou are querying
<truncate>
Jul 20 15:38:05 ns1 daemon.info named[4022]: validating
example.home/SOA: got insecure response; parent indicates it should be
secure
Jul 20 15:38:05 ns1 daemon.info named[4022]: no valid RRSIG resolving 'c1.example.home/DS/IN': 192.168.14.20#53
Jul 20 15:38:06 ns1 daemon.info named[4022]: insecurity proof failed resolving 'c1.example.home/A/IN': 192.168.14.20#53
</truncate>
and there is no log entries on the authoritative server
/Weeltin
On Sun, Jul 19, 2020 at 6:05 AM Josh Kuo <josh.kuo@gmail.com> wrote:
When querying your internal domain, I see the query actually ends with
=E2=80=9Crecursion requested but not available=E2=80=9D, it looks like y=
edirectly against your auth server, so I would check the setting to ensur=
the zone file is actually loaded correctly.
What Mark answered is assuming you are querying the recursive which then
returned SERVFAIL due to DNSSEC validation, but I do not see that in the
information you provided.
Can you run dig on the auth server itself, dig @ 127.0.0.1 for
example.home, and see what it returns?
Sysop: | DaiTengu |
---|---|
Location: | Appleton, WI |
Users: | 970 |
Nodes: | 10 (2 / 8) |
Uptime: | 105:46:25 |
Calls: | 12,740 |
Calls today: | 2 |
Files: | 186,574 |
Messages: | 3,171,706 |