Ok I've fixed that to be ns1.danielcproductions.net. And ns2.danielcproductions.net in the zone file now. It didn't complain about it before though, wonder why that is? Also, it let me change the soa which is odd. It was 2008021604 but I changed it back to 2008021601 and restarted named. Was I not suppose to change the soa back? If I wasn't, guess I should leave it how bind had it lol. I registered my nameservers with godaddy a long time ago. When should I be able to ping my name servers on the local box? When I ping them I get the following message: [root at web01 ~]# ping ns1.danielcproductions.net ping: unknown host ns1.danielcproductions.net [root at web01 ~]# [root at web01 ~]# ping ns2.danielcproductions.net ping: unknown host ns2.danielcproductions.net [root at web01 ~]# When I do an nslookup it says: [root at web01 ~]# nslookup ns1.danielcproductions.net Server: 10.1.110.101 Address: 10.1.110.101#53 ** server can't find ns1.danielcproductions.net: NXDOMAIN [root at web01 ~]# [root at web01 ~]# nslookup ns2.danielcproductions.net Server: 10.1.110.101 Address: 10.1.110.101#53 ** server can't find ns2.danielcproductions.net: NXDOMAIN [root at web01 ~]# This is on the local box where bind is running where these arrors are showing up at. Could it be that the name servers have to be cashed with bind first? Or could it be that port 53 has to be forwarded to the box running bind? As it stands now, port 53, DNS, is not forwarded anywhere. Again, thanks for the help. No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.516 / Virus Database: 269.20.6/1282 - Release Date: 2/15/2008 7:08 PM
