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


Click here to return to the 'Also Confused' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Also Confused
Authored by: cmccarthy on Dec 03, '02 11:41:50AM

Like a previous commenter, I am also confused as to how your setting up your Mac as a DNS server solved your problem of not being able to access your web server from outside your Airport network. You mentioned using a DynDNS hostname for your server before you switched to Airport. I also use a DynDNS hostname: I go to dyndns.org, set the IP address of the hostname to the IP address of the Airport Base Station as assigned by AT&T Broadband's DHCP, and set the Base Station to forward port 80 to my Linux box, whose statically-assigned address is 10.0.1.203.

So, exactly why is running your own DNS server necessary? And, if you are still using a DynDNS hostname, isn't it best not to try to set up your own DNS server for an address in DynDNS's domain? I feel like I must be missing something here. And thanks for good instructions on setting up a DNS server.



[ Reply to This | # ]