BIND9 start-up problem!
Clash Royale CLAN TAG#URR8PPP up vote
2
down vote
favorite
1
I'm a newbie to Ubuntu Server and I'm having trouble using BIND9 on Ubuntu Server 14.05.5.
My problem is BIND9 doesn't seem to start up correctly when I do a full reboot of my server. After a manual service restart BIND9 started running again. I'm wondering if there's a work-around to this?
Thanks so much in advance guys!
14.04 dns
asked Apr 13 at 8:07
Son Nguyen
133
add a comment |Â
up vote
2
down vote
favorite
1
I'm a newbie to Ubuntu Server and I'm having trouble using BIND9 on Ubuntu Server 14.05.5.
My problem is BIND9 doesn't seem to start up correctly when I do a full reboot of my server. After a manual service restart BIND9 started running again. I'm wondering if there's a work-around to this?
Thanks so much in advance guys!
14.04 dns
asked Apr 13 at 8:07
Son Nguyen
133
By enabling service it automatically start on system boot
– Kartik Agarwal
Apr 13 at 10:04
Hi Kartik Agarwa, I had it fixed by change the boot up order of BIND9 and my DHCP service. thanks for your help
– Son Nguyen
Apr 14 at 11:10
add a comment |Â
up vote
2
down vote
favorite
1
up vote
2
down vote
favorite
1
1
I'm a newbie to Ubuntu Server and I'm having trouble using BIND9 on Ubuntu Server 14.05.5.
My problem is BIND9 doesn't seem to start up correctly when I do a full reboot of my server. After a manual service restart BIND9 started running again. I'm wondering if there's a work-around to this?
Thanks so much in advance guys!
14.04 dns
asked Apr 13 at 8:07
Son Nguyen
133
I'm a newbie to Ubuntu Server and I'm having trouble using BIND9 on Ubuntu Server 14.05.5.
My problem is BIND9 doesn't seem to start up correctly when I do a full reboot of my server. After a manual service restart BIND9 started running again. I'm wondering if there's a work-around to this?
Thanks so much in advance guys!
14.04 dns
14.04 dns
asked Apr 13 at 8:07
Son Nguyen
133
asked Apr 13 at 8:07
Son Nguyen
133
asked Apr 13 at 8:07
Son Nguyen
133
asked Apr 13 at 8:07
Son Nguyen
133
asked Apr 13 at 8:07
Son Nguyen
133
133
By enabling service it automatically start on system boot
– Kartik Agarwal
Apr 13 at 10:04
Hi Kartik Agarwa, I had it fixed by change the boot up order of BIND9 and my DHCP service. thanks for your help
– Son Nguyen
Apr 14 at 11:10
add a comment |Â
By enabling service it automatically start on system boot
– Kartik Agarwal
Apr 13 at 10:04
Hi Kartik Agarwa, I had it fixed by change the boot up order of BIND9 and my DHCP service. thanks for your help
– Son Nguyen
Apr 14 at 11:10
By enabling service it automatically start on system boot
– Kartik Agarwal
Apr 13 at 10:04
By enabling service it automatically start on system boot
– Kartik Agarwal
Apr 13 at 10:04
Hi Kartik Agarwa, I had it fixed by change the boot up order of BIND9 and my DHCP service. thanks for your help
– Son Nguyen
Apr 14 at 11:10
Hi Kartik Agarwa, I had it fixed by change the boot up order of BIND9 and my DHCP service. thanks for your help
– Son Nguyen
Apr 14 at 11:10
add a comment |Â
2 Answers
2
active
oldest
votes
up vote
0
down vote
accepted
Just perform this command:
sudo update-rc.d "name of your service" defaults
It will add your service in autostart.
answered Apr 13 at 8:37
Gintoki
162
The start/stop links for bind9 already exist on my system, when I do a reboot on my server, the bind9 service did start but I can't resolve DNS until after a service restart. weird...
– Son Nguyen
Apr 13 at 8:57
Ok, first I misunderstood you. Could you show the BIND log after the start system?
– Gintoki
Apr 13 at 11:32
Apr 14 17:22:13 CTL named[1319]: zone 128.81.10.in-addr.arpa/IN: loaded serial 4 Apr 14 17:22:13 CTL named[1319]: zone 127.in-addr.arpa/IN: loaded serial 1 Apr 14 17:22:13 CTL named[1319]: zone loc/IN: loaded serial 3 Apr 14 17:22:13 CTL named[1319]: zone localhost/IN: loaded serial 2 Apr 14 17:22:13 CTL named[1319]: zone 255.in-addr.arpa/IN: loaded serial 1 Apr 14 17:22:13 CTL named[1319]: all zones loaded Apr 14 17:22:13 CTL named[1319]: running Apr 14 17:22:13 CTL named[1319]: zone loc/IN: sending notifies (serial 3)
– Son Nguyen
Apr 14 at 10:44
Sorry for the late reply. In the log after the system started, it indicates that my DNS zone is loaded in serial 4 and everything is fine although I can't resolve the DNS in that zone from a client.
– Son Nguyen
Apr 14 at 10:45
Ah sorry guys, I figure out the problem. My DHCP service boot up order is after the BIND9 so it wasn't able to bind the interface for listening. I change the order then it works like a charm. Thank you so much for your help, I had to check the log file to figure that out
– Son Nguyen
Apr 14 at 11:09
 |Â
show 1 more comment
up vote
1
down vote
You need to enable the bind9 service with the command.
sudo systemctl enable bind9
answered Apr 13 at 8:50
Kartik Agarwal
365210
Ah sorry guys, I figure out the problem. My DHCP service boot up order is after the BIND9 so it wasn't able to bind the interface for listening. I change the order then it works like a charm
– Son Nguyen
Apr 14 at 11:09
Yes got it thanks.
– Kartik Agarwal
Apr 16 at 5:34
add a comment |Â
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
accepted
Just perform this command:
sudo update-rc.d "name of your service" defaults
It will add your service in autostart.
answered Apr 13 at 8:37
Gintoki
162
The start/stop links for bind9 already exist on my system, when I do a reboot on my server, the bind9 service did start but I can't resolve DNS until after a service restart. weird...
– Son Nguyen
Apr 13 at 8:57
Ok, first I misunderstood you. Could you show the BIND log after the start system?
– Gintoki
Apr 13 at 11:32
Apr 14 17:22:13 CTL named[1319]: zone 128.81.10.in-addr.arpa/IN: loaded serial 4 Apr 14 17:22:13 CTL named[1319]: zone 127.in-addr.arpa/IN: loaded serial 1 Apr 14 17:22:13 CTL named[1319]: zone loc/IN: loaded serial 3 Apr 14 17:22:13 CTL named[1319]: zone localhost/IN: loaded serial 2 Apr 14 17:22:13 CTL named[1319]: zone 255.in-addr.arpa/IN: loaded serial 1 Apr 14 17:22:13 CTL named[1319]: all zones loaded Apr 14 17:22:13 CTL named[1319]: running Apr 14 17:22:13 CTL named[1319]: zone loc/IN: sending notifies (serial 3)
– Son Nguyen
Apr 14 at 10:44
Sorry for the late reply. In the log after the system started, it indicates that my DNS zone is loaded in serial 4 and everything is fine although I can't resolve the DNS in that zone from a client.
– Son Nguyen
Apr 14 at 10:45
Ah sorry guys, I figure out the problem. My DHCP service boot up order is after the BIND9 so it wasn't able to bind the interface for listening. I change the order then it works like a charm. Thank you so much for your help, I had to check the log file to figure that out
– Son Nguyen
Apr 14 at 11:09
 |Â
show 1 more comment
up vote
0
down vote
accepted
Just perform this command:
sudo update-rc.d "name of your service" defaults
It will add your service in autostart.
answered Apr 13 at 8:37
Gintoki
162
The start/stop links for bind9 already exist on my system, when I do a reboot on my server, the bind9 service did start but I can't resolve DNS until after a service restart. weird...
– Son Nguyen
Apr 13 at 8:57
Ok, first I misunderstood you. Could you show the BIND log after the start system?
– Gintoki
Apr 13 at 11:32
Apr 14 17:22:13 CTL named[1319]: zone 128.81.10.in-addr.arpa/IN: loaded serial 4 Apr 14 17:22:13 CTL named[1319]: zone 127.in-addr.arpa/IN: loaded serial 1 Apr 14 17:22:13 CTL named[1319]: zone loc/IN: loaded serial 3 Apr 14 17:22:13 CTL named[1319]: zone localhost/IN: loaded serial 2 Apr 14 17:22:13 CTL named[1319]: zone 255.in-addr.arpa/IN: loaded serial 1 Apr 14 17:22:13 CTL named[1319]: all zones loaded Apr 14 17:22:13 CTL named[1319]: running Apr 14 17:22:13 CTL named[1319]: zone loc/IN: sending notifies (serial 3)
– Son Nguyen
Apr 14 at 10:44
Sorry for the late reply. In the log after the system started, it indicates that my DNS zone is loaded in serial 4 and everything is fine although I can't resolve the DNS in that zone from a client.
– Son Nguyen
Apr 14 at 10:45
Ah sorry guys, I figure out the problem. My DHCP service boot up order is after the BIND9 so it wasn't able to bind the interface for listening. I change the order then it works like a charm. Thank you so much for your help, I had to check the log file to figure that out
– Son Nguyen
Apr 14 at 11:09
 |Â
show 1 more comment
up vote
0
down vote
accepted
up vote
0
down vote
accepted
Just perform this command:
sudo update-rc.d "name of your service" defaults
It will add your service in autostart.
answered Apr 13 at 8:37
Gintoki
162
Just perform this command:
sudo update-rc.d "name of your service" defaults
It will add your service in autostart.
answered Apr 13 at 8:37
Gintoki
162
answered Apr 13 at 8:37
Gintoki
162
answered Apr 13 at 8:37
Gintoki
162
answered Apr 13 at 8:37
Gintoki
162
162
The start/stop links for bind9 already exist on my system, when I do a reboot on my server, the bind9 service did start but I can't resolve DNS until after a service restart. weird...
– Son Nguyen
Apr 13 at 8:57
Ok, first I misunderstood you. Could you show the BIND log after the start system?
– Gintoki
Apr 13 at 11:32
Apr 14 17:22:13 CTL named[1319]: zone 128.81.10.in-addr.arpa/IN: loaded serial 4 Apr 14 17:22:13 CTL named[1319]: zone 127.in-addr.arpa/IN: loaded serial 1 Apr 14 17:22:13 CTL named[1319]: zone loc/IN: loaded serial 3 Apr 14 17:22:13 CTL named[1319]: zone localhost/IN: loaded serial 2 Apr 14 17:22:13 CTL named[1319]: zone 255.in-addr.arpa/IN: loaded serial 1 Apr 14 17:22:13 CTL named[1319]: all zones loaded Apr 14 17:22:13 CTL named[1319]: running Apr 14 17:22:13 CTL named[1319]: zone loc/IN: sending notifies (serial 3)
– Son Nguyen
Apr 14 at 10:44
Sorry for the late reply. In the log after the system started, it indicates that my DNS zone is loaded in serial 4 and everything is fine although I can't resolve the DNS in that zone from a client.
– Son Nguyen
Apr 14 at 10:45
Ah sorry guys, I figure out the problem. My DHCP service boot up order is after the BIND9 so it wasn't able to bind the interface for listening. I change the order then it works like a charm. Thank you so much for your help, I had to check the log file to figure that out
– Son Nguyen
Apr 14 at 11:09
 |Â
show 1 more comment
The start/stop links for bind9 already exist on my system, when I do a reboot on my server, the bind9 service did start but I can't resolve DNS until after a service restart. weird...
– Son Nguyen
Apr 13 at 8:57
Ok, first I misunderstood you. Could you show the BIND log after the start system?
– Gintoki
Apr 13 at 11:32
Apr 14 17:22:13 CTL named[1319]: zone 128.81.10.in-addr.arpa/IN: loaded serial 4 Apr 14 17:22:13 CTL named[1319]: zone 127.in-addr.arpa/IN: loaded serial 1 Apr 14 17:22:13 CTL named[1319]: zone loc/IN: loaded serial 3 Apr 14 17:22:13 CTL named[1319]: zone localhost/IN: loaded serial 2 Apr 14 17:22:13 CTL named[1319]: zone 255.in-addr.arpa/IN: loaded serial 1 Apr 14 17:22:13 CTL named[1319]: all zones loaded Apr 14 17:22:13 CTL named[1319]: running Apr 14 17:22:13 CTL named[1319]: zone loc/IN: sending notifies (serial 3)
– Son Nguyen
Apr 14 at 10:44
Sorry for the late reply. In the log after the system started, it indicates that my DNS zone is loaded in serial 4 and everything is fine although I can't resolve the DNS in that zone from a client.
– Son Nguyen
Apr 14 at 10:45
Ah sorry guys, I figure out the problem. My DHCP service boot up order is after the BIND9 so it wasn't able to bind the interface for listening. I change the order then it works like a charm. Thank you so much for your help, I had to check the log file to figure that out
– Son Nguyen
Apr 14 at 11:09
The start/stop links for bind9 already exist on my system, when I do a reboot on my server, the bind9 service did start but I can't resolve DNS until after a service restart. weird...
– Son Nguyen
Apr 13 at 8:57
The start/stop links for bind9 already exist on my system, when I do a reboot on my server, the bind9 service did start but I can't resolve DNS until after a service restart. weird...
– Son Nguyen
Apr 13 at 8:57
Ok, first I misunderstood you. Could you show the BIND log after the start system?
– Gintoki
Apr 13 at 11:32
Ok, first I misunderstood you. Could you show the BIND log after the start system?
– Gintoki
Apr 13 at 11:32
Apr 14 17:22:13 CTL named[1319]: zone 128.81.10.in-addr.arpa/IN: loaded serial 4 Apr 14 17:22:13 CTL named[1319]: zone 127.in-addr.arpa/IN: loaded serial 1 Apr 14 17:22:13 CTL named[1319]: zone loc/IN: loaded serial 3 Apr 14 17:22:13 CTL named[1319]: zone localhost/IN: loaded serial 2 Apr 14 17:22:13 CTL named[1319]: zone 255.in-addr.arpa/IN: loaded serial 1 Apr 14 17:22:13 CTL named[1319]: all zones loaded Apr 14 17:22:13 CTL named[1319]: running Apr 14 17:22:13 CTL named[1319]: zone loc/IN: sending notifies (serial 3)
– Son Nguyen
Apr 14 at 10:44
Apr 14 17:22:13 CTL named[1319]: zone 128.81.10.in-addr.arpa/IN: loaded serial 4 Apr 14 17:22:13 CTL named[1319]: zone 127.in-addr.arpa/IN: loaded serial 1 Apr 14 17:22:13 CTL named[1319]: zone loc/IN: loaded serial 3 Apr 14 17:22:13 CTL named[1319]: zone localhost/IN: loaded serial 2 Apr 14 17:22:13 CTL named[1319]: zone 255.in-addr.arpa/IN: loaded serial 1 Apr 14 17:22:13 CTL named[1319]: all zones loaded Apr 14 17:22:13 CTL named[1319]: running Apr 14 17:22:13 CTL named[1319]: zone loc/IN: sending notifies (serial 3)
– Son Nguyen
Apr 14 at 10:44
Sorry for the late reply. In the log after the system started, it indicates that my DNS zone is loaded in serial 4 and everything is fine although I can't resolve the DNS in that zone from a client.
– Son Nguyen
Apr 14 at 10:45
Sorry for the late reply. In the log after the system started, it indicates that my DNS zone is loaded in serial 4 and everything is fine although I can't resolve the DNS in that zone from a client.
– Son Nguyen
Apr 14 at 10:45
Ah sorry guys, I figure out the problem. My DHCP service boot up order is after the BIND9 so it wasn't able to bind the interface for listening. I change the order then it works like a charm. Thank you so much for your help, I had to check the log file to figure that out
– Son Nguyen
Apr 14 at 11:09
Ah sorry guys, I figure out the problem. My DHCP service boot up order is after the BIND9 so it wasn't able to bind the interface for listening. I change the order then it works like a charm. Thank you so much for your help, I had to check the log file to figure that out
– Son Nguyen
Apr 14 at 11:09
 |Â
show 1 more comment
up vote
1
down vote
You need to enable the bind9 service with the command.
sudo systemctl enable bind9
answered Apr 13 at 8:50
Kartik Agarwal
365210
Ah sorry guys, I figure out the problem. My DHCP service boot up order is after the BIND9 so it wasn't able to bind the interface for listening. I change the order then it works like a charm
– Son Nguyen
Apr 14 at 11:09
Yes got it thanks.
– Kartik Agarwal
Apr 16 at 5:34
add a comment |Â
up vote
1
down vote
You need to enable the bind9 service with the command.
sudo systemctl enable bind9
answered Apr 13 at 8:50
Kartik Agarwal
365210
Ah sorry guys, I figure out the problem. My DHCP service boot up order is after the BIND9 so it wasn't able to bind the interface for listening. I change the order then it works like a charm
– Son Nguyen
Apr 14 at 11:09
Yes got it thanks.
– Kartik Agarwal
Apr 16 at 5:34
add a comment |Â
up vote
1
down vote
up vote
1
down vote
You need to enable the bind9 service with the command.
sudo systemctl enable bind9
answered Apr 13 at 8:50
Kartik Agarwal
365210
You need to enable the bind9 service with the command.
sudo systemctl enable bind9
answered Apr 13 at 8:50
Kartik Agarwal
365210
answered Apr 13 at 8:50
Kartik Agarwal
365210
answered Apr 13 at 8:50
Kartik Agarwal
365210
answered Apr 13 at 8:50
Kartik Agarwal
365210
365210
Ah sorry guys, I figure out the problem. My DHCP service boot up order is after the BIND9 so it wasn't able to bind the interface for listening. I change the order then it works like a charm
– Son Nguyen
Apr 14 at 11:09
Yes got it thanks.
– Kartik Agarwal
Apr 16 at 5:34
add a comment |Â
Ah sorry guys, I figure out the problem. My DHCP service boot up order is after the BIND9 so it wasn't able to bind the interface for listening. I change the order then it works like a charm
– Son Nguyen
Apr 14 at 11:09
Yes got it thanks.
– Kartik Agarwal
Apr 16 at 5:34
Ah sorry guys, I figure out the problem. My DHCP service boot up order is after the BIND9 so it wasn't able to bind the interface for listening. I change the order then it works like a charm
– Son Nguyen
Apr 14 at 11:09
Ah sorry guys, I figure out the problem. My DHCP service boot up order is after the BIND9 so it wasn't able to bind the interface for listening. I change the order then it works like a charm
– Son Nguyen
Apr 14 at 11:09
Yes got it thanks.
– Kartik Agarwal
Apr 16 at 5:34
Yes got it thanks.
– Kartik Agarwal
Apr 16 at 5:34
add a comment |Â
Â
draft saved
draft discarded
Â
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1024571%2fbind9-start-up-problem%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
By enabling service it automatically start on system boot
– Kartik Agarwal
Apr 13 at 10:04
Hi Kartik Agarwa, I had it fixed by change the boot up order of BIND9 and my DHCP service. thanks for your help
– Son Nguyen
Apr 14 at 11:10