RE: i'm concerned about some RFC 2136 interoperability problems

[Raymond Forbes <rforbes@MICROSOFT.COM>]

For the record; 

microsoft has a primary dns server that is purely for handling the zones.
we don't want it queried from.  we have the name in the SOA to keep with the
standard. 

Raymond Forbes
Hostmaster
Microsoft Corp.

-----Original Message-----
From: Harald Tveit Alvestrand [mailto:Harald@Alvestrand.no]
Sent: Sunday, September 12, 1999 1:57 PM
To: James Gilroy (Exchange); Paul A Vixie; namedroppers@internic.net
Subject: RE: i'm concerned about some RFC 2136 interoperability problems


At 14:31 11.09.99 -0700, James Gilroy (Exchange) wrote:
> I made the change to put the A record in the additional section simply for
> efficiency.  My reading of the RFC (more or less the "nothing forbids it"
> argument you note below) suggested it was ok, and it is a piece of
> information that will be immediately desired by the client to complete the
> update.
>
> On the client side, the microsoft client will prefer to go to the primary
> name server given in the SOA, but if that seems to be unreachable it does
> the NS query and tries the update to each of the given servers in turn.
We
> have a couple of servers running recent BIND versions in the lab and the
> client has no trouble updating them.

>From a thread on the dnsop list: In some cases the owner of the zone does 
not *want* people to query the nameserver listed in the SOA.

In those cases, the SOA is not listed in the NS list when you ask for NS.

Quote from that debate (date Aug 23):

>> Do you know of any cases now where there is no overlap between SOA
>> and NS?
> li.org, slashdot.org, microsoft.com (!), for instance.
> more bizarre things happen - altavista.com uses a name in the SOA that
> has the same A as one of its NSes, but different name.
> microsoft looks as if it's round-robining its NS set, and my copy just
> happened not to include ns 1.
> the world is a strange place.

Not sure how this affects dynamic update.

                          Harald A

--
Harald Tveit Alvestrand, Maxware, Norway
Harald.Alvestrand@maxware.no