Your content DNS server at 188.138.56.201 is misconfigured:
[M:\]dnsqry /serverip:188.138.56.201 a spotagel.com.
[0.0.0.0:0000] -> [188.138.56.201:0035] 30
Header: 0000 1+0+0+0, Q, , query, no_error
Question: spotagel.com. IN A
[188.138.56.201:0035] -> [0.0.0.0:0000] 30
Header: 0000 1+0+0+0, R, , query, refused
Question: spotagel.com. IN A
[M:\]dnsqry /serverip:188.138.56.201 a spotagel-emlak.com.
[0.0.0.0:0000] -> [188.138.56.201:0035] 36
Header: 0000 1+0+0+0, Q, , query, no_error
Question: spotagel-emlak.com. IN A
[188.138.56.201:0035] -> [0.0.0.0:0000] 97
Header: 0000 1+1+2+0, R, AUTH, query, no_error
Question: spotagel-emlak.com. IN A
Answer: spotagel-emlak.com. IN A 86400 188.138.56.201
Authority: spotagel-emlak.com. IN NS 86400 ns1.spotagel.com.
Authority: spotagel-emlak.com. IN NS 86400 ns2.spotagel.com.
[M:\]
There are various well-known causes for such an error, for different content DNS server softwares. For Microsoft's DNS server, for example, this can be caused by a DNS content server configured to be a secondary server for the "zone" having a problem replicating its database. For ISC's BIND, for example, one would look to "views" as a potential cause of this.