Nameserver not solved

M

Mdave

Verified User
Joined
Jan 17, 2006
Messages
5
Sorry fo my bad english.

I hope i'm in the good thread.

I have one problem,
a freash dediserver on , 3 IP
Master IP = 83.98.159.120
Ns1 = 83.98.159.121 ns1.alsjeblief.be
Ns2 = 83.98.159.122 ns1.alsjeblief.be

Domain = of course alsjeblief.be

Now , it's want resolved.
Dns Report say lame naamserver.
I do search on DA forum , and try many thinks , but nothing happend.

Domain and namservers are 100% registred.

Somoene any idee.??
Thx for help
 
Hello,

Code: 
[root@server]# dig alsjeblief.be @83.98.159.121 +nocomments

; <<>> DiG 9.2.1 <<>> alsjeblief.be @83.98.159.121 +nocomments
;; global options:  printcmd
;alsjeblief.be.                 IN      A
;; Query time: 139 msec
;; SERVER: 83.98.159.121#53(83.98.159.121)
;; WHEN: Tue Jan 17 15:08:05 2006
;; MSG SIZE  rcvd: 31

[root@server]# dig alsjeblief.be @83.98.159.122 +nocomments

; <<>> DiG 9.2.1 <<>> alsjeblief.be @83.98.159.122 +nocomments
;; global options:  printcmd
;alsjeblief.be.                 IN      A
;; Query time: 157 msec
;; SERVER: 83.98.159.122#53(83.98.159.122)
;; WHEN: Tue Jan 17 15:08:08 2006
;; MSG SIZE  rcvd: 31
So it looks like named is running and port 53 is open. That leaves the error to either named has not been restarted, or there is a syntax error in the zone causing it to not be included when named is reloaded.

Try restarting named, then check your /var/log/messages file for any errors relating to the domain.

John
 
I did it but ....
Error log from Named:

Jan 17 23:13:54 hosted-by named[9242]: shutting down
Jan 17 23:13:54 hosted-by named[9242]: stopping command channel on 127.0.0.1#953
Jan 17 23:13:54 hosted-by named[9242]: stopping command channel on ::1#953
Jan 17 23:13:54 hosted-by named[9242]: no longer listening on 127.0.0.1#53
Jan 17 23:13:54 hosted-by named[9242]: no longer listening on 83.98.159.120#53
Jan 17 23:13:54 hosted-by named[9242]: no longer listening on 83.98.159.121#53
Jan 17 23:13:54 hosted-by named[9242]: no longer listening on 83.98.159.122#53
Jan 17 23:13:54 hosted-by named[9242]: exiting
Jan 17 23:13:54 hosted-by named: named afgesloten succeeded
Jan 17 23:13:54 hosted-by named[11703]: starting BIND 9.2.4 -u named
Jan 17 23:13:54 hosted-by named[11703]: using 1 CPU
Jan 17 23:13:54 hosted-by named[11703]: loading configuration from '/etc/named.conf'
Jan 17 23:13:54 hosted-by named[11703]: /etc/named.conf:37: open: /etc/rndc.key: permission denied
Jan 17 23:13:54 hosted-by named[11703]: loading configuration: permission denied
Jan 17 23:13:54 hosted-by named[11703]: exiting (due to fatal error)
Jan 17 23:13:54 hosted-by named: named start op failed
Jan 17 23:14:01 hosted-by named[11721]: starting BIND 9.2.4 -u named
Jan 17 23:14:01 hosted-by named[11721]: using 1 CPU
Jan 17 23:14:01 hosted-by named[11721]: loading configuration from '/etc/named.conf'
Jan 17 23:14:01 hosted-by named[11721]: /etc/named.conf:37: open: /etc/rndc.key: permission denied
Jan 17 23:14:01 hosted-by named[11721]: loading configuration: permission denied
Jan 17 23:14:01 hosted-by named[11721]: exiting (due to fatal error)
Jan 17 23:14:01 hosted-by named: named start op failed


I think he can't find rndc.key

And i don't know what for rndc.key is
 
You must log in or register to reply here.
Back
Top