Secondary DNS Problem (slv2.1und1.de) Maybe somebody out here can help me, i am truely stuck. We're currently evaluating a root server running Plesk 7.5.2 on Suse 9.1 at 1and1 (Germany). We're trying to setup DNS Servers. As Primary DNS, we're using: ns.myserver.de As Secondary DNS we were given: slv2.1und1.de by our provider. Primary DNS is working properly, however: changes made to a domain in Plesk never propagate to slv2.1und1.de. In other words: i've setup: www.clientdomain.com. Now, I do aCode: dig @ns.myserver.de clientdomain.com and i get the proper answer. Now, if I try aCode:dig @slv2.1und1.de clientdomain.com it turns out that slv2.1und1.de has no info for clientdomain.com I changed the default DNS Templates and I've added slv2.1und1.de's IP address to the ACL List in Plesk. Also made sure that the DNS settings for clientdomain.com is matching. To the best of my knowledge, which admittedly isn't much, these are correct. According to /var/log/messages notifications are sent by named to somehwere. But i do not see any indication that slv2.1und1.de actually did transfer the zones. If it helps, i'll create a textfile with named.conf, zone files, and anything else that might prove helpful, just let me know if there is anything that might prove helpful. I can add .com/net domains to this server, as they only require 1 ns to be working. But trying to add a .de domain for example fails, because they need both ns to respond. Dnsreport.com reports slv2.1und1.de as lame server when i check clientdomain.com there. Something is wrong, but i have no clue what and how to fix this. My ISP (1and1) just informed me that they dont know and wont be able to get back to me for another week at least.. Can anybody help?