error after backup

yatoula

New member
Joined
Sep 7, 2009
Messages
138
Location
France (Metz)
Hello, after installation of debian I installed DirectAdmin. No worries. But after installing my backup, many sites do not work, in fact they are not accessible via the browser.
If I change my host file with the IP address of the server I see the sites operate.
An example: http://www.mccreation.ch
 
i don't now what you say, excuse i am french ..

$TTL 14400
@ IN SOA ks369375.kimsufi.com. hostmaster.mccreation.ch. (
2010121000
14400
3600
1209600
86400 )

mccreation.ch. 14400 IN NS ks369375.kimsufi.com.
mccreation.ch. 14400 IN NS ns.kimsufi.com.

ftp 14400 IN A 94.23.44.18
localhost 14400 IN A 127.0.0.1
mail 14400 IN A 94.23.44.18
mccreation.ch. 14400 IN A 94.23.44.18
pop 14400 IN A 94.23.44.18
smtp 14400 IN A 94.23.44.18
www 14400 IN A 94.23.44.18

mccreation.ch. 14400 IN MX 10 mail



mccreation.ch. 14400 IN TXT "v=spf1 a mx ip4:94.23.44.18 ~all"
 
Last edited:
Are you running dns on a seperate server?

Make sure that your firewall is not blocking port 53 tcp and udp on your server.

This works (but doesnt look like the dns zone is there):
Code:
[admin@ns1 ~]$ dig @ns.kimsufi.com mccreation.ch

; <<>> DiG 9.3.6-P1 <<>> @ns.kimsufi.com mccreation.ch
; (1 server found)
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: REFUSED, id: 49004
;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;mccreation.ch.                 IN      A

;; Query time: 112 msec
;; SERVER: 213.186.33.199#53(213.186.33.199)
;; WHEN: Fri Dec 10 17:03:05 2010
;; MSG SIZE  rcvd: 31

This doesnt work:
Code:
[admin@ns1 ~]$ dig @94.23.44.18 mccreation.ch   

; <<>> DiG 9.3.6-P1 <<>> @94.23.44.18 mccreation.ch
; (1 server found)
;; global options:  printcmd
;; connection timed out; no servers could be reached
 
The two nameservers listed for the site (in the internet root servers) are:

ns.kimsufi.com
ks369375.kimsufi.com

The former doesn't have a zone file for the domain, and the latter isn't answering.

Note I fixed a misspelling in the thread subject to help in future searches.

Jeff
 
solved for yatoula,

the bind server was listening just on 127.0.0.1.

solved removing that line and restarting bind.

regards
 
Back
Top