The problem is that the 2 nameservers for gildendkp.de give DIFFERENT answers for (some?) subdomains, only one of which is actually CORRECT[0]:
# host -t ns gildendkp.de
gildendkp.de name server ns.du-sys.de.
gildendkp.de name server ns10.schlundtech.de.
# host mea-requies.gildendkp.de ns.du-sys.de.
mea-requies.gildendkp.de has address 85.214.64.113
# host mea-requies.gildendkp.de ns10.schlundtech.de.
mea-requies.gildendkp.de has address 85.214.57.43
And this despite that the 2 nameservers claim to have the same serial on the zone gildendkp.de:
# host -t soa gildendkp.de ns10.schlundtech.de.
gildendkp.de has SOA record ns.du-sys.de. dunkelberg.du-sys.de. 2009081401 39940 7200 604800 86400
# host -t soa gildendkp.de ns.du-sys.de.
gildendkp.de has SOA record ns.du-sys.de. dunkelberg.du-sys.de. 2009081401 39940 7200 604800 86400
gildendkp.de, you have a DNS-problem.
For our guild, I'm having everyone "solve" this problem with an entry in the local hosts-File, which is very, very, very much an ugly hack (and'll need to be reversed once you get your setup under some semblance of control).
0: 85.214.57.43 gives a 301 (Moved
Permanently, which is extra un-helpful because the browser remembers that, well, pretty much
permanently) to
http://www.gildendkp.de, only 85.214.64.113 gives the actual wanted content.
cheers,
Barc