Hello David,
Am Sonntag, 15. August 2021, 13:40:00 CEST schrieb David Vasek:
Hello Günther,
khost -v ipa.4gjn.com.lan
and
host -v ipa.4gjn.com.lan
should shed some light on the issue.
yes ;-)
host -v ipa.4gjn.com.lan
Trying "ipa.4gjn.com.lan"
Host ipa.4gjn.com.lan not found: 3(NXDOMAIN)
Received 109 bytes from 217.196.154.211#53 in 9 ms
Received 109 bytes from 217.196.154.211#53 in 9 ms
host uses the third external server see resolv.conf ?
but khost use 127.0.0.1
[root@dns1 knot-resolver]# khost -v 192.168.100.204
;; ->>HEADER<<- opcode: QUERY; status: NOERROR; id: 10776
;; Flags: qr aa rd; QUERY: 1; ANSWER: 1; AUTHORITY: 0; ADDITIONAL: 0
;;204.100.168.192.in-addr.arpa. IN PTR
204.100.168.192.in-addr.arpa. 3600 IN PTR ipa.4gjn.com.lan.
;; Received 76 B
;; Time 2021-08-15 16:04:19 CEST
;; From 127.0.0.1@53(UDP) in 0.0 ms
[root@dns1 knot-resolver]# khost -v ipa.4gjn.com.lan
;; ->>HEADER<<- opcode: QUERY; status: NOERROR; id: 52255
;; Flags: qr aa rd; QUERY: 1; ANSWER: 1; AUTHORITY: 0; ADDITIONAL: 0
;;ipa.4gjn.com.lan. IN A
ipa.4gjn.com.lan. 86400 IN A 192.168.100.204
;; Received 50 B
;; Time 2021-08-15 16:04:40 CEST
;; From 127.0.0.1@53(UDP) in 0.0 ms
;; ->>HEADER<<- opcode: QUERY; status: NOERROR; id: 53725
;; Flags: qr aa rd; QUERY: 1; ANSWER: 0; AUTHORITY: 1; ADDITIONAL: 0
;;ipa.4gjn.com.lan. IN AAAA
4gjn.com.lan. 86400 IN SOA
dns1.4gjn.com. postmaster.
4gjn.com. 2021032801 3600 1800 604800 86400
;; Received 94 B
;; Time 2021-08-15 16:04:40 CEST
;; From 127.0.0.1@53(UDP) in 0.0 ms
;; ->>HEADER<<- opcode: QUERY; status: NOERROR; id: 32759
;; Flags: qr aa rd; QUERY: 1; ANSWER: 0; AUTHORITY: 1; ADDITIONAL: 0
;;ipa.4gjn.com.lan. IN MX
4gjn.com.lan. 86400 IN SOA
dns1.4gjn.com. postmaster.
4gjn.com. 2021032801 3600 1800 604800 86400
;; Received 94 B
;; Time 2021-08-15 16:04:40 CEST
;; From 127.0.0.1@53(UDP) in 0.0 ms
after more than 20 years of "bind" is it difficult to understand knot in a
"fast" way? I first have to find out how I can get my internal network up and
running again.
This problem aside, if you just need to serve that two
private static
zones for your local LAN only and resolve the rest of the Internet, it's
much more efficient to configure these two static zones in you resolver
(such as kresd/Knot Resolver or unbound) and avoid necessity to use an
authoritative server at all.
Regards,
David
On 2021-08-14 22:19, Günther J. Niederwimmer wrote:
> Hello David,
>
> Am Samstag, 14. August 2021, 18:36:11 CEST schrieb David Vasek:
>> Hello Günther,
>>
>> do you query the server from the same host in both cases? If so, may I
>> ask what's the contents of /etc/resolv.conf and what's your OS?
>
> yes this is from the same host, but all other host have the same
> problem with
> "host", on this servers I don't have a "khost"
>
> The OS is oracle Linux 8.4
>
> The resolv.conf
> cat /etc/resolv.conf
> # Generated by NetworkManager
> search 4gjn.com.lan
4gjn.com
> nameserver 127.0.0.1
> nameserver 192.168.100.221
> nameserver 217.196.154.211
>
>> > I am a newbie
>> > I have a problem with KNOT or I don't understand Knot?
>> >
>> > What do I have to configure so that knot also dissolves my internal
>> > zones?
>> > My config for the zones
>> > # Internal zone
>> >
>> > - domain: 4gjn.com.lan
>> >
>> > # notify: secondary
>> >
>> > file: "/var/lib/knot/zones/4gjn.com.lan.zone"
>> > dnssec-signing: off
>> > zonefile-sync: -1
>> > zonefile-load: difference
>> > journal-content: changes
>> >
>> > # master: primary1
>> > # acl: update_acl
>> >
>> > # Master zone
>> >
>> > - domain: 100.168.192.in-addr.arpa
>> >
>> > # notify: secondary
>> >
>> > file: "/var/lib/knot/zones/100.168.192.in-addr.arpa.zone"
>> > zonefile-sync: -1
>> > zonefile-load: difference
>> > journal-content: changes
>> > dnssec-signing: off
>> >
>> > # master: primary
>> > # acl: acl_secondary
>> > with khost I have this answer on the knot-server
>> > khost 192.168.100.204
>> > 204.100.168.192.in-addr.arpa. points to ipa.4gjn.com.lan.
>> > khost ipa.4gjn.com.lan
>> > ipa.4gjn.com.lan. has IPv4 address 192.168.100.204
>> >
>> > But with host do I get the answer back?
>> >
>> > host 192.168.100.204
>> > Host 204.100.168.192.in-addr.arpa. not found: 3 (NXDOMAIN)
>> > host ipa.4gjn.com.lan
>> > Host ipa.4gjn.com.lan not found: 3 (NXDOMAIN)
>> >
>> > is that correct or do I have an error?
>> >
>> > ping seems to work
>> > ping ipa.4gjn.com.lan
>> > PING ipa.4gjn.com.lan (192.168.100.204) 56 (84) bytes of data.
>> >
>> > Thanks for an answer,
--
mit freundlichen Grüßen / best regards
Günther J. Niederwimmer