Here is SOA in pri.wnof.com: $TTL 86400 @ IN SOA ns11.grfe.net. ray.grfe.com. ( 2011031702 ; serial, todays date + todays serial # 10800 ; refresh, seconds 3600 ; retry, seconds 604800 ; expire, seconds 86400 ) ; minimum, seconds ; mail A 38.99.159.173 wnof.com. A 38.99.159.173 wnof.com. MX 10 mail.wnof.com. wnof.com. NS ns11.grfe.net. wnof.com. NS ns12.grfe.net. www A 38.99.159.173 can I find SOA in anywhere else?
That looks ok, but your nameservers are not accessible: Code: server1:~# dig @ns11.grfe.net wnof.com ; <<>> DiG 9.6-ESV-R1 <<>> @ns11.grfe.net wnof.com ; (1 server found) ;; global options: +cmd ;; connection timed out; no servers could be reached server1:~# dig @ns12.grfe.net wnof.com ; <<>> DiG 9.6-ESV-R1 <<>> @ns12.grfe.net wnof.com ; (1 server found) ;; global options: +cmd ;; connection timed out; no servers could be reached server1:~# Did you open port 53 (TCP and UDP) in your firewall?
Yes port 53 is open. this name server was working perfect on ISPconfig2 with the same config. still more than 95 sites are working with this name server but I don't know why ns11 and ns12 are not reachable on this server!!
At least ns11 seems to work now: Code: server1:~# dig @ns11.grfe.net wnof.com ; <<>> DiG 9.6-ESV-R1 <<>> @ns11.grfe.net wnof.com ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 25319 ;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 1 ;; WARNING: recursion requested but not available ;; QUESTION SECTION: ;wnof.com. IN A ;; ANSWER SECTION: wnof.com. 86400 IN A 38.99.159.173 ;; AUTHORITY SECTION: wnof.com. 86400 IN NS ns11.grfe.net. wnof.com. 86400 IN NS ns12.grfe.net. ;; ADDITIONAL SECTION: ns12.grfe.net. 84143 IN A 38.99.159.170 ;; Query time: 103 msec ;; SERVER: 38.99.159.169#53(38.99.159.169) ;; WHEN: Wed Mar 23 18:24:41 2011 ;; MSG SIZE rcvd: 104 server1:~# dig @ns12.grfe.net wnof.com ; <<>> DiG 9.6-ESV-R1 <<>> @ns12.grfe.net wnof.com ; (1 server found) ;; global options: +cmd ;; connection timed out; no servers could be reached server1:~#
Thank you guys Falko, Stephan the domain is now up and working. I changed the named.conf to listen port 53 on my ns IP.