Ricardo Rodriguez Peralta wrote:
>
> This will be use as a local DNS to provide outside access. My current
> scenario is as follows:
>
> Two networks remotely connected throug a VPN. 2nd network goes out thru
> main one, so some unnecesary traffic is going on the network becuase
> people on the 2nd network is using my local DNS from main network.
>
> By setting up a DNS server on my second network, they will be able to go
> out without needing to use the VPN for it. In this case, I'll use VPN
> only to transaction processing within my DB. Right?
>
> That's why I'm planning to set up a local DNS server to provide access
> for users on 2nd network to go out.
If I understand correctly, then you may want to look into the dnsmasq
package instead of using a full-blown name server. It is not nearly as
full-featured as a package like bind, but it will provide a nice local
cache, and you can specify what name servers it will use forward
lookups, as well as how it does it. It also has other features that may
or may not be needed on your local lan. If you want, it can provide DNS
information for machines on your local network, as well as functioning
as a DHCP server. This is nice if you want to be able to access other
machines on the local network by name, without having to keep a local
/etc/hosts file up to date on each machine.
One thing the package will not do well is act as a domain DNS server.
For example, if I were hosting infinity-ltd.com on a local machine, and
needed to provide DNS information to the Internet from a local name
server, dnsmasq would not be the package to run.
Mikkel
--
Do not meddle in the affairs of dragons,
for thou art crunchy and taste good with Ketchup!
____________________________________________________
Want to buy your Pack or Services from Mandriva?
Go to http://store.mandriva.com
Join the Club : http://www.mandrivaclub.com
____________________________________________________
What I need is to provide DNS services to computers networked without a DNS server in that network. That's why these computers need to go thru a VPN to use my other network local DNS, got it?
Example:
Network A has a local DNS_A (I do not want all my computers in this network to use my ISP DNS) and every computer in network A ask this DNS_A how to get to infinity-ltd.com.
Network B do not have a local DNS_B provider so for this computer to be able to access infinity-ltd.com they would use my VPN to ask DNS_A how to get there.
I'm trying to avoid this extra traffic and hassel and use a Mandriva box as a DNS_B so they can go out without needing to get to network A first.
Let's say network A is down, this will also affect users in network B for no reason. By having their own local DNS users in network B could get to infinity-ltd.com and pay $1000 for proofreading advertising e-mail (I don't think you'll like to miss that because network A is down).
I think I should use a DNS service other than dnsmasq. Am I wrong?
Thank you.
