I don't thing this is a bind problem because this
particular network has some Microsoft DNS's that are doing
exactly the same thing.
There are several domains names that are broken in this
network and the symptome is always the same:
Dig +trace @localhost one.bad.domain.co
In article ,
Martin McCormick wrote:
> I don't thing this is a bind problem because this
> particular network has some Microsoft DNS's that are doing
> exactly the same thing.
>
> There are several domains names that are broken in this
> network and the symptome is always the same:
Hi Martin,
Just to clarify, how many domain names are doing this for you? Are they
all remote domains, or are some of them okstate.edu domains?
John
--
John Miller
Systems Engineer
Brandeis University
johnm...@brandeis.edu
On 10/30/2012 04:10 PM, Martin McCormick wrote:
I don't thin
John Miller writes:
> Just to clarify, how many domain names are doing this for you? Are they
> all
> remote domains, or are some of them okstate.edu domains?
They are all remote as far as I can tell.
I will have some answers for Barry Margolin's questions a bit
later. It seems like the tear of
In message <201210302010.q9ukaytl064...@x.it.okstate.edu>, Martin McCormick wri
tes:
> I don't thing this is a bind problem because this
> particular network has some Microsoft DNS's that are doing
> exactly the same thing.
>
> There are several domains names that are broken in this
>
5 matches
Mail list logo