DNS, Linux and Active Directory Problem from Hell! :0)

[Guest]

Hi there peeps, I’m hoping someone out there will be able to confirm something for me. I have an issue with my 2000 domain and a DNS problem which is preventing me from installing additional active directory domain controllers into my existing domain. My company is part of a larger WAN that uses Redhat Linux servers to manage its DNS and other network services. In this instance I will call it example.co.uk. I have created my new 2000 domain (the only of its kind across the WAN) it is the only Win 2000 server within the WAN in a sub domain called mydomain.example.co.uk. It is obviously not the master and it points to two linux boxes as its primary and secondary DNS servers. The server and the new mycompany.example.co.uk zone have been added to the local DNS listings on the nearest Redhat Linux DNS servers that this PDC has as its primary and secondary lookups. The server functions on the network as a domain controller for my LAN ie people can authenticate with it, get their drive maps, shared printers etc. The local clients who log onto this 2000 domain and have this servers IP as their primary DNS have automatically been updated into the forward and reverse lookup zones on this PDC (so certainly from a local lookup point of view this seems to be working). My problem is that when I try to add active directory to another 2000 server in order to join it onto the network (in this case to construct a new 2000 excahnge server) I am not able to resolve the DNS it returns an error that “there is no domain controller available for the domain mydomain.example.co.uk†or “the server mypdc.mydomain.example.co.uk could not be contactedâ€. Now I have spoken to several people about this and done extensive reading and have been told that in order for this to be resolved as far as windows 2000 server is concerned, is that I need to have a windows 2000 active directory controller as the start or authority at the top of the DNS tree and that a Linuz box cannot do this? Can anyone shed any light on this. My understanding of DNS is not text book taught, but I’m pretty confident that I’ve covered all the obvious bases, my grey area is really what compatibility issues are there (if any) of interfacing with Redhat Linux. The solution I’ve been told for this will be for me to rebuild my domain outside of the existing WAN DNS ie mydomain.co.uk so that the 2000 Server is the start of authority and then get it listed with the Linux boxes to re-establish the WAN link. I will be eternally greatful for anyone who can shed a little bit of light on this as I have lots of people who are supposedly more technically qualified than me telling me two completely different things lol

Thankyou to anyone who can help! :0)

 

[Kevin D. Goodknecht [MVP]]

In

Hi there peeps, I'm hoping someone out there will be able to confirm
something for me. I have an issue with my 2000 domain and a DNS
problem which is preventing me from installing additional active
directory domain controllers into my existing domain. My company is
part of a larger WAN that uses Redhat Linux servers to manage its DNS
and other network services. In this instance I will call it
example.co.uk. I have created my new 2000 domain (the only of its
kind across the WAN) it is the only Win 2000 server within the WAN in
a sub domain called mydomain.example.co.uk. It is obviously not the
master and it points to two linux boxes as its primary and secondary
DNS servers. The server and the new mycompany.example.co.uk zone have
been added to the local DNS listings on the nearest Redhat Linux DNS
servers that this PDC has as its primary and secondary lookups. The
server functions on the network as a domain controller for my LAN ie
people can authenticate with it, get their drive maps, shared
printers etc. The local clients who log onto this 2000 domain and
have this servers IP as their primary DNS have automatically been
updated into the forward and reverse lookup zones on this PDC (so
certainly from a local lookup point of view this seems to be
working). My problem is that when I try to add active directory to
another 2000 server in order to join it onto the network (in this
case to construct a new 2000 excahnge server) I am not able to
resolve the DNS it returns an error that "there is no domain
controller available for the domain mydomain.example.co.uk" or "the
server mypdc.mydomain.example.co.uk could not be contacted". Now I
have spoken to several people about this and done extensive reading
and have been told that in order for this to be resolved as far as
windows 2000 server is concerned, is that I need to have a windows
2000 active directory controller as the start or authority at the top
of the DNS tree and that a Linuz box cannot do this? Can anyone shed
any light on this. My understanding of DNS is not text book taught,
but I'm pretty confident that I've covered all the obvious bases, my
grey area is really what compatibility issues are there (if any) of
interfacing with Redhat Linux. The solution I've been told for this
will be for me to rebuild my domain outside of the existing WAN DNS
ie mydomain.co.uk so that the 2000 Server is the start of authority
and then get it listed with the Linux boxes to re-establish the WAN
link. I will be eternally greatful for anyone who can shed a little
bit of light on this as I have lots of people who are supposedly more
technically qualified than me telling me two completely different
things lol!

Thankyou to anyone who can help! :0)

If all machines are pointing to the Linux for DNS then does the Linux DNS
have dynamic updates enabled to allow the creation of the DC's SRV records?
I would think not, what you should probably do is installl DNS on the DC
create a zone named "mydomain.example.co.uk" set it to allow dynamic
updates, then in the linux zone for "example.co.uk" delegate the name
"mydomain" to the DC "mypdc.mydomain.example.co.uk" and its IP address.
This will allow the DC to register its records in DNS so it can be found,
and allow you to keep your Linux DNS server in your NIC setup.
The DC will need its own address in its NIC for DNS only, And any DC you add
will need to use the first DC for DNS.

 

[Jonathan de Boyne Pollard]

A> It is obviously not the master [...]

That's not obvious at all. What makes you think that this is obvious?
You've chosen to run the content DNS service for that subdomain on
your Linux machines. However, it wasn't _necessary_ for you to choose
to do things that way.

A> Now I have spoken to several people about this and done
A> extensive reading [...]

<URL:http://microsoft.com./windows2000/techinfo/reskit/en-us/cnet/cncf_imp_bdvd.asp>
<URL:http://microsoft.com./technet/prodt...r/sag_DNS_imp_Interoperability.asp?frame=true>

 

[Guest]

Thankyou very much for your responses they have been most helpful.

I have been able to query these issues with the administrators who look after the Redhat DNS boxes and I am hoping that a resolution to this will be found today (I know naff all about Linux so checking myself is not the easiest of tasks).

Speak soon