I don't know if this is a bug or what, but if an existing DNS entry exists in the DNS Manager and say I need to change the IP address of that entry, simply editing the entry and saving the new entry does not update the DNS record. I actually have to delete the entry, empty the recycle bin, go back into the ISP Manager and re-save the site that I am trying to update. If I don't do that process, the changes to the DNS entry won't update. They update on my end, but the DNS records never change.
Did you change the dns entry in the dns manager or did you change the IP address of a website in isp-manager? Did the IP in the pri... doamin file changed?
I changed it in the IPS Manager, but it didn't change at all in the DNS Manager so I manually changed it. Now I am getting the following error and named won't even start now. Code: [root@server etc]# /etc/init.d/named start Starting named: Error in named configuration: zone 0.0.127.in-addr.arpa/IN: loaded serial 1997022700 dns_rdata_fromtext: pri.105.93.24.in-addr.arpa:23: near '@.vasceria.com.': bad name (check-names) zone 105.93.24.in-addr.arpa/IN: loading from master file pri.105.93.24.in-addr.arpa failed: bad name (check-names) _default/105.93.24.in-addr.arpa/IN: bad name (check-names) zone plastikracing.net/IN: loaded serial 2007082503 zone legionofshadows.net/IN: loaded serial 2007082502 zone plastikhosting.net/IN: loaded serial 2007082501 zone allash.com/IN: loaded serial 2007082502 zone vasceria.com/IN: loaded serial 2007082510 [FAILED] I've searched through /etc/named.conf /etc/named.caching-nameserver.conf /etc/named.rfc1912.zones and I don't see an @.vasceria.com anywhere.