On Thu, Aug 05, 2010 at 06:03:34PM -0700, CLOSE Dave (DAE) wrote:
> My company has two internal name servers accessible to me. One (PUB) is
> the usual Internet-facing server than can resolve most internal and all
> public names. The other (PRIV) is a special purpose server that only
> resolves
Assuming your private domain is mydomain.com, in the named.conf for the
public server put:
zone "mydomain.com"{
type forward;
forward only;
forwarders { ;}; };
The priv server needs to be authorative(and probably master) for
mydomain.com.
In resolv.conf on the clients, you only need the pub serv
My company has two internal name servers accessible to me. One (PUB) is
the usual Internet-facing server than can resolve most internal and all
public names. The other (PRIV) is a special purpose server that only
resolves names in a special private domain. If I list both servers in
resolv.conf,
Yes I have a wonderful script doing that for SSH but not for iptables.
For Bind, I must say that this problem appears 2-3 times a month, I can
therefore manage it manually for the moment...
Denis
Le 04.08.2010 14:36, Sten Carlsen a écrit :
You may want to consider how to trigger removal of
On 05.08.10 17:17, listus...@gmail.com wrote:
> We are in preparation to migrate all zones from a Bind 8 server to a Bind 9
> server. The Bind 9 servers are up and running in production. On the Bind 8
> server, we have a domain that has a very large zone file, it contains around
> 1,000 resource r
Hello all,
We are in preparation to migrate all zones from a Bind 8 server to a Bind 9
server. The Bind 9 servers are up and running in production. On the Bind 8
server, we have a domain that has a very large zone file, it contains around
1,000 resource records.
Ordinarily we would do AXFR from t
6 matches
Mail list logo
