Re: Forwarding request to another DNS server but the same domain

Hello, On 30.04.14 17:32, Jeronimo L. Cabral wrote: 1) Office 1: people work with some machines and fill up a local master zone "company.com" with records in DNS1 2) Office 2: people works with some others machines and fill up a local master zone "company.com" with another records in DNS2 So bo

Re: Forwarding request to another DNS server but the same domain

Either do as Kevin Darcy said or else use separate names: company.com office1.company.com office2.company.com The admin in office 2 updates the office2 zone. The dynamic updates in office 1 go to the office1 zone. The company.com zone delegates both. Everyone can find everything via that delega

Re: Forwarding request to another DNS server but the same domain

DNS1 with dynamic update and DNS2 with manually update On Wed, Apr 30, 2014 at 8:11 PM, Kevin Darcy wrote: > I'm still not understanding your constraints. If *all* updates come in > through Dynamic Update, then you don't need freeze/unfreeze. > >

Re: Forwarding request to another DNS server but the same domain

I'm still not understanding your constraints. If *all* updates come in through Dynamic Update, then you don't need freeze/unfreeze. - Kevin On 4/30/2014 6:47 PM, Jeronimo L. Cabral wrote: In office #1, the "company.com " master zone is updated automatically from som

Re: Forwarding request to another DNS server but the same domain

In office #1, the "company.com" master zone is updated automatically from some Windows machines inn DNS1 and in office #2 the same zone is updated manually in DNS2 by the administrator who shouldn't update (using freeze and unfreeze) the master zone from office #1. This is the scenario, and we need

Re: Forwarding request to another DNS server but the same domain

First of all, unless you need separate views for each office, don't go down that path. Why are you attempting this as opposed to standard master-slave replication? There's something else I'm not understanding here: why would recursive queries from one office go to the other office's nameservers?

Re: Forwarding request to another DNS server but the same domain

Oh, I thought this was an external-versus-internal scenario. But, this is even easier. A) One of the nameservers (pick DNS1 or DNS2) becomes a slave (of the "stealth" variety, if you want) of the other B) People use nsupdate to maintain the zone For security, TSIG-sign the updates. For fast c

Re: Forwarding request to another DNS server but the same domain

Dear John, this is my scenario: 1) Office 1: people work with some machines and fill up a local master zone "company.com" with records in DNS1 2) Office 2: people works with some others machines and fill up a local master zone "company.com" with another records in DNS2 So both office have a diffe

Re: Forwarding request to another DNS server but the same domain

Hi Jeronimo, First of all, please just tell us the real domain. Yes, we could try and talk about a fictitious "example.com" or "company.com," but having the real domain name lets us actually query your nameservers. Let me be sure I understand: you have two DNS servers. Each of them is authorita

Re: Forwarding request to another DNS server but the same domain

Being authoritative means that you know everything about the zone. If you know everything about a zone, why ask anyone else? Split DNS does not follow the DNS paradigm, so there is no "standard" way to implement it, and despite many people asking over the years, there is no "NXDOMAIN failover

Forwarding request to another DNS server but the same domain

Dear, I would like to ask for solution related with DNS (bind) configuration to allow forward requests to another DNS but related with the same domain. I'm asking about two authoritative name servers serving the same domain but with different zone file info on each and have one of them forward rec