>To help us correct this problem temporarily, we decided to pull the
>conducent.com zone and load it as a master in all our NT Bind servers even
>though we are not authoritative.
ok, that's certainly an interesting solution. and why not?
>The zone pulled via named-xfer runs fine locally.
yep, I just axfr'd 227 records from
ns1.conducent.com. sca02.sec.dns.exodus.net transfers, also. psinet.net's
dns's are refusing zone transfer.
The have 40+ A records for adsdl.conducent.com. I wonder if they have 40
distinct servers there?
>This prevents any interruptions due to this bug as I cannot tolerate ANY
>downtime. I'd rather be out-of-date on this domain than have problems.
yeah, sure. The world will still spin without conducent's ad servers.
>BTW, I don't know why the zone works fine when loaded as a master on NT Bind
>but not when queried remotely.
that's bugz for ya.
Len
Please visit http://www.ipswitch.com/support/mailing-lists.html
to be removed from this list.
