New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bind9 installation #109
Comments
Could you paste /etc/bind/named.conf.options? I'd suggest creating a new fresh machine, copying /home/user-data over to the new machine, and then running the setup script. |
Sure, here is the contents of named.conf.options:
Could the listen-on IP be wrong? |
I think you'll need to get rid of |
I commented out the line from named.conf.options and also set it to "none" and restarted bind9, but either way I still can't ping any domains from the server or run apt-get update. |
See if there are any errors in /var/log/syslog. (Try |
Here is the end of the syslog contents after restarting bind9:
|
Can you show me the output of Sorry for all of the trouble. Appreciate you sticking through this. |
Also run |
No problem at all, I appreciate you trying to get to the bottom of this for us.
The output for
Output for
|
That's odd. nsd.conf is missing But I'm stumped. If the output of |
Maybe the fact that bind9 isn't running is preventing nsd.conf from being updated to have the right value. So maybe try |
I tried stopping nsd, then running the start.sh script again and it provided the same errors as above while running. Do you think it advisable just to create an entirely new Digital Ocean container, start fresh and move the user-data folder over as you indicated earlier? |
Yeah that would probably be the fastest way to get back to normal. |
Sounds good - I will do that and if there are any other issues related to the same thing I will let you know! Thanks for all your help so far. |
Let me know how it goes. |
By creating a new droplet and running everything from scratch, it all worked out nicely. One problem I did notice was that the original droplet was a 512mb / 20gb Digital Ocean droplet, and your script threw an error on the new droplet (with the same settings):
So I upgraded the droplet and it worked. I'm having two other issues now with the new version of mailinabox, but I will try working them out on our end prior to posting them. |
Great. I'll close this issue. Let me know about other problems as you find them (on new issues)! |
We installed mail-in-a-box a couple of months ago on our Digital Ocean server and everything setup fine and has been working nicely. However, we recently upgraded but after it installed bind9 everything started to fail as DNS queries stopped resolving. When we stop the bind9 service, DNS queries resolve again. Here is the output from running start.sh:
Any advice on how to resolve this would be greatly appreciated.
The text was updated successfully, but these errors were encountered: