- Original Message -
Hi Lawrence,
I'm going to answer your questions a bit out of order, but hopefully
things'll still be clear.
How do you have an AD domain where your AD servers aren't
authoritative for itself?
This is how our AD domain is set up -- the root of the AD
Probably should've wrote that is the first case it was:
$ORIGIN foo.example.com.
...
ads NS ads.foo.example.com.
...
ads A a.b.c.d
dc2 A a.b.c.e
dc3 A a.b.c.f
And, the modified case was:
$ORIGIN foo.example.com
...
ads NS dc2.foo.example.com.
NS
Had a strange problem where our servers couldn't resolve hosts in an AD
subdomain.
This was in the zone file:
$ORIGIN foo.example.com.
...
ads NS ads.foo.example.com
...
...
...
ads A a.b.c.d
...
...
...
They said if you used their ADS for lookups, things
Hi Lawrence,
I'm going to answer your questions a bit out of order, but hopefully
things'll still be clear.
How do you have an AD domain where your AD servers aren't authoritative
for itself?
This is how our AD domain is set up -- the root of the AD domain is
brandeis.edu, but the domain
4 matches
Mail list logo
