Re: This didn't work....

> 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 dc

Re: This didn't work....

- 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

Re: This didn't work....

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

This didn't work....

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 worked...exc