Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the 'Why to setup a dns server' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Why to setup a dns server
Authored by: benoitc on Dec 03, '02 06:56:39PM

When you configure the Airport Base station, you can set it to do port mapping (not port fowarding) on port 80 or any other port to allow a machine from the outside to access to a machine on the lan on this port. So anybody can access to to your domain mydomain.dyndns.org from the outside. Buy when you want to access to mydomain.dyndns.org from a machine behind the Airport Base Station (on the wlan), you can't because there ise no reverse mapping on NAT. And this is often the case with NAT router. So why not to access to the machine with the internal ip if you are on the wlan ?
Because if you do virtual hosting on apache, as I do, you need to access to the domain name nbot the IP.

So that's why I setup a DNS server ;)



[ Reply to This | # ]
Why to setup a dns server
Authored by: physicsGuy on Dec 05, '02 04:22:31AM

I'm still confused. If what you just said makes any sense, your original explanation must have been wrong. In your original, you said you couldn't see your dyndns domain name from OUTSIDE. But now, it sounds like you were having trouble seeing it from inside.

I had the same problem, and first was running macDNS 1.0.4 under classic environment (klugy, I know) as a caching name server with domain resolution on the LAN and caching WAN addresses. Later, I switched to the equiv of a hosts file under netinfo.



[ Reply to This | # ]
Why to setup a dns server
Authored by: benoitc on Dec 09, '02 06:36:23PM

Outside can see my domain name but not my users on the lan. So I decide to install a DNS server that to set internal ip to access to my domain. So this is easy to laptop users to configure their connection.



[ Reply to This | # ]