I have set up IPCop with the public address of my web server, and placed the server on the DMZ port with a private IP. I have set up all ports for mail and web to be directed to the server, and it all works fine for anyone coming from the outside. Users on the local network cannot access the server by domain name anylonger, so I am told I need to set up DNS on my private LAN. I have never done this, but I have a box that I can load RedHat 7.1 on. I would appreciate any detailed help someone could provide.


Thanks in advance


Raymond

Hey Raymond,


I'm having a similar problem, perhaps we could help each other out.....

My situation is like this....I've got a RH7.1 box that's setup as a "dial-in PPP server." I have been able to successfully dial in to the box, have the server answer the modem and negotiate/authenticate the user.....

Where things fall down is the DNS lookup. My client cannot resolve names to IP numbers. If I directly type in an IP number, it works.

I've read the docs from the web on DNS server types and setup.

What documentation do you have?

If we could both get this going, it would be cool.

Danny

Actually I believe Morton's problem is a tad different... correct me if im wrong... I think you are wanting to setup your own DNS server to respond to machines on your local network with your own hostname/domainname scheme, in other words, not the public DNS names like you find on the internet. For instance if you want to setup a domain called "myworld.com" with machines named "bob", "jim", and "steve", but not have to register them publically. So when a local machine says "nslookup jim.myworld.com" it comes back with whatever local ip you've assigned... 192.168.100.3, or whatever.

That sound about right?

That is exactly what I need to do (create DNS for a private network). I use webmin, so that may make it easier, but I can't seem to connect the dots at this time. Any help would be great!

Wouldn't the host responsible for DNS do both?

I could be really wrong, but my understanding is that DNS first checks the "local" hosts...i.e. for machines that it knows, then if not found, forwards to a "higher authority"....in a caching situation, it saves all previous DNS resolutions (for a while) and passes those to the clients if there are any repeat lookups. Wouldn't both cases require the same DNS solution?

In both cases, shouldn't the server (in Raymond's case, the mail/web server for intranet and my dial-in server connected to the cable modem) perform this function?

Perhaps this is the source of my confusion.


Danny

This is my scenerio:

I run IPCop with 3 interfaces. Red= Internet, orange=DMZ (my server is here), and green = local lan. Anyone on green can get everywhere they need to by domain name, except for the local mail/web server, which has to be reached by IP address. I need local DNS, so I can reach this server by domain name too, preferably by the same name the public reaches it.

Again, any help would be appreciated.

Yes, the answer to the problem is setting up a DNS server with your local IP network information. This server WILL also be able to resolve public hostnames/IP addresses as well if setup right.

Unfortunately, I've never done this, and I understand it's no easy feat, but I did find some sites on the subject:

http://www.ludd.luth.se/~kavli/BIND-FAQ.html
http://www.geckil.com/~harvest/dns/

Just out of curiosity, what OS are the machines on the local lan running?

I am running NT, Linux, WIn2000, and 98.

Thanks for the site, I will see what I can learn from them.