ENUM Records Using DYNDNS.ORG

[Ron]

Is there a problem using dynamic ip addresses in ENUM records on the new e164.org server?

If I make my ENUM record sip/000@xxx.xxx.xxx.xxx, a scheduled diagnostic call works perfectly.

If I make my ENUM record sip/000@user.dyndns.org (which resolves to the IP address in the previous example), a scheduled diagnostic call fails (there's no sign of it from my end).

I have ENUM lookups implemented in my Asterisk server. If the ENUM record is using an IP address, a SIP ENUM record is returned and used properly and the call succeeds. If the ENUM record record is using dyndns.org, it appears two DNC (Do Not Call?) records are returned instead of a SIP and DNC record and my call fails.

Any idea what's going on here?

Ron