> > internally, my network uses the main.gaddis.org. subdomain, > > which doesn't exist outside of the internal network. i run > > nameservers on the internal side which are authoritative for > > main.gaddis.org. subdomain. any machine inside the network that > > looks up (for example) www.main.gaddis.org gets the a record > > from the internal nameservers, pointing at 192.168.0.x. anyone > > outside of my network (e.g. on the public internet) that does a > > lookup for the same host gets redirected to my external ip. > > then i have 80/tcp port-forwarded into the network to the > > 192.168.0.x address... if you understand that. > > If I understand you, your local DNS only revolves for names within your > internal domain.
my local dns servers are only *authoritative* for names in my internal domain. if they are unable to answer a query, they forward the dns request on to my isp's nameservers for resolution. > Your solution sounds nice as it would solve another of my problems: the > naming of my machine. Right now I access it using its IP. I could have > changed the host file on all our local machines, but that's not really a > good solution. hosts file sucks, imo. :) > But it's probably faster than any other as we only have 10-20 machines, > and less than 5 really need access to this server now. > The DNS seems the perfect solution but I was trying to avoid it. > But that seems like I can't. i've of the belief that if you have more than two or three machines, you implement dns. once set up and running, it's 100 times easier to maintain than running around and updating 20 hosts files everytime you add another host, change a hosts ip address, etc. > But then I probably have to change the network config of all our machines > to point to this local DNS. Am I correct? yes, but that's not much of an issue. on linux machines, you simply modify /etc/resolv.conf to point at your local dns server. on windows clients you go just into the tcp/ip properties and change the value for the dns servers. your local dns server can be configured (as mine is) to forward any requests it can't answer to another dns server (e.g. your isp). this is what i do, and it works beautifully. dns can be somewhat of a chore to get up and running for the neophyte, but once it's running, it "just works"(tm). hth, j. -- Jeremy L. Gaddis <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <http://www.gaddis.org/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
