nsupdate problem

[Kevin Darcy]

With the BIND 9 version of nsupdate, there is a "server" command which forces
it to send the update to a particular nameserver.


- Kevin

jjhirschauer at duke-energy.com wrote:

> I started using invisible.duke-energy.com in the MNAME field of the SOA
> record on all of my internal zones. This seems to have caused a problem
> with the nsupdate command. When running an update the server seems to use
> the MNAME field to see who the master server is. If the name is invalid it
> seems that it looks to the NS records for the zone. My zones have 5 NS
> records each with one of them being the Master. Nsupdate starts working
> it's way through the list of nameservers it got from the NS records. It
> stops after 3 attempts. If the master is not one of the first three it
> just gives up with no update. Is there any way I can tell nsupdate which
> is the Master server without changing back the MNAME field?