named (bind) dosen't Start! Dns Resolve Problme!

S

server4irco

New member
Joined
Apr 5, 2009
Messages
2
Hi , I Have Urgent problme with my dns (named).
my dns dosen't work i searched in your froum's but no topics help me!
i do every thing en your's froum that about dns , bind , named! but any yhing work!

all of my services is run witout named! my named server is stop!
when i put this commands shows my any error
:
[root@server home]# /etc/init.d/named start
Starting named: [FAILED]
[root@server home]#





[root@server directadmin]# /sbin/service named reload
Reloading named: [FAILED]
[root@server directadmin]#


[root@server home]# service named start
Starting named: [FAILED]
[root@server home]#

and in my panel shows me

named Process is stopped

and when i start it in panel directadmin shows me!


An error has occurred

Details

/sbin/service named start 2>&1


i do any thing !

i remove bind and reinstall again! i get file from directadmin and install again and compile it again but dosen't work!!!!!!!!!!!!!!!!!!!!!!!!!!!!

i do any thing!
thi is very importand for me i have many site in my server and it is very bad for me becuse my all website is down 34 hours!!!!!!!!!!
plz help me!


this is my logs :


/var/log/directadmin/errortask.log

Code: 
2009:04:17-02:10:11: service named didn't start, re-starting it
2009:04:17-02:10:13: Error restarting service named : uid 0 gid 0 : /sbin/service named restart                         >>/dev/null 2>>/dev/null                     
2009:04:17-02:11:01: service named wasn't running, starting it
2009:04:17-02:11:01: Error starting service named : uid 0 gid 0 : /sbin/service named start                         >>/dev/null 2>>/dev/null                     
2009:04:17-02:11:11: service named didn't start, re-starting it
2009:04:17-02:11:13: Error restarting service named : uid 0 gid 0 : /sbin/service named restart                         >>/dev/null 2>>/dev/null                     
2009:04:17-02:12:01: service named wasn't running, starting it
2009:04:17-02:12:02: Error starting service named : uid 0 gid 0 : /sbin/service named start                         >>/dev/null 2>>/dev/null                     
2009:04:17-02:12:12: service named didn't start, re-starting it
2009:04:17-02:12:14: Error restarting service named : uid 0 gid 0 : /sbin/service named restart                         >>/dev/null 2>>/dev/null                     
2009:04:17-02:13:01: service named wasn't running, starting it
2009:04:17-02:13:01: Error starting service named : uid 0 gid 0 : /sbin/service named start                         >>/dev/null 2>>/dev/null                     
2009:04:17-02:13:11: service named didn't start, re-starting it
2009:04:17-02:13:13: Error restarting service named : uid 0 gid 0 : /sbin/service named restart                         >>/dev/null 2>>/dev/null                     
2009:04:17-02:14:01: service named wasn't running, starting it
2009:04:17-02:14:01: Error starting service named : uid 0 gid 0 : /sbin/service named start                         >>/dev/null 2>>/dev/null                     
2009:04:17-02:14:11: service named didn't start, re-starting it
2009:04:17-02:14:13: Error restarting service named : uid 0 gid 0 : /sbin/service named restart                         >>/dev/null 2>>/dev/null                     
2009:04:17-02:15:01: service named wasn't running, starting it
2009:04:17-02:15:01: Error starting service named : uid 0 gid 0 : /sbin/service named start                         >>/dev/null 2>>/dev/null                     
2009:04:17-02:15:11: service named didn't start, re-starting it
2009:04:17-02:15:13: Error restarting service named : uid 0 gid 0 : /sbin/service named restart                         >>/dev/null 2>>/dev/null                     
2009:04:17-02:16:01: service named wasn't running, starting it
2009:04:17-02:16:01: Error starting service named : uid 0 gid 0 : /sbin/service named start                         >>/dev/null 2>>/dev/null                     
2009:04:17-02:16:12: service named didn't start, re-starting it
2009:04:17-02:16:14: Error restarting service named : uid 0 gid 0 : /sbin/service named restart                         >>/dev/null 2>>/dev/null                     
2009:04:17-02:17:01: service named wasn't running, starting it
2009:04:17-02:17:01: Error starting service named : uid 0 gid 0 : /sbin/service named start                         >>/dev/null 2>>/dev/null                     
2009:04:17-02:17:11: service named didn't start, re-starting it
2009:04:17-02:17:13: Error restarting service named : uid 0 gid 0 : /sbin/service named restart                         >>/dev/null 2>>/dev/null                     
2009:04:17-02:18:01: service named wasn't running, starting it
2009:04:17-02:18:01: Error starting service named : uid 0 gid 0 : /sbin/service named start                         >>/dev/null 2>>/dev/null                     
2009:04:17-02:18:11: service named didn't start, re-starting it
2009:04:17-02:18:13: Error restarting service named : uid 0 gid 0 : /sbin/service named restart                         >>/dev/null 2>>/dev/null                     
2009:04:17-02:19:01: service named wasn't running, starting it
2009:04:17-02:19:01: Error starting service named : uid 0 gid 0 : /sbin/service named start                         >>/dev/null 2>>/dev/null                     
2009:04:17-02:19:11: service named didn't start, re-starting it
2009:04:17-02:19:13: Error restarting service named : uid 0 gid 0 : /sbin/service named restart                         >>/dev/null 2>>/dev/null                     
2009:04:17-02:20:01: service named wasn't running, starting it
2009:04:17-02:20:02: Error starting service named : uid 0 gid 0 : /sbin/service named start                         >>/dev/null 2>>/dev/null                     
2009:04:17-02:20:12: service named didn't start, re-starting it
2009:04:17-02:20:14: Error restarting service named : uid 0 gid 0 : /sbin/service named restart                         >>/dev/null 2>>/dev/null                     
2009:04:17-02:21:01: service named wasn't running, starting it
2009:04:17-02:21:01: Error starting service named : uid 0 gid 0 : /sbin/service named start                         >>/dev/null 2>>/dev/null                     
2009:04:17-02:21:11: service named didn't start, re-starting it
2009:04:17-02:21:13: Error restarting service named : uid 0 gid 0 : /sbin/service named restart                         >>/dev/null 2>>/dev/null                     
2009:04:17-02:22:01: service named wasn't running, starting it
2009:04:17-02:22:01: Error starting service named : uid 0 gid 0 : /sbin/service named start                         >>/dev/null 2>>/dev/null                     
2009:04:17-02:22:11: service named didn't start, re-starting it
2009:04:17-02:22:13: Error restarting service named : uid 0 gid 0 : /sbin/service named restart                         >>/dev/null 2>>/dev/null



/var/log/massages


Code: 
Apr 17 02:19:01 server named[19505]: starting BIND 9.3.4-P1 -u named
Apr 17 02:19:01 server named[19505]: found 4 CPUs, using 4 worker threads
Apr 17 02:19:01 server named[19505]: loading configuration from '/etc/named.conf'
Apr 17 02:19:01 server named[19505]: listening on IPv4 interface lo, 127.0.0.1#53
Apr 17 02:19:01 server named[19505]: listening on IPv4 interface venet0:0, 173.45.80.13#53
Apr 17 02:19:01 server named[19505]: listening on IPv4 interface venet0:1, 173.45.70.185#53
Apr 17 02:19:01 server named[19505]: listening on IPv4 interface venet0:2, 173.45.70.184#53
Apr 17 02:19:01 server named[19505]: could not configure root hints from 'named.ca': file not found
Apr 17 02:19:01 server named[19505]: loading configuration: file not found
Apr 17 02:19:01 server named[19505]: exiting (due to fatal error)
Apr 17 02:19:13 server named[19594]: starting BIND 9.3.4-P1 -u named
Apr 17 02:19:13 server named[19594]: found 4 CPUs, using 4 worker threads
Apr 17 02:19:13 server named[19594]: loading configuration from '/etc/named.conf'
Apr 17 02:19:13 server named[19594]: listening on IPv4 interface lo, 127.0.0.1#53
Apr 17 02:19:13 server named[19594]: listening on IPv4 interface venet0:0, 173.45.80.13#53
Apr 17 02:19:13 server named[19594]: listening on IPv4 interface venet0:1, 173.45.70.185#53
Apr 17 02:19:13 server named[19594]: listening on IPv4 interface venet0:2, 173.45.70.184#53
Apr 17 02:19:13 server named[19594]: could not configure root hints from 'named.ca': file not found
Apr 17 02:19:13 server named[19594]: loading configuration: file not found
Apr 17 02:19:13 server named[19594]: exiting (due to fatal error)
Apr 17 02:19:38 server named[19843]: starting BIND 9.3.4-P1 -u named
Apr 17 02:19:38 server named[19843]: found 4 CPUs, using 4 worker threads
Apr 17 02:19:38 server named[19843]: loading configuration from '/etc/named.conf'
Apr 17 02:19:38 server named[19843]: listening on IPv4 interface lo, 127.0.0.1#53
Apr 17 02:19:38 server named[19843]: listening on IPv4 interface venet0:0, 173.45.80.13#53
Apr 17 02:19:38 server named[19843]: listening on IPv4 interface venet0:1, 173.45.70.185#53
Apr 17 02:19:38 server named[19843]: listening on IPv4 interface venet0:2, 173.45.70.184#53
Apr 17 02:19:38 server named[19843]: could not configure root hints from 'named.ca': file not found
Apr 17 02:19:38 server named[19843]: loading configuration: file not found
Apr 17 02:19:38 server named[19843]: exiting (due to fatal error)
Apr 17 02:20:02 server named[20320]: starting BIND 9.3.4-P1 -u named
Apr 17 02:20:02 server named[20320]: found 4 CPUs, using 4 worker threads
Apr 17 02:20:02 server named[20320]: loading configuration from '/etc/named.conf'
Apr 17 02:20:02 server named[20320]: listening on IPv4 interface lo, 127.0.0.1#53
Apr 17 02:20:02 server named[20320]: listening on IPv4 interface venet0:0, 173.45.80.13#53
Apr 17 02:20:02 server named[20320]: listening on IPv4 interface venet0:1, 173.45.70.185#53
Apr 17 02:20:02 server named[20320]: listening on IPv4 interface venet0:2, 173.45.70.184#53
Apr 17 02:20:02 server named[20320]: could not configure root hints from 'named.ca': file not found
Apr 17 02:20:02 server named[20320]: loading configuration: file not found
Apr 17 02:20:02 server named[20320]: exiting (due to fatal error)
Apr 17 02:20:14 server named[20403]: starting BIND 9.3.4-P1 -u named
Apr 17 02:20:14 server named[20403]: found 4 CPUs, using 4 worker threads
Apr 17 02:20:14 server named[20403]: loading configuration from '/etc/named.conf'
Apr 17 02:20:14 server named[20403]: listening on IPv4 interface lo, 127.0.0.1#53
Apr 17 02:20:14 server named[20403]: listening on IPv4 interface venet0:0, 173.45.80.13#53
Apr 17 02:20:14 server named[20403]: listening on IPv4 interface venet0:1, 173.45.70.185#53
Apr 17 02:20:14 server named[20403]: listening on IPv4 interface venet0:2, 173.45.70.184#53
Apr 17 02:20:14 server named[20403]: could not configure root hints from 'named.ca': file not found
Apr 17 02:20:14 server named[20403]: loading configuration: file not found
Apr 17 02:20:14 server named[20403]: exiting (due to fatal error)
Apr 17 02:21:01 server named[21657]: starting BIND 9.3.4-P1 -u named
Apr 17 02:21:01 server named[21657]: found 4 CPUs, using 4 worker threads
Apr 17 02:21:01 server named[21657]: loading configuration from '/etc/named.conf'
Apr 17 02:21:01 server named[21657]: listening on IPv4 interface lo, 127.0.0.1#53
Apr 17 02:21:01 server named[21657]: listening on IPv4 interface venet0:0, 173.45.80.13#53
Apr 17 02:21:01 server named[21657]: listening on IPv4 interface venet0:1, 173.45.70.185#53
Apr 17 02:21:01 server named[21657]: listening on IPv4 interface venet0:2, 173.45.70.184#53
Apr 17 02:21:01 server named[21657]: could not configure root hints from 'named.ca': file not found
Apr 17 02:21:01 server named[21657]: loading configuration: file not found
Apr 17 02:21:01 server named[21657]: exiting (due to fatal error)
Apr 17 02:21:13 server named[21804]: starting BIND 9.3.4-P1 -u named
Apr 17 02:21:13 server named[21804]: found 4 CPUs, using 4 worker threads
Apr 17 02:21:13 server named[21804]: loading configuration from '/etc/named.conf'
Apr 17 02:21:13 server named[21804]: listening on IPv4 interface lo, 127.0.0.1#53
Apr 17 02:21:13 server named[21804]: listening on IPv4 interface venet0:0, 173.45.80.13#53
Apr 17 02:21:13 server named[21804]: listening on IPv4 interface venet0:1, 173.45.70.185#53
Apr 17 02:21:13 server named[21804]: listening on IPv4 interface venet0:2, 173.45.70.184#53
Apr 17 02:21:13 server named[21804]: could not configure root hints from 'named.ca': file not found
Apr 17 02:21:13 server named[21804]: loading configuration: file not found
Apr 17 02:21:13 server named[21804]: exiting (due to fatal error)
Apr 17 02:22:01 server named[22061]: starting BIND 9.3.4-P1 -u named
Apr 17 02:22:01 server named[22061]: found 4 CPUs, using 4 worker threads
Apr 17 02:22:01 server named[22061]: loading configuration from '/etc/named.conf'
Apr 17 02:22:01 server named[22061]: listening on IPv4 interface lo, 127.0.0.1#53
Apr 17 02:22:01 server named[22061]: listening on IPv4 interface venet0:0, 173.45.80.13#53
Apr 17 02:22:01 server named[22061]: listening on IPv4 interface venet0:1, 173.45.70.185#53
Apr 17 02:22:01 server named[22061]: listening on IPv4 interface venet0:2, 173.45.70.184#53
Apr 17 02:22:01 server named[22061]: could not configure root hints from 'named.ca': file not found
Apr 17 02:22:01 server named[22061]: loading configuration: file not found
Apr 17 02:22:01 server named[22061]: exiting (due to fatal error)
Apr 17 02:22:13 server named[22159]: starting BIND 9.3.4-P1 -u named
Apr 17 02:22:13 server named[22159]: found 4 CPUs, using 4 worker threads
Apr 17 02:22:13 server named[22159]: loading configuration from '/etc/named.conf'
Apr 17 02:22:13 server named[22159]: listening on IPv4 interface lo, 127.0.0.1#53
Apr 17 02:22:13 server named[22159]: listening on IPv4 interface venet0:0, 173.45.80.13#53
Apr 17 02:22:13 server named[22159]: listening on IPv4 interface venet0:1, 173.45.70.185#53
Apr 17 02:22:13 server named[22159]: listening on IPv4 interface venet0:2, 173.45.70.184#53
Apr 17 02:22:13 server named[22159]: could not configure root hints from 'named.ca': file not found
Apr 17 02:22:13 server named[22159]: loading configuration: file not found
Apr 17 02:22:13 server named[22159]: exiting (due to fatal error)
Apr 17 02:23:01 server named[22377]: starting BIND 9.3.4-P1 -u named
Apr 17 02:23:01 server named[22377]: found 4 CPUs, using 4 worker threads
Apr 17 02:23:01 server named[22377]: loading configuration from '/etc/named.conf'
Apr 17 02:23:01 server named[22377]: listening on IPv4 interface lo, 127.0.0.1#53
Apr 17 02:23:01 server named[22377]: listening on IPv4 interface venet0:0, 173.45.80.13#53
Apr 17 02:23:01 server named[22377]: listening on IPv4 interface venet0:1, 173.45.70.185#53
Apr 17 02:23:01 server named[22377]: listening on IPv4 interface venet0:2, 173.45.70.184#53
Apr 17 02:23:01 server named[22377]: could not configure root hints from 'named.ca': file not found
Apr 17 02:23:01 server named[22377]: loading configuration: file not found
Apr 17 02:23:01 server named[22377]: exiting (due to fatal error)
Apr 17 02:23:13 server named[22451]: starting BIND 9.3.4-P1 -u named
Apr 17 02:23:13 server named[22451]: found 4 CPUs, using 4 worker threads
Apr 17 02:23:13 server named[22451]: loading configuration from '/etc/named.conf'
Apr 17 02:23:13 server named[22451]: listening on IPv4 interface lo, 127.0.0.1#53
Apr 17 02:23:13 server named[22451]: listening on IPv4 interface venet0:0, 173.45.80.13#53
Apr 17 02:23:13 server named[22451]: listening on IPv4 interface venet0:1, 173.45.70.185#53
Apr 17 02:23:13 server named[22451]: listening on IPv4 interface venet0:2, 173.45.70.184#53
Apr 17 02:23:13 server named[22451]: could not configure root hints from 'named.ca': file not found
Apr 17 02:23:13 server named[22451]: loading configuration: file not found
Apr 17 02:23:13 server named[22451]: exiting (due to fatal error)
Apr 17 02:24:01 server named[23741]: starting BIND 9.3.4-P1 -u named
Apr 17 02:24:01 server named[23741]: found 4 CPUs, using 4 worker threads
Apr 17 02:24:01 server named[23741]: loading configuration from '/etc/named.conf'
Apr 17 02:24:01 server named[23741]: listening on IPv4 interface lo, 127.0.0.1#53
Apr 17 02:24:01 server named[23741]: listening on IPv4 interface venet0:0, 173.45.80.13#53
Apr 17 02:24:01 server named[23741]: listening on IPv4 interface venet0:1, 173.45.70.185#53
Apr 17 02:24:01 server named[23741]: listening on IPv4 interface venet0:2, 173.45.70.184#53
Apr 17 02:24:01 server named[23741]: could not configure root hints from 'named.ca': file not found
Apr 17 02:24:01 server named[23741]: loading configuration: file not found
Apr 17 02:24:01 server named[23741]: exiting (due to fatal error)
Apr 17 02:24:13 server named[23830]: starting BIND 9.3.4-P1 -u named
Apr 17 02:24:13 server named[23830]: found 4 CPUs, using 4 worker threads
Apr 17 02:24:13 server named[23830]: loading configuration from '/etc/named.conf'
Apr 17 02:24:13 server named[23830]: listening on IPv4 interface lo, 127.0.0.1#53
Apr 17 02:24:13 server named[23830]: listening on IPv4 interface venet0:0, 173.45.80.13#53
Apr 17 02:24:13 server named[23830]: listening on IPv4 interface venet0:1, 173.45.70.185#53
Apr 17 02:24:13 server named[23830]: listening on IPv4 interface venet0:2, 173.45.70.184#53
Apr 17 02:24:13 server named[23830]: could not configure root hints from 'named.ca': file not found
Apr 17 02:24:13 server named[23830]: loading configuration: file not found
Apr 17 02:24:13 server named[23830]: exiting (due to fatal error)
Apr 17 02:25:02 server named[24405]: starting BIND 9.3.4-P1 -u named
Apr 17 02:25:02 server named[24405]: found 4 CPUs, using 4 worker threads
Apr 17 02:25:02 server named[24405]: loading configuration from '/etc/named.conf'
Apr 17 02:25:02 server named[24405]: listening on IPv4 interface lo, 127.0.0.1#53
Apr 17 02:25:02 server named[24405]: listening on IPv4 interface venet0:0, 173.45.80.13#53
Apr 17 02:25:02 server named[24405]: listening on IPv4 interface venet0:1, 173.45.70.185#53
Apr 17 02:25:02 server named[24405]: listening on IPv4 interface venet0:2, 173.45.70.184#53
Apr 17 02:25:02 server named[24405]: could not configure root hints from 'named.ca': file not found
Apr 17 02:25:02 server named[24405]: loading configuration: file not found
Apr 17 02:25:02 server named[24405]: exiting (due to fatal error)
Apr 17 02:25:14 server named[24509]: starting BIND 9.3.4-P1 -u named
Apr 17 02:25:14 server named[24509]: found 4 CPUs, using 4 worker threads
Apr 17 02:25:14 server named[24509]: loading configuration from '/etc/named.conf'
Apr 17 02:25:14 server named[24509]: listening on IPv4 interface lo, 127.0.0.1#53
Apr 17 02:25:14 server named[24509]: listening on IPv4 interface venet0:0, 173.45.80.13#53
Apr 17 02:25:14 server named[24509]: listening on IPv4 interface venet0:1, 173.45.70.185#53
Apr 17 02:25:14 server named[24509]: listening on IPv4 interface venet0:2, 173.45.70.184#53
Apr 17 02:25:14 server named[24509]: could not configure root hints from 'named.ca': file not found
Apr 17 02:25:14 server named[24509]: loading configuration: file not found
Apr 17 02:25:14 server named[24509]: exiting (due to fatal error)


plz help me!!!!!!!!!!!!!!1
 
[root@server home]# service named restart
Stopping named: [ OK ]
Starting named: [FAILED]
[root@server home]#
 
These 2 lines describe the problem:
Code: 
Apr 17 02:25:14 server named[24509]: could not configure root hints from 'named.ca': file not found[FONT=monospace]
[/FONT]Apr 17 02:25:14 server named[24509]: loading configuration: file not found
 
Hello,

If you're missing the named.ca, then type:
Code: 
cd /var/named
wget http://www.directadmin.com/named.ca
/sbin/service named start
John
 
BIND was designed to be both a caching (also called resolving) nameserver, and an authoritative nameserver, both at the same time. You use a caching nameserver to find the IP#s of other domain names than the ones you host (for example, google.com), while others use your authoritative nameserver to find the IP#s of the domains you host.

Over the years, hackers have found ways to break into caching nameservers and to then be able to get them to give out incorrect information; this is called Cache Poisoning (good explanation on Wikipedia).

So best practices dictate that you don't use your local nameserver (the one on your webserver) as a caching nameserver. Turn it off in your named.conf file by adding this line:
Code: 
recursion no;
as the bottom line inside the options section (the first section of the named.conf file); then restart BIND.

However, before you do this, make sure you're not using your local nameserver inside your /etc/resolv.conf file:

First make sure you've got at least two nameserver lines. Make sure they both use IP#s as arguments. Make sure they do NOT have either 127.0.0.1 or any of your own IP#s. They should be IP#s give to you as caching nameservers by your upstream connectivity provider (who may call them resolving nameservers).

There have been discussions on these forums for using OpenDNS nameservers; if you use them be sure you read their site as to how to join them and set your preferences (you'll have to give them the IP#s of all the servers using them) so you'll get raw DNS responses instead of (for example) filtering and redirecting.

But if your provider has a good connection to Level3 or Verizon you may be able to get away with this example:
Code: 
nameserver 4.2.2.3
nameserver 4.2.2.2
The above two lines are all you really need in your /etc/resolv.conf file IF they work for you.

To make sure they work, simply try these two lookups from your command line (on the server from which you're testing):
Code: 
$ dig @4.2.2.2 +short www.nobaloney.net
and
Code: 
$ dig @4.2.2.3 +short www.nobaloney.net
which should both give you the IP# of my server (you can tell by doing a reverse lookup):
Code: 
$ dig @4.2.2.2 -x XX.YY.ZZ.AA +short
(of course replacing XX.YY.ZZ.AA with the IP# you get from one of the first two requests. Then do a whois on the domain name you get to see if you can figure out if it's mine or not (or at least registered by me).

If it all works you can use those two lines in your /etc/resolv.conf file and your local nameserver won't be at risk as a caching nameserver and won't need the named.ca file.

So then you should take out the zone line in /etc/named.conf which references the named.ca file.

Now I've not only explained how it all works, how to tighten up your nameserver security, but also how to trace who owns what.

:)

Jeff
 
You must log in or register to reply here.
Back
Top