Thanx a lot, using the "option domain-name-servers" it worked perfect but .....
What if my ISP change the DNS servers addresses ??
Note that using your ISP's nameservers is usually quicker, since one assumes that the ISP runs a pretty professional operation, that their DNS server is hit by thousands of people, and so their cache will be better than yours. So, my preferred option is to set up a caching nameserver on your gateway or firewall system (a caching nameserver is one that only helps clients resolve queries, but does not serve any specific zones). For this you need at least the "bind" and "caching-nameserver" RPMs although I always install the "bind-utils" as well.
At the top of your /etc/named.conf file, inside the "options" block, add in the following lines:
forward first;
forwarders { 168.234.135.2; 168.234.135.3; };My complete options block looks like this:
options {
directory "/var/named";
version "No."; forward first;
forwarders { 168.234.135.2; 168.234.135.3; }; listen-on { 192.168.0.1; 127.0.0.1; };
};That way your nameserver will check your ISP's nameservers first to see if they know the answer, and if they don't answer will check the root servers. So you are protected against your ISP's nameservers changing, and your clients will get quicker answers overall. Now, just point your internal clients to your local nameserver.
Make sense?
-- Rodolfo J. Paiz rpaiz@xxxxxxxxxxxxxx
-- Shrike-list mailing list Shrike-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/shrike-list
