6 reputation
3
bio website dustinschreiber.com
location Rochester, NY
age 20
visits member for 1 years, 9 months
seen Apr 15 '13 at 18:07

Aug
12
accepted BIND Name Servers aren't returning my site
Aug
12
comment BIND Name Servers aren't returning my site
You got me going in the right direction (plus your the only one that left an actual "answer" I guess you would say) so I'm going to mark you as solution. Everyone else: read the bottom update on my original question for the full explanation and solution. Thank you once again!
Aug
12
comment BIND Name Servers aren't returning my site
@petrus yes I did have an allow query line, I just edited my question with my solution :D
Aug
12
revised BIND Name Servers aren't returning my site
added 605 characters in body
Aug
12
revised BIND Name Servers aren't returning my site
Added dig from local BIND
Aug
12
comment BIND Name Servers aren't returning my site
Also, if I run the dig command you did on the BIND server itself (mind you I never edited the resolv file or the hosts file) I am presented with the updated info I posted in the question which leads me to think... well I have no idea actually :P
Aug
12
comment BIND Name Servers aren't returning my site
An access-list? Not that I can find at least. Looking in the conf file reveals nothing and Webmin I find "Access Control List" is empty.
Aug
12
comment BIND Name Servers aren't returning my site
@Chida yes BIND is running. and listening on both my IP addresses on port 53
Aug
10
comment BIND Name Servers aren't returning my site
As far as I know the firewall is off.
Aug
10
awarded  Scholar
Aug
10
accepted Can't create a working init.d for Apache 2.4.2 on CentOS
Aug
10
asked BIND Name Servers aren't returning my site
Jul
30
awarded  Commentator
Jul
30
comment Can't create a working init.d for Apache 2.4.2 on CentOS
Thanks I'll take a look
Jul
29
awarded  Editor
Jul
29
revised Can't create a working init.d for Apache 2.4.2 on CentOS
deleted 4199 characters in body
Jul
29
comment Can't create a working init.d for Apache 2.4.2 on CentOS
So I've discovered that it's not deleting the pid file so running status says dead but pid file exists. But the command is there to remove it it seems. I've updated my origonal post with my latest script.
Jul
29
comment Can't create a working init.d for Apache 2.4.2 on CentOS
Wait, it still is failing to stop. It says the pid file isn't running. I have PidFile set to /var/run/httpd.pid in my httpd.conf and the script has the same path assigned to the pidfile path.
Jul
29
comment Can't create a working init.d for Apache 2.4.2 on CentOS
This worked! I also changed the start section to use apachectl and it seems to be working. Last question though, Is it possible to have it print the [ OK ] and [ FAILED ] depending on what happens? Or is that dependent on apachectl?
Jul
28
comment Can't create a working init.d for Apache 2.4.2 on CentOS
I'm sorry I meant stopping. It starts just fine. I have a lot on my mind at the moment. I can't remember it saying any errors. I'll get back on that.