Ugh, well, I can think of two ugly ways to do it.
Option 1: Set your server to host dyndns.org. home1.dyndns.org will always resolve to 192.168.0.10 for instance. Note that this will, um, break any resolution for anything other than the fakey DNS records you create in your bogus dyndns.org zone. Yuck.
Option 2: If you don’t want to break resolution for everything ending in dyndns.org (including http://www.dyndns.org! ) , use another of their free domains, or fork over the money to dyndns.org for your own domain name. dynadrian isn’t taken 🙂 Have your server serve up your bogus domain to the local network, but everyone outside your local network will get resolution from dyndns.org.
In either case, point your internal clients to your server for DNS service, and allow your DNS server to recursively look up DNS for everything else it is not already serving.
Ugly.
Comments are closed