Windows dns slave

Nothing in DNS is capable of "pushing. There is a "Notify" feature on the Master the Primary zone that will notify servers that have Secondary copies when something changes in the Primary zone to come and get it, so to speak. Stubs "pull" only the NS records of the zone from the Master. This posting is provided AS-IS with no warranties or guarantees and confers no rights. Ace, let me try "interpreting" the question; what I suspect is that Chris has the following kind of setup.

Now, if my guess is correct, what Chris wants is to publish the "adzone. If that's the case, then a possible solution would be ticking the "BIND secondaries" in the Windows DNS servers, enabling notifies and zone transfers for "adzone. Thank you all for the info it's been helpful. What is happening is we are in the process of migrating off of Novell into an existing AD structure. Workstation resolution is done currently through WINS.

A consultant has suggested that we switch to Integrated DNS for the AD environment as sub-domain to our existing domain.

Catch they would have to share the same reverse lookup zone ip range We have concerns with this plan and want another cleaner solution. Just a though. Let's say your current zone in Novell is "contoso. Whether you enter the zone and server manually or use the Browse shortcut, click Next to get the next window, shown in Figure At this point, the process of creating a primary master zone and a slave zone really diverge.

This is the screen where you specify where this name server will get the zone data. We need to tell wormhole to load the zone from terminator , the primary master. In fact, on this screen you can specify multiple IP addresses.

In advanced and complicated configurations, sometimes there are multiple primaries or multiple sources from which a slave can get the zone information. The DNS console supports those configurations. You could also just specify the IP address of another slave after that of the primary: in case the primary is down, this slave can load from another slave. Of course, Movie U. Then click Next. As a general rule, when you add another name server for a zone, you also need to add an NS record for it.

Remember that all changes to a zone are made on the primary and propagate automatically to the slaves. In our case, we need to add an NS record for wormhole to the movie. So we highlight movie. To add another, click Add Enter the name and IP address of the slave name server and click OK. Now repeat this slave zone creation process with the Remember this SOA record for the movie.

The serial number applies to all the data within the zone. For most purposes the default configuration of BIND would satisfy points 2 and 3, however it is good practice to configure it explicitly if you intend to rely on its behaviour. The named configuration file must include a zone declaration for each zone to be served. Here is a suitable declaration for the zone example. Setting the type to slave specifies that the zone data is obtained from another nameserver.

The masters statement contains a list of nameservers from which zone data can be obtained. These need not be masters in the sense defined above: it is possible and sometimes necessary for a slave to obtain zone data from another slave. Zone files are optional for slave nameservers, but strongly recommended otherwise the slave will lose all knowledge of the zone content whenever it is restarted. It will not then be able to start serving the zone again until it has performed a zone transfer, and if the master is unavailable for any reason then the period of downtime could be substantial.

The latter method is preferred as it is both quicker and more efficient. BIND sends notifications by default, however it is good practice to enable them explicitly if they are an important part of the configuration. This can be done for individual zones:. The setting for a zone takes precedence, therefore if you use the latter method then you should check that it has not been overridden. The master needs to know which nameservers to notify.

By default it notifies the ones that have NS records, which for most purposes is sufficient. Nameservers that do not have NS records can be notified by adding an also-notify statement.

As previously this can be done either for an individual zone:. By default BIND allows zone transfers from anywhere. Opinion is divided as to whether this is good practice, and it is not unusual for a more restrictive policy to be imposed. The servers that are allowed to perform transfers are specified in an allow-transfer statement.

Active 2 years, 6 months ago. Viewed times. In Oracle Linux I have these configurations: named. Improve this question. Any errors in logs? The DLV has been deprecated and phased out since at least , be wary of following old pages.

RuiFRibeiro, no error in logs. Ok, I will try with underscores. RuiFRibeiro, it did not work — it dev.