While Setup DNS For 1 Domain.de

One of our customers need to use a domain.de (.de ext), he registered the domain using godaddy, and godaddy have a few very special requirements for .de domains:

• The first 3 bits of the IP address (C-class) is different for each name server.
• A glue record is necessary for the domain on the name servers.
• The SOA (Start of Authority) must be within the following guidelines:

refresh : 10000 - 86400
retry: 1800 -28800
expire: 604800 - 3600000
ttl: 180 - 345600

This is all done, 2 different C class IPs for each name servers, glue record, and SOA has been configured between specified values. Because of the 2 C class, we created DNS at server1, and pointed all www traffic to server2 (where the domain.de will be hosted)

This is the DNS zone at server1 (an Ensim server):

$ORIGIN .
$TTL 3600 ; 1 hour
sitename.de IN SOA nameserver1.server.com. support@hostingcompany.com. (
2008010804 ; serial
10000 ; refresh (1 hour)
1800 ; retry (10 minutes)
604800 ; expire (2 weeks)
345600 ; minimum (1 hour)
)
NS nameserver1.server.com.
NS nameserver2.server2.com.
$TTL 86400 ; 1 day
A XX.XX.XX.XX
$ORIGIN sitename.de.
ftp A XX.XX.XX.XX
www A XX.XX.XX.XX

This is the DNS zone at server2 (an cPanel server):

; Modified by Web Host Manager
; Zone File for sitename.de
$TTL 3600
@ 86400 IN SOA nameserver2.server2.com. support@hostingcompany.com. (
2008010804
10000
1800
604800
345600
)

sitename.de. 86400 IN NS nameserver2.server2.com.
sitename.de. 86400 IN NS nameserver3.server2.com.

sitename.de. 14400 IN A XX.XX.XX.XX

localhost.sitename.de. 14400 IN A 127.0.0.1

sitename.de. 14400 IN MX 0 sitename.de.

mail 14400 IN CNAME sitename.de.
www 14400 IN A sitename.de.
ftp 14400 IN A XX.XX.XX.XX
While checking the domain at [url], an error appears:

Zone sitename.de.
Primary nameserver1.server.com. IP_ADDRESS_HERE
Secondary nameserver2.server2.com. IP_ADDRESS_HERE

Test results

---- fatal ----
f: [TEST SOA record present]: server failure (IN/SOA: sitename.de.)

* nameserver2.server.com./IP_ADDRESS_HERE

I have verified every single thing at sitename.de.db on both servers at /var/named/, disabled DNS Recursion protection, stopped firewall, and the error continues.

And the error as you can see only happens with SOA at second server.