exdos
asked on
what is the correct process of forwarding DNS requests
we have a 2003 server installed under the domain name of server2
the other server (windows 2000 server) domain name server1 is also the dns and dhcp server. can somebody give me some instructions (or point me to some useful websites) on how to configure the servers in order for server2 (windows2003server) to forward the dns requests to server1(windows2000)
just another quick question. dns... does this have anything to do with the logging on process ie when you type a user name and password and press enter does dns have anything to do the with the process that occurs next
thanks
the other server (windows 2000 server) domain name server1 is also the dns and dhcp server. can somebody give me some instructions (or point me to some useful websites) on how to configure the servers in order for server2 (windows2003server) to forward the dns requests to server1(windows2000)
just another quick question. dns... does this have anything to do with the logging on process ie when you type a user name and password and press enter does dns have anything to do the with the process that occurs next
thanks
ASKER
reason for the the post is as you said the logon is taking 5 minutes.
do i have to use the forwarding option on server2 to point to server one?
do i have to use the forwarding option on server2 to point to server one?
ASKER
sorry simon can you expand on your comment please
Is the second server a domain controller?
Does the second server have DNS server installed on it?
Forwarders are only used for a DNS server to do lookup from the Internet when responding to the request from the client. You don't actually need forwarders in most cases - Windows 2003 is quite capable of doing lookups on its own.
Simon.
Does the second server have DNS server installed on it?
Forwarders are only used for a DNS server to do lookup from the Internet when responding to the request from the client. You don't actually need forwarders in most cases - Windows 2003 is quite capable of doing lookups on its own.
Simon.
ASKER
hi
yes the second server is a DC
dns is running as a forward lookup zone ( under which is the server1)
yes the second server is a DC
dns is running as a forward lookup zone ( under which is the server1)
To add to Simon's information:
If the DNS is Active Directory integrated, then both DCs running DNS should have the same records. You can enable Forwarding from each DNS server to the ISP's DNS server for Internet lookups.
If you are having login delays there are several things to look at. I'm not sure I understand your setup - are these servers in two different domains or are they simply 2 servers in the same domain? If you used Server1 and Server2 as actual domain names then this is the problem. Single-label DNS is a bad thing, it caused immense problems.
Please clarify your environment a little more clearly before we continue with answers.
If the DNS is Active Directory integrated, then both DCs running DNS should have the same records. You can enable Forwarding from each DNS server to the ISP's DNS server for Internet lookups.
If you are having login delays there are several things to look at. I'm not sure I understand your setup - are these servers in two different domains or are they simply 2 servers in the same domain? If you used Server1 and Server2 as actual domain names then this is the problem. Single-label DNS is a bad thing, it caused immense problems.
Please clarify your environment a little more clearly before we continue with answers.
Seeing your post above, I would install DNS server on to the second server. Create a new AD integrated zone that matches the zone on your first machine. Wait for AD to propagate the records across.
Then adjust the DNS settings as I have previously indicated.
However you do need to provide some more information on the environment in order to confirm whether my approach is correct.
Simon.
Then adjust the DNS settings as I have previously indicated.
However you do need to provide some more information on the environment in order to confirm whether my approach is correct.
Simon.
ASKER
sorry just to clarify we have we have two seperate domains on the same lan.
one network is for student data win2000 server
one for admin work (the new 2003 server)
both machines are dc's
please ask if any more info is required
one network is for student data win2000 server
one for admin work (the new 2003 server)
both machines are dc's
please ask if any more info is required
you need to really set up ONE domain and set the permissions properly,, or you could set up one parent domain and 2 child domains,, so it would then be like
parent= domain.com
child1= students.domain.com
child2= admin.domain.com
parent= domain.com
child1= students.domain.com
child2= admin.domain.com
if you go with the parent/child setup you would need 3 DCs though,, one to host the parent,, and an additional one for each child
ASKER
set the permissions properly
expand please
expand please
ASKER
we have we have two seperate domains on the same lan.
one network is for student data win2000 server
one for admin work (the new 2003 server)
would this really apply?
if you go with the parent/child setup you would need 3 DCs though,, one to host the parent,, and an additional one for each child
one network is for student data win2000 server
one for admin work (the new 2003 server)
would this really apply?
if you go with the parent/child setup you would need 3 DCs though,, one to host the parent,, and an additional one for each child
rightclick on any file/folder and choose permissions,,,, from there give admins access to what they need,,, give students access to what they need
Wait a minute. COULDN'T he just (Yes I am not sure)
Why not set up the second DOMAIN (server2) so it operates just like the first DOMAIN (server1). When I say operates just like create the same DNS forwarders etc out to the ISP etc. Of course each domain will be seperate from each other.
Then set up trusts between them???
It sounds like that most users will only use one domain anyway so it should be fairly simple.
BUT one of you AD gurus will have to comment further as I am not testing here <G>..
DC
Why not set up the second DOMAIN (server2) so it operates just like the first DOMAIN (server1). When I say operates just like create the same DNS forwarders etc out to the ISP etc. Of course each domain will be seperate from each other.
Then set up trusts between them???
It sounds like that most users will only use one domain anyway so it should be fairly simple.
BUT one of you AD gurus will have to comment further as I am not testing here <G>..
DC
ASKER
i don't feel i am getting anywhere here.
domain server1 is a windows 2000 server dc running dhcp and dns. The old server2 (nt4 server) did not have dns or dhcp enabled as the windows 2000 server was handling dchp and dns quiries. we bought a new server that had windows 2003 onit and copied accross the data from the nt4 server.
A forwarder was setup on the windows 2003 server to point to the windows 2000 server, because logon on was taking forever. (was this the correct move not sure!) however logon is still taking a good 4-5 minutes.
as the old nt4server was getting the windows 2000 server to handle dns quries i would like to have the same sort of set up on the windows 2003 server doing the same thing, sending requests for dns query resolving to the windows 2000 server
thanks for taking time to read this thread
domain server1 is a windows 2000 server dc running dhcp and dns. The old server2 (nt4 server) did not have dns or dhcp enabled as the windows 2000 server was handling dchp and dns quiries. we bought a new server that had windows 2003 onit and copied accross the data from the nt4 server.
A forwarder was setup on the windows 2003 server to point to the windows 2000 server, because logon on was taking forever. (was this the correct move not sure!) however logon is still taking a good 4-5 minutes.
as the old nt4server was getting the windows 2000 server to handle dns quries i would like to have the same sort of set up on the windows 2003 server doing the same thing, sending requests for dns query resolving to the windows 2000 server
thanks for taking time to read this thread
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
However all you need to do is ensure that your domain controller is pointing to itself for DNS in Network Configuration. Any client machines - be it member servers or workstations should point to the domain controller ONLY for DNS.
If you are using DHCP then you should configure nameservers (option 005) and DNS servers (option 006) with the IP address of your domain controller.
If you have multiple domain controllers then you should point them at themselves for primary and each other for secondary.
That is it.
Simon.