AD clients should get the DNS server's IP address for the DNS server set up for the AD domain only.
DNS may be set up on your AD server. In that case configure your router to give your clients the IP address of that server.
AD DNS servers must support SRV records. It may be possible the previous router did support SRV records and you were using it for DNS and now this router does not support SRV records.
You need to find out where the DNS server for the AD domain is/was and either replace it if it went away with the previous router or just have your router hand out the correct IP address if it is on the AD server.
hth DDS
"Daljit Singh Dhaliwal" <daljsd[ at ]hotmail.com> wrote in message news:1176716207.155972.175270[ at ]l77g2000hsb.googlegroups.com...
[Quoted Text] > hello, our old router died and was replaced with a basic BT one. now > we our PC's are taking a long time to log in. > > when I do a ipconfig /all from my PC I get (windows xp pro) > > IP Address 192.168.0.5 > subnet 255.255.255.0 > gateway 192.168.0.254 (firewall) > DHCP server 192.168.0.254 (firewall) > DNS Server 192.168.1.254 (BT router) > > this does not seem correct to me as the BT router does not have our BT > DNS servers entered in it (e.g. 212.21.......) > > > in our firewall configuration, dns is set to 192.168.1.254 > > if I get a new router like our old one (netgear) would it be possible > to enter the DNS server addresses we have and route our firewall dns > to the new router? > > I have checked our server (server 2003) and DHCP is not installed, > but DNS forwarders are installed with our BT DNS server addresses > added. >
|