Bringing DNS In-house
- From: "K" <no@xxxxxxxx>
- Date: Wed, 5 Nov 2008 08:57:40 -0000
I am looking to move the DNS name servers for our registered domain name
in-house away from our ISP as we are doing some resilience work and the ISP
cannot give me a better TTL than 4 hours, which is not conducive to good
failover (potential 8 hour update depending on when we register change).
I have 2 servers in my DMZ (Server 2003 SP2) which I have installed DNS on
and have created a primary zone named domainname.com on one and a secondary
zone named domainname.com on the other with transfers between them.
Do I need to set forwarders on these DNS servers to our ISP DNS servers?
Why or why not?
Also, when I populate this DNS with records, for example one of my web
servers in the DMZ, do I populate with the private address of the server or
the public address?
I assume the public addresses so that they are the ones handed out in
requests. But if this is the case, do I also need a CNAME for the private
address?
Apologies if these are basic questions but I have only ever worked with DNS
on private networks where resolution was internal only.
.
- Follow-Ups:
- Re: Bringing DNS In-house
- From: Phillip Windell
- Re: Bringing DNS In-house
- Prev by Date: Re: Machines not being registered in DNS anymore
- Next by Date: Duplicate PTR records in reverse lookup zone
- Previous by thread: Internal domain resolving to external domain not owned by us
- Next by thread: Re: Bringing DNS In-house
- Index(es):
Relevant Pages
|
