Re: Multiple DNS

On 2/19/06, Robert Slade <bsd@xxxxxxxxxxxxxxxx> wrote:
Hi,

I am looking for some advice. I have a network which is based on a
number of servers running FreeBsd 6.0 serving Win XP work stations. (yes
I know but..) The network is large enough to use DHCP and DNS for the
internal network, I have setup a DHCP server with a Dynamic DNS (Bind 9)
on one of the servers. That server is handling the LDAP side of the
domain.

There appears to be a fair bit of DNS Traffic which leads to a secondary
DNS being required to take some of the load as DNS lookup are slow. The
question I have is should I just setup a cashing DNS on another server
using the primary as a forwarder or even several servers eg the mail
server and the secondary LDAP server, or should I setup a proper
secondary DNS using my ISP as a forwarder with dynamic updates from the
primary.

Sorry if this is a bit vague, but I have no experience in this area.

Rob


_______________________________________________
freebsd-questions@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscribe@xxxxxxxxxxx"


A secondary server using the primary as a forwarder is
generally a better idea if the primary is stable enough.
The secondary will share some load without taking up
extra bandwidth.

In case the primary is not stable enough, or if you really
need to scale by 2 (i.e. share the load evenly between
the servers), you'll have to use the ISP's dns servers as
forwarders instead. This will cut the efficiency of your
DNS cache by two.

At our place (3000+ hosts) we have our primary on a
rock-solid box and secondaries using it as forwarder.
_______________________________________________
freebsd-questions@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscribe@xxxxxxxxxxx"

Relevant Pages

  • Re: Domain Replica
    ... reason for long boot time when none DNS server is available. ... DNS Client side Resolver service Query Process ... DNS Forwarder Resolution and Time Out Process: ...
    (microsoft.public.windows.server.general)
  • Issues migrating SBS 2003 domain to Server 2008 Standard
    ... We are stuck migrating our SBS 2003 domain to Server 2008. ... Fatal Error:DsGetDcName (SRV-EXCH) call failed, ... Verify your Domain Name Sysytem (DNS) is ... network connectivity to a domain controller. ...
    (microsoft.public.windows.server.sbs)
  • Re: AD management snap in cannot find DC (netdiag /v workstation)
    ... The name.local entries are used by my apache server to implement ... change button, more button, the "Primary DNS suffix of this ... Attr: subschemaSubentry ... Owner of the binding path: ...
    (microsoft.public.windows.server.active_directory)
  • Re: AD management snap in cannot find DC (netdiag /v workstation)
    ... button, more button, the "Primary DNS suffix of this computer", it should ... The Security System could not establish a secured connection with the server ... Attr: subschemaSubentry ... Owner of the binding path: ...
    (microsoft.public.windows.server.active_directory)
  • Re: AD management snap in cannot find DC (netdiag /v workstation)
    ... DNS Host Name: tonyb-pc.imageproc.imageproc.com ... Testing IpConfig - pinging the DHCP Server... ... Attr: subschemaSubentry ... Owner of the binding path: ...
    (microsoft.public.windows.server.active_directory)