Re: Name or Sevice not known - bind

2023-01-19 Thread Greg Wooledge
On Thu, Jan 19, 2023 at 09:12:19PM +0100, Maurizio Caloro wrote: > # host -t A pluto.sternbild.m 127.0.0.1 > Using domain server: > Name: 127.0.0.1 > Address: 127.0.0.1#53 > Aliases: > > Host pluto.sternbild.m not found: 3(NXDOMAIN) Hmm. In your previous message, you have: > # cat /etc/bind/nam

Re: Name or Sevice not known - bind

2023-01-19 Thread Maurizio Caloro
Am 19.01.2023 um 20:24 schrieb Greg Wooledge: On Thu, Jan 19, 2023 at 07:45:34PM +0100, Maurizio Caloro wrote: Let's start here. Why do you have multiple nameserver lines here? Which one is the bind9 server that you're configuring? That should be the only line. If the bind9 server is 127.0.0.1

Re: Name or Sevice not known - bind

2023-01-19 Thread Greg Wooledge
On Thu, Jan 19, 2023 at 07:45:34PM +0100, Maurizio Caloro wrote: > fighting little with bind9, on Debian 10.13, in my opinion appair right, but > # cat /etc/resolv.conf > search sternbild.m > nameserver 127.0.0.1 > nameserver A.B.C.D -> other Nameservers > nameserver A.B.C.D -> other Nameservers

Name or Sevice not known - bind

2023-01-19 Thread Maurizio Caloro
hello fighting little with bind9, on Debian 10.13, in my opinion appair right, but arn't possible to ping local/inside the Client that i have add to my config. information this machine running on a VPS envirment. also the checks are positiv # named-checkzone sternbild.m /var/cache/bind/db.ster