Trouble w/ DynDNS over a bridged wireless network

[Murphy's Law]

I have a wireless network stretching across two buildings with a Dlink DI-624 acting as the main router and a WRT54G flashed w/ the latest Alchemy firmware running as a client/bridge in the second building. I have a server setup with a dynamic DynDNS service behind the second router.

Here's my problem. My server can connect to dyndns and update the ip address fine, but I cannot access my dyndns hostname through a web browser or SSH. What's odd is that I can ping my hostname and receive a response, but when I try to ping the ip address the hostname is attached to, I get a reponse timeout error. I've tried forwarding ports and enabling DDNS on both routers, neither of which work. I know this has something to do with the server being behind TWO routers, but I don't have a clue on how to go about fixing it.

[nstabl]

can you ping the router? does the true ip match what dyndns is translating to?

[Murphy's Law]

Yes, I can ping both routers and recieve a response. What do you mean by the true IP matching to what DynDNS is translating to? I've setup services on both no-ip and DynDNS, and they both detect the same external IP. Determing my IP from IP sites reports the same IP as well.

[nstabl]

u sound like u know what u doin, stil havent figured it out?