Can’t bind to ‘formGroup’ since it isn’t a known property of ‘form’

Angular: 7
Есть компонент для входа в приложение. Получаю ошибку:

Uncaught Error: Template parse errors: Can’t bind to ‘formGroup’ since it isn’t a known property of ‘form’.

HTML:

<form [formGroup]="loginForm" novalidate (ngSubmit)="authenticate()">     <div class="row m-1">         <div class="col-sm-3 col-md-2 col-lg-1">             <span>Email:</span>         </div>         <div class="col-sm-4">             <input class="form-control"                    placeholder="Email"                    formControlName="email"                    name="email">         </div>     </div>      <div class="row m-1">         <div class="col-sm-3 col-md-2 col-lg-1">             <span>Password:</span>         </div>         <div class="col-sm-4">             <input class="form-control"                    placeholder="Password"                    formControlName="password"                    name="password">         </div>     </div>      <div class="row m-1">         <div class="col">             <button class="btn btn-primary"                     [disabled]="loginForm.invalid">                 Log in             </button>         </div>     </div> </form> 

TS:

import { Component, OnInit } from '@angular/core'; import { AuthenticationService } from "../shared/authentication.service"; import { Router } from "@angular/router"; import { FormBuilder, FormGroup, Validators } from "@angular/forms";  @Component({     selector: 'cts-login',     templateUrl: './login.component.html',     styleUrls: ['./login.component.sass'] }) export class LoginComponent implements OnInit {     loginForm: FormGroup;      constructor(private authService: AuthenticationService,                 private formBuilder: FormBuilder) {         this.loginForm = formBuilder.group({             email: ['', [Validators.required, Validators.email]],             password: ['', [Validators.required]]         })     }      ngOnInit() { }      authenticate() {         console.log(this.loginForm);     } } 

nginx bind() to 0.0.0.0:443 failed (48: Address already in use)

I have Laravel Valet 2.1.6 installed on Mac OS 10.14.2.

nginx 1.15.8 is installed using brew.

I restarted my Mac without installing any updates or new software, and now all example.test sites are giving a 502 error with the following showing in the /usr/local/var/log/nginx/error.log log:

2019/01/17 20:38:47 [warn] 31277#0: the "user" directive makes sense only if the master process runs with super-user privileges, ignored in /usr/local/etc/nginx/nginx.conf:1 2019/01/17 20:38:47 [emerg] 31277#0: bind() to 0.0.0.0:443 failed (48: Address already in use) 2019/01/17 20:38:47 [emerg] 31277#0: bind() to 0.0.0.0:443 failed (48: Address already in use) 2019/01/17 20:38:47 [emerg] 31277#0: bind() to 0.0.0.0:443 failed (48: Address already in use) 2019/01/17 20:38:47 [emerg] 31277#0: bind() to 0.0.0.0:443 failed (48: Address already in use) 2019/01/17 20:38:47 [emerg] 31277#0: bind() to 0.0.0.0:443 failed (48: Address already in use) 2019/01/17 20:38:47 [emerg] 31277#0: still could not bind() 

At the same time, I get the following in the /Users/Myself/.config/valet/Log/nginx-error.log log:

2019/01/17 20:41:34 [error] 32071#0: *1 upstream prematurely closed connection while reading response header from upstream, client: 127.0.0.1, server: example.test, request: "GET / HTTP/2.0", upstream: "fastcgi://unix:/Users/Myself/.config/valet/valet.sock:", host: "example.test" 

When I run ps ax -o pid,ppid,%cpu,vsz,wchan,command|egrep '(nginx|PID)' I see this list:

  PID  PPID  %CPU      VSZ WCHAN  COMMAND 32064     1   0.0  4306660 -      nginx: master process /usr/local/opt/nginx/bin/nginx -g daemon off; 32065 32064   0.0  4333284 -      nginx: worker process 32066 32064   0.0  4332260 -      nginx: worker process 32067 32064   0.0  4333284 -      nginx: worker process 32068 32064   0.0  4333284 -      nginx: worker process 32069 32064   0.0  4326116 -      nginx: worker process 32070 32064   0.0  4316900 -      nginx: worker process 32071 32064   0.0  4368236 -      nginx: worker process 32072 32064   0.0  4331236 -      nginx: worker process 32073 32064   0.0  4326116 -      nginx: worker process 32074 32064   0.0  4340452 -      nginx: worker process 32075 32064   0.0  4333284 -      nginx: worker process 32076 32064   0.0  4334308 -      nginx: worker process 36815  1406   0.0  4268060 -      egrep (nginx|PID) 

None of the following solves the issue:

  • sudo killall nginx
  • brew services restart nginx
  • brew services restart php
  • valet restart
  • Restarting my Mac
  • valet uninstall && valet install then valet park on the relevant dir

Apache is not running as a conflicting service.

I tried doing sudo /usr/local/opt/nginx/bin/nginx -g 'daemon off;' and got this:

nginx: [emerg] bind() to 0.0.0.0:80 failed (48: Address already in use) nginx: [emerg] bind() to 0.0.0.0:443 failed (48: Address already in use) nginx: [emerg] bind() to 0.0.0.0:60 failed (48: Address already in use) nginx: [emerg] bind() to 0.0.0.0:80 failed (48: Address already in use) nginx: [emerg] bind() to 0.0.0.0:443 failed (48: Address already in use) nginx: [emerg] bind() to 0.0.0.0:60 failed (48: Address already in use) nginx: [emerg] bind() to 0.0.0.0:80 failed (48: Address already in use) nginx: [emerg] bind() to 0.0.0.0:443 failed (48: Address already in use) nginx: [emerg] bind() to 0.0.0.0:60 failed (48: Address already in use) nginx: [emerg] bind() to 0.0.0.0:80 failed (48: Address already in use) nginx: [emerg] bind() to 0.0.0.0:443 failed (48: Address already in use) nginx: [emerg] bind() to 0.0.0.0:60 failed (48: Address already in use) nginx: [emerg] bind() to 0.0.0.0:80 failed (48: Address already in use) nginx: [emerg] bind() to 0.0.0.0:443 failed (48: Address already in use) nginx: [emerg] bind() to 0.0.0.0:60 failed (48: Address already in use) nginx: [emerg] still could not bind() 

Running sudo lsof -i tcp:80 produces:

COMMAND   PID USER   FD   TYPE             DEVICE SIZE/OFF NODE NAME nginx   42220 root    7u  IPv4 0x7ac8eae7874ccb11      0t0  TCP *:http (LISTEN) nginx   42221 Myself    7u  IPv4 0x7ac8eae7874ccb11      0t0  TCP *:http (LISTEN) nginx   42222 Myself    7u  IPv4 0x7ac8eae7874ccb11      0t0  TCP *:http (LISTEN) nginx   42223 Myself    7u  IPv4 0x7ac8eae7874ccb11      0t0  TCP *:http (LISTEN) nginx   42224 Myself    7u  IPv4 0x7ac8eae7874ccb11      0t0  TCP *:http (LISTEN) nginx   42225 Myself    7u  IPv4 0x7ac8eae7874ccb11      0t0  TCP *:http (LISTEN) nginx   42226 Myself    7u  IPv4 0x7ac8eae7874ccb11      0t0  TCP *:http (LISTEN) nginx   42227 Myself    7u  IPv4 0x7ac8eae7874ccb11      0t0  TCP *:http (LISTEN) nginx   42228 Myself    7u  IPv4 0x7ac8eae7874ccb11      0t0  TCP *:http (LISTEN) nginx   42229 Myself    7u  IPv4 0x7ac8eae7874ccb11      0t0  TCP *:http (LISTEN) nginx   42230 Myself    7u  IPv4 0x7ac8eae7874ccb11      0t0  TCP *:http (LISTEN) nginx   42231 Myself    7u  IPv4 0x7ac8eae7874ccb11      0t0  TCP *:http (LISTEN) nginx   42232 Myself    7u  IPv4 0x7ac8eae7874ccb11      0t0  TCP *:http (LISTEN) 

Basically the same output when I run that command for port 443.

This valet issue post suggests valet domain test might fix it, but that didn’t help.

Tried reinstalling PHP but no luck:

  • brew uninstall –force php
  • brew cleanup
  • brew install php
  • valet uninstall && valet install

Laravel valet bind() to 0.0.0.0:443 failed (48: Address already in use)

I have Laravel Valet 2.1.6 installed on Mac OS 10.14.2.

nginx 1.15.8 is installed using brew.

I restarted my Mac without installing any updates or new software, and now all example.test sites are giving a 502 error with the following showing in the /usr/local/var/log/nginx/error.log log:

2019/01/17 20:38:47 [warn] 31277#0: the "user" directive makes sense only if the master process runs with super-user privileges, ignored in /usr/local/etc/nginx/nginx.conf:1 2019/01/17 20:38:47 [emerg] 31277#0: bind() to 0.0.0.0:443 failed (48: Address already in use) 2019/01/17 20:38:47 [emerg] 31277#0: bind() to 0.0.0.0:443 failed (48: Address already in use) 2019/01/17 20:38:47 [emerg] 31277#0: bind() to 0.0.0.0:443 failed (48: Address already in use) 2019/01/17 20:38:47 [emerg] 31277#0: bind() to 0.0.0.0:443 failed (48: Address already in use) 2019/01/17 20:38:47 [emerg] 31277#0: bind() to 0.0.0.0:443 failed (48: Address already in use) 2019/01/17 20:38:47 [emerg] 31277#0: still could not bind() 

At the same time, I get the following in the /Users/Myself/.config/valet/Log/nginx-error.log log:

2019/01/17 20:41:34 [error] 32071#0: *1 upstream prematurely closed connection while reading response header from upstream, client: 127.0.0.1, server: vshred.test, request: "GET / HTTP/2.0", upstream: "fastcgi://unix:/Users/Myself/.config/valet/valet.sock:", host: "example.test" 

When I run ps ax -o pid,ppid,%cpu,vsz,wchan,command|egrep '(nginx|PID)' I see this list:

  PID  PPID  %CPU      VSZ WCHAN  COMMAND 32064     1   0.0  4306660 -      nginx: master process /usr/local/opt/nginx/bin/nginx -g daemon off; 32065 32064   0.0  4333284 -      nginx: worker process 32066 32064   0.0  4332260 -      nginx: worker process 32067 32064   0.0  4333284 -      nginx: worker process 32068 32064   0.0  4333284 -      nginx: worker process 32069 32064   0.0  4326116 -      nginx: worker process 32070 32064   0.0  4316900 -      nginx: worker process 32071 32064   0.0  4368236 -      nginx: worker process 32072 32064   0.0  4331236 -      nginx: worker process 32073 32064   0.0  4326116 -      nginx: worker process 32074 32064   0.0  4340452 -      nginx: worker process 32075 32064   0.0  4333284 -      nginx: worker process 32076 32064   0.0  4334308 -      nginx: worker process 36815  1406   0.0  4268060 -      egrep (nginx|PID) 

None of the following solves the issue:

  • sudo killall nginx
  • brew services restart nginx
  • brew services restart php
  • valet restart
  • Restarting my Mac
  • valet uninstall && valet install then valet park on the relevant dir

Apache is not running as a conflicting service.

I tried doing sudo /usr/local/opt/nginx/bin/nginx -g 'daemon off;' and got this:

nginx: [emerg] bind() to 0.0.0.0:80 failed (48: Address already in use) nginx: [emerg] bind() to 0.0.0.0:443 failed (48: Address already in use) nginx: [emerg] bind() to 0.0.0.0:60 failed (48: Address already in use) nginx: [emerg] bind() to 0.0.0.0:80 failed (48: Address already in use) nginx: [emerg] bind() to 0.0.0.0:443 failed (48: Address already in use) nginx: [emerg] bind() to 0.0.0.0:60 failed (48: Address already in use) nginx: [emerg] bind() to 0.0.0.0:80 failed (48: Address already in use) nginx: [emerg] bind() to 0.0.0.0:443 failed (48: Address already in use) nginx: [emerg] bind() to 0.0.0.0:60 failed (48: Address already in use) nginx: [emerg] bind() to 0.0.0.0:80 failed (48: Address already in use) nginx: [emerg] bind() to 0.0.0.0:443 failed (48: Address already in use) nginx: [emerg] bind() to 0.0.0.0:60 failed (48: Address already in use) nginx: [emerg] bind() to 0.0.0.0:80 failed (48: Address already in use) nginx: [emerg] bind() to 0.0.0.0:443 failed (48: Address already in use) nginx: [emerg] bind() to 0.0.0.0:60 failed (48: Address already in use) nginx: [emerg] still could not bind() 

Running sudo lsof -i tcp:80 produces:

COMMAND   PID USER   FD   TYPE             DEVICE SIZE/OFF NODE NAME nginx   42220 root    7u  IPv4 0x7ac8eae7874ccb11      0t0  TCP *:http (LISTEN) nginx   42221 Myself    7u  IPv4 0x7ac8eae7874ccb11      0t0  TCP *:http (LISTEN) nginx   42222 Myself    7u  IPv4 0x7ac8eae7874ccb11      0t0  TCP *:http (LISTEN) nginx   42223 Myself    7u  IPv4 0x7ac8eae7874ccb11      0t0  TCP *:http (LISTEN) nginx   42224 Myself    7u  IPv4 0x7ac8eae7874ccb11      0t0  TCP *:http (LISTEN) nginx   42225 Myself    7u  IPv4 0x7ac8eae7874ccb11      0t0  TCP *:http (LISTEN) nginx   42226 Myself    7u  IPv4 0x7ac8eae7874ccb11      0t0  TCP *:http (LISTEN) nginx   42227 Myself    7u  IPv4 0x7ac8eae7874ccb11      0t0  TCP *:http (LISTEN) nginx   42228 Myself    7u  IPv4 0x7ac8eae7874ccb11      0t0  TCP *:http (LISTEN) nginx   42229 Myself    7u  IPv4 0x7ac8eae7874ccb11      0t0  TCP *:http (LISTEN) nginx   42230 Myself    7u  IPv4 0x7ac8eae7874ccb11      0t0  TCP *:http (LISTEN) nginx   42231 Myself    7u  IPv4 0x7ac8eae7874ccb11      0t0  TCP *:http (LISTEN) nginx   42232 Myself    7u  IPv4 0x7ac8eae7874ccb11      0t0  TCP *:http (LISTEN) 

Basically the same output when I run that command for port 443.

This valet issue post suggests valet domain test might fix it, but that didn’t help.

How to set bind a text box to a class not in the data context class

I have this dock panel which I’m trying to set up bindings for.

The problem is that my DataContext for my XAML is set to the MainWindow class but my class that I want to bind to (autoCam) is separate from that class. I have an instance of autoCam being used in the MainWindow class, called “myCam”, but I’ve gotten confused about how to get these bindings to work.

This is the code I’m using in my dock panel:

            <DockPanel  x:Name="BottomDock" Visibility="Collapsed" Grid.Column="2" Grid.Row="2" Grid.ColumnSpan="2" DockPanel.Dock="Bottom" Margin="0">                 <Button x:Name="Rewind" Click="Rewind_Click" HorizontalAlignment="Left" Width="23" RenderTransformOrigin="0.5,0.5" Grid.Row="1"/>                 <Button x:Name="Play" Content=">" Click="Play_Click" HorizontalAlignment="Left" Width="17" RenderTransformOrigin="0.5,0.5" Grid.Row="1"/>                 <Button x:Name="Pause" Content="||" Click ="Pause_Click" HorizontalAlignment="Left" VerticalAlignment="Top" Width="16" Height="22" RenderTransformOrigin="0.5,0.5" Grid.Row="1"/>                 <Button x:Name="FastForward" Content=">>" Click="FastForward_Click" HorizontalAlignment="Left" Width="23" RenderTransformOrigin="0.5,0.5" Grid.Row="1"/>                 <TextBlock Background="Black" TextAlignment="Center" Foreground="AliceBlue" HorizontalAlignment="Left" Width="95" Text="Camera Position"/>                 <TextBox Background="Black" TextAlignment="Center" Foreground="AliceBlue" HorizontalAlignment="Left" Width="40" Name="cpx" Text="{Binding Path=myCam.cameraPositionX, UpdateSourceTrigger=PropertyChanged}"/>                 <TextBox Background="Black" TextAlignment="Center" Foreground="AliceBlue" HorizontalAlignment="Left" Width="40" Name="cpy" Text="{Binding Path=myCam.cameraPositionY, UpdateSourceTrigger=PropertyChanged}"/>                 <TextBox Background="Black" TextAlignment="Center" Foreground="AliceBlue" HorizontalAlignment="Left" Width="40" Name="cpz" Text="{Binding Path=myCam.cameraPositionZ, UpdateSourceTrigger=PropertyChanged}"/>                 <TextBlock Background="Black" TextAlignment="Center" Foreground="AliceBlue" HorizontalAlignment="Left" Width="95" Text="Look Direction"/>                 <TextBox Background="Black" TextAlignment="Center" Foreground="AliceBlue" HorizontalAlignment="Left" Width="40" Name="ldx" Text="{Binding Path=myCam.lookDirectionX, UpdateSourceTrigger=PropertyChanged}"/>                 <TextBox Background="Black" TextAlignment="Center" Foreground="AliceBlue" HorizontalAlignment="Left" Width="40" Name="ldy" Text="{Binding Path=myCam.lookDirectionY, UpdateSourceTrigger=PropertyChanged}"/>                 <TextBox Background="Black" TextAlignment="Center" Foreground="AliceBlue" HorizontalAlignment="Left" Width="40" Name="ldz" Text="{Binding Path=myCam.lookDirectionZ, UpdateSourceTrigger=PropertyChanged}"/>             </DockPanel> 

At first I thought I could just write DataContext=autoCam as a property of the dock panel itself, or for each individual textbox and then just say {binding cameraPositionX} or something, but that didn’t do anything.

Then i thought I could just say {Binding myCam.cameraPositionX} since myCam is a member of the MainWindow class. But that didn’t work either.

In a futile attempt, I tried to sort of combine both of my guesses and add DataContext=autoCam to properties of all of the text boxes but I never thought that would actually work.

I would really appreciate a solution, but a break down of why these aren’t working for me is essentially going to help me a lot more in the long run.

Thank you for your time and help everyone.

Can a warlock with pact of the blade bind a non-magical weapon to be their pact weapon?

In the pact of the blade text, the following is read:

… You can transform one magic weapon into your pact weapon by performing a special ritual while you hold the weapon. …

This indicates to me that only magical weapons can be bound in this way. Does that mean a silvered weapon, adamantine weapon, or even just a entirely mundane weapon is unable to be bound in this manner?

Inspired by this

Error: VanillaMasker: There is no element to bind

Olá obrigado desde já.

Tenho esse seguinte problema.

console

Error: VanillaMasker: There is no element to bind. vanilla-masker.min.js:49:23

h public/Js/vanilla-masker.min.js:49:23

public/Js/add-javascript.js:6:1

var h = function(a) {     if (!a) throw new Error("VanillaMasker: There is no element to bind.");     var b = "length" in a ? a.length ? a : [] : [a];     return new g(b) }; 

BIND SERVFAIL on common domains, restarting BIND resolves the issue

From time to time by BIND 9 fails with SERVFAIL on pretty much every query. What’s weird is that restarting BIND helps.

I turned on debugging and get this in logs:

24-Dec-2018 15:32:58.790 lame-servers: info: broken trust chain resolving 'github.com/AAAA/IN': 1.2.3.4#53 24-Dec-2018 15:32:58.790 query-errors: debug 1: client 10.0.1.163#45403 (github.com): query failed (SERVFAIL) for github.com/IN/AAAA at ../../../bin/named/query.c:7773 24-Dec-2018 15:32:58.900 resolver: debug 1: fetch: bitbucket.org/A 24-Dec-2018 15:32:58.900 resolver: debug 1: fetch: bitbucket.org/AAAA 24-Dec-2018 15:32:58.906 database: debug 1: decrement_reference: delete from rbt: 0x7fb568a19e80 bitbucket.org 24-Dec-2018 15:32:58.906 resolver: debug 1: fetch: bitbucket.org/DS 24-Dec-2018 15:32:58.907 database: debug 1: decrement_reference: delete from rbt: 0x7fb568a19e80 bitbucket.org 24-Dec-2018 15:32:58.907 resolver: debug 1: fetch: bitbucket.org/DS 24-Dec-2018 15:32:58.919 dnssec: info:   validating org/SOA: got insecure response; parent indicates it should be secure 24-Dec-2018 15:32:58.919 lame-servers: info: no valid RRSIG resolving 'bitbucket.org/DS/IN': 1.2.3.4#53 24-Dec-2018 15:32:58.928 resolver: debug 1: fetch: org/DNSKEY 24-Dec-2018 15:32:58.935 dnssec: info: validating org/DNSKEY: got insecure response; parent indicates it should be secure 24-Dec-2018 15:32:58.935 lame-servers: info: insecurity proof failed resolving 'org/DNSKEY/IN': 1.2.3.4#53 24-Dec-2018 15:32:58.947 resolver: debug 1: fetch: bitbucket.org.dlv.isc.org/DLV 24-Dec-2018 15:32:58.947 resolver: debug 1: fetch: bitbucket.org.dlv.isc.org/DLV 24-Dec-2018 15:32:58.986 dnssec: info:   validating dlv.isc.org/SOA: got insecure response; parent indicates it should be secure 24-Dec-2018 15:32:58.986 dnssec: info: validating bitbucket.org.dlv.isc.org/DLV: bad cache hit (org.dlv.isc.org/DS) 24-Dec-2018 15:32:58.986 lame-servers: info: broken trust chain resolving 'bitbucket.org.dlv.isc.org/DLV/IN': 1.2.3.4#53 24-Dec-2018 15:32:58.986 lame-servers: info: broken trust chain resolving 'bitbucket.org/A/IN': 1.2.3.4#53 24-Dec-2018 15:32:58.986 lame-servers: info: broken trust chain resolving 'bitbucket.org/AAAA/IN': 1.2.3.4#53 24-Dec-2018 15:32:58.986 query-errors: debug 1: client 10.0.1.163#54539 (bitbucket.org): query failed (SERVFAIL) for bitbucket.org/IN/A at ../../../bin/named/query.c:7773 24-Dec-2018 15:32:58.986 query-errors: debug 1: client 10.0.1.163#54539 (bitbucket.org): query failed (SERVFAIL) for bitbucket.org/IN/AAAA at ../../../bin/named/query.c:7773 24-Dec-2018 15:32:58.987 resolver: debug 1: fetch: bitbucket.org/A 24-Dec-2018 15:32:58.987 resolver: debug 1: fetch: bitbucket.org/AAAA 24-Dec-2018 15:32:58.993 dnssec: info: validating bitbucket.org/A: bad cache hit (bitbucket.org.dlv.isc.org/DLV) 24-Dec-2018 15:32:58.993 lame-servers: info: broken trust chain resolving 'bitbucket.org/A/IN': 1.2.3.4#53 24-Dec-2018 15:32:58.993 query-errors: debug 1: client 10.0.1.163#54539 (bitbucket.org): query failed (SERVFAIL) for bitbucket.org/IN/A at ../../../bin/named/query.c:7773 24-Dec-2018 15:32:58.994 dnssec: info: validating bitbucket.org/AAAA: bad cache hit (bitbucket.org.dlv.isc.org/DLV) 24-Dec-2018 15:32:58.994 lame-servers: info: broken trust chain resolving 'bitbucket.org/AAAA/IN': 1.2.3.4#53 24-Dec-2018 15:32:58.994 query-errors: debug 1: client 10.0.1.163#54539 (bitbucket.org): query failed (SERVFAIL) for bitbucket.org/IN/AAAA at ../../../bin/named/query.c:7773 24-Dec-2018 15:33:23.774 resolver: debug 1: fetch: 43.249.96.191.in-addr.arpa/PTR 24-Dec-2018 15:33:23.780 resolver: debug 1: fetch: 249.96.191.in-addr.arpa.dlv.isc.org/DLV -- 24-Dec-2018 15:33:33.502 lame-servers: info: broken trust chain resolving '170.81.36.185.in-addr.arpa/PTR/IN': 1.2.3.4#53 24-Dec-2018 15:33:33.502 query-errors: debug 1: client 10.5.1.181#58654 (170.81.36.185.in-addr.arpa): query failed (SERVFAIL) for 170.81.36.185.in-addr.arpa/IN/PTR at ../../../bin/named/query.c:7773 24-Dec-2018 15:33:35.271 resolver: debug 1: fetch: bitbucket.org/A 24-Dec-2018 15:33:35.286 dnssec: info: validating bitbucket.org/A: bad cache hit (bitbucket.org.dlv.isc.org/DLV) 24-Dec-2018 15:33:35.286 lame-servers: info: broken trust chain resolving 'bitbucket.org/A/IN': 1.2.3.4#53 24-Dec-2018 15:33:35.286 query-errors: debug 1: client 10.0.1.163#59171 (bitbucket.org): query failed (SERVFAIL) for bitbucket.org/IN/A at ../../../bin/named/query.c:7773 24-Dec-2018 15:33:51.394 resolver: debug 1: fetch: 118.120.54.92.in-addr.arpa/PTR 24-Dec-2018 15:33:51.401 database: debug 1: decrement_reference: delete from rbt: 0x7fb50b313268 118.120.54.92.in-addr.arpa -- 24-Dec-2018 15:33:56.771 lame-servers: info: broken trust chain resolving '1.debian.pool.ntp.org/AAAA/IN': 1.2.3.4#53 24-Dec-2018 15:33:56.771 query-errors: debug 1: client 10.0.1.163#59947 (1.debian.pool.ntp.org): query failed (SERVFAIL) for 1.debian.pool.ntp.org/IN/AAAA at ../../../bin/named/query.c:7773 24-Dec-2018 15:34:02.364 resolver: debug 1: fetch: bitbucket.org/A 24-Dec-2018 15:34:02.371 dnssec: info: validating bitbucket.org/A: bad cache hit (bitbucket.org.dlv.isc.org/DLV) 24-Dec-2018 15:34:02.371 lame-servers: info: broken trust chain resolving 'bitbucket.org/A/IN': 1.2.3.4#53 24-Dec-2018 15:34:02.371 query-errors: debug 1: client 10.0.1.90#39850 (bitbucket.org): query failed (SERVFAIL) for bitbucket.org/IN/A at ../../../bin/named/query.c:7773 24-Dec-2018 15:34:02.751 resolver: debug 1: fetch: 159.47.143.90.in-addr.arpa/PTR 24-Dec-2018 15:34:02.896 database: debug 1: decrement_reference: delete from rbt: 0x7fb50b313268 159.47.143.90.in-addr.arpa -- 24-Dec-2018 15:34:03.927 resolver: debug 1: fetch: 159.47.143.90.xbl.spamhaus.org/TXT 24-Dec-2018 15:34:15.106 resolver: debug 1: fetch: 20.81.36.185.in-addr.arpa/PTR 24-Dec-2018 15:34:22.655 resolver: debug 1: fetch: bitbucket.org/A 24-Dec-2018 15:34:22.664 dnssec: info: validating bitbucket.org/A: bad cache hit (bitbucket.org.dlv.isc.org/DLV) 24-Dec-2018 15:34:22.664 lame-servers: info: broken trust chain resolving 'bitbucket.org/A/IN': 5.6.7.8#53 24-Dec-2018 15:34:22.664 query-errors: debug 1: client 127.0.0.1#49536 (bitbucket.org): query failed (SERVFAIL) for bitbucket.org/IN/A at ../../../bin/named/query.c:7773 24-Dec-2018 15:34:26.860 resolver: debug 1: fetch: 2.debian.pool.ntp.org/AAAA 24-Dec-2018 15:34:26.860 resolver: debug 1: fetch: 2.debian.pool.ntp.org/A 

Why is that happening and how can I fix that? And why restarting BIND helps?

OS: Debian 9.6 amd64.

BIND:

ii  bind9                                         1:9.10.3.dfsg.P4-12.3+deb9u4                amd64        Internet Domain Name Server ii  bind9-host                                    1:9.10.3.dfsg.P4-12.3+deb9u4                amd64        Version of 'host' bundled with BIND 9.X ii  bind9utils                                    1:9.10.3.dfsg.P4-12.3+deb9u4                amd64        Utilities for BIND ii  libbind9-140:amd64                            1:9.10.3.dfsg.P4-12.3+deb9u4                amd64        BIND9 Shared Library used by BIND 

Bind Primary Dns Server on WLAN

I’m trying to build a local DNS server (Bind Ubuntu 18.04) which I’m told is a requirement for Samba’s Implementation of Active Directory.

When I try named-checkzone followed by the domain I get the following error:

dns_master_load: db.example.com:13: unexpected end of line dns_master_load: db.example.com:13: unexpected end of input zone example.com/IN: loading from master file db.example.com failed: unexpected end of input

The DNS server will also act as the active directory server. It runs as a VM in virtualBox in Bridged mode and has a static IP (192.168.0.75) that can be seen by the host VM and the rest of the network.

I’ve checked several guides and documentation but I cant see what I’m doing wrong.

I’m just trying to create a primary DNS server for the WLAN so I can get AD working, not sure why its this hard :/

P. S. I have a copy of the conf files but they exceed word limit here. Happy to upload if required.

Many Thanks for any response 🙂

bind9-dyndb-ldap, BIND, named.conf: “cannot parse settings” during service start

I’ve installed LDAP, BIND9 and Bind9-dyndb-ldap on 18.04 server. Added the BIND schema to LDAP; added a zone and a few server dns entries to LDAP. Added the “dyndb” section to the named.conf, configuring the ldap connectivity information.

... dyndb "bind9-dyndb" "/usr/lib/bind/ldap.so" {         uri         "ldap://ldap.example.com";         base        "ou=dns,dc=example,dc=com";         auth_method "simple";         bind_dn     "cn=admin,dc=example,dc=com";         password    "MyPassword"; }; ... 

I can search my ldap using the username and password given using “ldapsearch”. I also was able to work around the AppArmor config issue that did not allow BIND9 use “/usr/lib/bind/ldap.so”.

Now when I attempt to start bind9, I receive the following error in the syslog:

Dec 21 21:42:20 ltserver1 named[17111]: cannot parse settings for 'named.conf for database bind9-dyndb': not found Dec 21 21:42:20 ltserver1 named[17111]: dynamic database 'bind9-dyndb' configuration failed: not found Dec 21 21:42:20 ltserver1 named[17111]: loading configuration: not found Dec 21 21:42:20 ltserver1 named[17111]: exiting (due to fatal error) 

I’m stumped as to how to debug this further. Any “pointers” as to what to do would be greatly appreciated!

I have not found any tutorials showing recent bind9-dyndb-ldap/BIND9 configuration examples (the most recent one I find is for Ubuntu 16.04 and it still uses “Dynamic-DB” instead of “dyndb”). I feel like I’m groping in the dark. Any assistance would be very helpful!