juxhindb / oob-server Goto Github PK

Hello , thank you for your useful tools, when i restart the bind server, i obtain an issue, I've tried to search in a lot of forum but i don't understand where can be the problem, you can see picture below .

the server used is an Ec2 instance, I have followed this youtube video
https://www.youtube.com/watch?v=p8wbebEgtDk&t=422s

Thanks :)

When i fired the command as root:
./setup domain_name ip

i got the below error at last

Creating new state
[+] setup: [10-09-2020 06:18:00] INFO Restarting Bind9 service
Failed to restart bind9.service: Unit bind9.service not found.

kindly help me to resolve this issue.

I'm not an expert with DNS and I'm having trouble getting the setup working. I own a domain I want to use exclusively for that Bind9 server, let's call it foo.bar. I've run the script in a clean Ubuntu 18.04 Droplet on DigitalOcean. The server is running on port 53:

root@oob:~# netstat -tulpn
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name    
tcp        0      0 10.19.0.7:53            0.0.0.0:*               LISTEN      1996/named          
tcp        0      0 1.2.3.4.103:53      0.0.0.0:*               LISTEN      1996/named          
tcp        0      0 127.0.0.1:53            0.0.0.0:*               LISTEN      1996/named          
tcp        0      0 127.0.0.53:53           0.0.0.0:*               LISTEN      582/systemd-resolve 
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      949/sshd            
tcp        0      0 127.0.0.1:953           0.0.0.0:*               LISTEN      1996/named          
tcp6       0      0 :::53                   :::*                    LISTEN      1996/named          
tcp6       0      0 :::22                   :::*                    LISTEN      949/sshd            
tcp6       0      0 ::1:953                 :::*                    LISTEN      1996/named          
udp        0      0 10.19.0.7:53            0.0.0.0:*                           1996/named          
udp        0      0 1.2.3.4.103:53      0.0.0.0:*                           1996/named          
udp        0      0 127.0.0.1:53            0.0.0.0:*                           1996/named          
udp        0      0 127.0.0.53:53           0.0.0.0:*                           582/systemd-resolve 
udp6       0      0 :::53                   :::*                                1996/named

The part I'm struggling with is actually setting up my domain. The docs say

Note—for this to work without specifying nameservers (i.e. dig A +short foo.bar @ns1.foo.bar)

Let's focus on that first part first. If I run dig @1.2.3.4 random.foo.bar. (the IP is redacted) I get

;; WARNING: recursion requested but not available

and also

;gh.foo.bar.      IN  A

Shouldn't that resolve to the same IP?

The second part is where my lack of DNS knowledge comes in.

you would need your domain provider to have the domain point to your custom domain for example:

Do I do that with a glue record? Because that's what I've done (having ns1.foo.bar and ns2.foo.bar point to the droplet). I can confirm that the glue record works by asking the nameserver on the bar. level. Do I need to have a SOA as well? But I assume that's something the Bind9 server would provide anyway, right?

So I assume my DNS setup is correct (the root level nameserver knows about my ns1 and ns2) but the server is not installed/configured properly. If I run a plain dig random-stuff.foo.bar I get the same empty ";ffewf.foo.bar. IN A
" line as above when I queried it directly from the server.

Edit: I just realized both dig and host also say "SERVFAIL"

Edit2: Forgot to mention the logs. A named.log does not exist, but syslog has

Apr  1 16:21:08 oob named[1996]: client @0x7fb1281c7240 1.2.3.4#10130 (ns2.foo.bar): query (cache) 'stuff.foo.bar/A/IN' denied

so their might be a permission issue? Or maybe the Bind9 config is missing something?

After "sudo ./setup foo.bar ipaddress" a deamon getting started, by which we are getting an continuous update on named.log.

Because after this comman : sudo tail -f /var/log/named/named.log
This what i am getting

21-May-2020 19:09:45.725 notify: info: zone localhost/IN: sending notifies (serial 2)
21-May-2020 19:09:45.758 general: info: managed-keys-zone: Key 20326 for zone . acceptance timer complete: key now trusted
21-May-2020 19:09:45.759 resolver: info: resolver priming query complete
21-May-2020 19:30:55.724 general: info: received control channel command 'stop'
21-May-2020 19:30:55.724 general: info: shutting down: flushing changes
21-May-2020 19:30:55.724 general: notice: stopping command channel on 127.0.0.1#953
21-May-2020 19:30:55.725 network: info: no longer listening on 127.0.0.1#53
21-May-2020 19:30:55.725 network: info: no longer listening on 1.2.3.4#53
21-May-2020 19:30:55.725 network: info: no longer listening on 5.6.7.8#53
21-May-2020 19:30:55.728 general: notice: exiting

1. What if I want to end this process, whats the command for it.
2. How to completely remove this from the server/system where ever it is installed, to start it freshly