Forward lookup zone for dyndns.org

[grimstoner]

Hi...

We have a computer setup in our office for source control. I've setup our ADSL router to forward the relevant ports to this computer, and it's accessible from outside (our network) via a dyndns.org address. Works perfect.

Internally, I've setup a forward lookup zone in Windows Server 2k8 for dyndns.org, added a host to it (oursc.dyndns.org), and forwarded the traffic to the internal network address. Also works.

However, other dyndns.org addresses (i.e. members.dyndns.org) don't resolve, because I didn't add host records for them in the dyndns.org forward lookup zone. Is it possible to use a wildcard to have any other dyndns.org subdomains be resolved by dyndns themselves, excluding the one I specified (oursc)?

 

[T-Man]

I usually just add a record to the "hosts" file. Only problem is that it has to be done on each PC referencing that domain (oursc.dyndns.org)

 

[thisgeek]

However, other dyndns.org addresses (i.e. members.dyndns.org) don't resolve, because I didn't add host records for them in the dyndns.org forward lookup zone. Is it possible to use a wildcard to have any other dyndns.org subdomains be resolved by dyndns themselves, excluding the one I specified (oursc)?

I suggest you try adding a forwarder for dyndns.org on your server as well.
You do that in the main server properties.

Theoretically, then anything for dyndns.org that is not answered by your server will be sent to the forwarder.

I'm not sure if this will work, however.