Guest idyleorfus@yahoo.com Posted October 8, 2007 Posted October 8, 2007 I was having trouble with all machines hanging up late in the day but found that the group policy for each workstation was set to auto renew the network login after logged on for approximately 6-8 hours. I turned off the auto-renew feature which was giving me trouble because the DNS is NOT the local network but that of the ISP. I have each machine set up with a static IP and in so doing I cannot change the DNS to automatic. I must specify it which I did as the ISP primary and secondary. It plays havoc with the auto-renew feature on the system. Should I add the ISP DNS to the forwarder?? The only IP in the forwarder is 192.168.1.1 which is the router not the IP of my local server/DC which is 192.168.1.252. I'm confused about this. My understanding of DNS is much like fuzzy logic. Can someone help me?? Thanks....
Guest Danny Sanders Posted October 8, 2007 Posted October 8, 2007 Re: DNS lookup?? Is this a domain or a workgroup? hth DDS <idyleorfus@yahoo.com> wrote in message news:1191872040.046817.312340@d55g2000hsg.googlegroups.com... >I was having trouble with all machines hanging up late in the day but > found that the group policy for each workstation was set to auto renew > the network login after logged on for approximately 6-8 hours. I > turned off the auto-renew feature which was giving me trouble because > the DNS is NOT the local network but that of the ISP. I have each > machine set up with a static IP and in so doing I cannot change the > DNS to automatic. I must specify it which I did as the ISP primary > and secondary. It plays havoc with the auto-renew feature on the > system. > > Should I add the ISP DNS to the forwarder?? The only IP in the > forwarder is 192.168.1.1 which is the router not the IP of my local > server/DC which is 192.168.1.252. > > I'm confused about this. My understanding of DNS is much like fuzzy > logic. Can someone help me?? Thanks.... >
Guest idyleorfus@yahoo.com Posted October 8, 2007 Posted October 8, 2007 Re: DNS lookup?? On Oct 8, 5:29 pm, "Danny Sanders" <DSand...@NOSPAMciber.com> wrote: > Is this a domain or a workgroup? > > hth > DDS > > <idyleor...@yahoo.com> wrote in message > > news:1191872040.046817.312340@d55g2000hsg.googlegroups.com... > > > > >I was having trouble with all machines hanging up late in the day but > > found that the group policy for each workstation was set to auto renew > > the network login after logged on for approximately 6-8 hours. I > > turned off the auto-renew feature which was giving me trouble because > > the DNS is NOT the local network but that of the ISP. I have each > > machine set up with a static IP and in so doing I cannot change the > > DNS to automatic. I must specify it which I did as the ISP primary > > and secondary. It plays havoc with the auto-renew feature on the > > system. > > > Should I add the ISP DNS to the forwarder?? The only IP in the > > forwarder is 192.168.1.1 which is the router not the IP of my local > > server/DC which is 192.168.1.252. > > > I'm confused about this. My understanding of DNS is much like fuzzy > > logic. Can someone help me?? Thanks....- Hide quoted text - > > - Show quoted text - This is Domain. NOT a workgroup. Domain is domain.local
Guest Danny Sanders Posted October 8, 2007 Posted October 8, 2007 Re: DNS lookup?? AD MUST have a DNS server setup for the AD domain. Basic AD DNS setup is to install DNS on the AD DC. Point it to itself for DNS in the properties of TCP/IP for DNS. Use the actual IP address NOT 127.0.0.1. Point all AD clients to the DNS server setup for the AD domain ONLY. Servers are AD clients also. For Internet access, either use root hints or set up forwarders and list your ISP's DNS server(s) as the forwarder. Listing any other DNS server on the AD client as "preferred" will cause long log in times, Group policy will not work and a whole list of things that if used in a production environment, will cause more problems. If any other DNS server is listed on the client as "alternate" except for the DNS server setup for the AD domain will cause mapped drives to become "unavailable" at times during the day. When you point the AD DNS server to itself for DNS this will allow the SRV records for your DCs to be registered in the zone the DNS server holds. Pointing your AD clients to the same DNS zone will allow your AD clients to "find" the SRV records they must find in order to "find" the domain. See: Setting Up the Domain Name System for Active Directory http://support.microsoft.com/default.aspx?scid=kb;en-us;237675 Best Practices for DNS Client settings in Windows 2000 server and in Windows Server 2003 http://support.microsoft.com/default.aspx?scid=kb;en-us;825036 How to configure DNS for Internet access in Windows Server 2003 http://support.microsoft.com/default.aspx?scid=kb;en-us;323380 hth DDS <idyleorfus@yahoo.com> wrote in message news:1191880990.902557.3690@57g2000hsv.googlegroups.com... > On Oct 8, 5:29 pm, "Danny Sanders" <DSand...@NOSPAMciber.com> wrote: >> Is this a domain or a workgroup? >> >> hth >> DDS >> >> <idyleor...@yahoo.com> wrote in message >> >> news:1191872040.046817.312340@d55g2000hsg.googlegroups.com... >> >> >> >> >I was having trouble with all machines hanging up late in the day but >> > found that the group policy for each workstation was set to auto renew >> > the network login after logged on for approximately 6-8 hours. I >> > turned off the auto-renew feature which was giving me trouble because >> > the DNS is NOT the local network but that of the ISP. I have each >> > machine set up with a static IP and in so doing I cannot change the >> > DNS to automatic. I must specify it which I did as the ISP primary >> > and secondary. It plays havoc with the auto-renew feature on the >> > system. >> >> > Should I add the ISP DNS to the forwarder?? The only IP in the >> > forwarder is 192.168.1.1 which is the router not the IP of my local >> > server/DC which is 192.168.1.252. >> >> > I'm confused about this. My understanding of DNS is much like fuzzy >> > logic. Can someone help me?? Thanks....- Hide quoted text - >> >> - Show quoted text - > > This is Domain. NOT a workgroup. Domain is domain.local >
Guest idyleorfus@yahoo.com Posted October 9, 2007 Posted October 9, 2007 Re: DNS lookup?? On Oct 8, 6:23 pm, "Danny Sanders" <DSand...@NOSPAMciber.com> wrote: > AD MUST have a DNS server setup for the AD domain. > Basic AD DNS setup is to install DNS on the AD DC. Point it to itself for > DNS in the properties of TCP/IP for DNS. Use the actual IP address NOT > 127.0.0.1. Point all AD clients to the DNS server setup for the AD domain > ONLY. Servers are AD clients also. For Internet access, either use root > hints or set up forwarders and list your ISP's DNS server(s) as the > forwarder. Listing any other DNS server on the AD client as "preferred" will > cause long log in times, Group policy will not work and a whole list of > things that if used in a production environment, will cause more problems. > If any other DNS server is listed on the client as "alternate" except for > the DNS server setup for the AD domain will cause mapped drives to become > "unavailable" at times during the day. When you point the AD DNS server to > itself for DNS this will allow the SRV records for your DCs to be registered > in the zone the DNS server holds. Pointing your AD clients to the same DNS > zone will allow your AD clients to "find" the SRV records they must find in > order to "find" the domain. > > See: > Setting Up the Domain Name System for Active Directoryhttp://support.microsoft.com/default.aspx?scid=kb;en-us;237675 > > Best Practices for DNS Client settings in Windows 2000 server and in Windows > Server 2003http://support.microsoft.com/default.aspx?scid=kb;en-us;825036 > > How to configure DNS for Internet access in Windows Server 2003http://support.microsoft.com/default.aspx?scid=kb;en-us;323380 > > hth > > DDS > > <idyleor...@yahoo.com> wrote in message > > news:1191880990.902557.3690@57g2000hsv.googlegroups.com... > > > > > On Oct 8, 5:29 pm, "Danny Sanders" <DSand...@NOSPAMciber.com> wrote: > >> Is this a domain or a workgroup? > > >> hth > >> DDS > > >> <idyleor...@yahoo.com> wrote in message > > >>news:1191872040.046817.312340@d55g2000hsg.googlegroups.com... > > >> >I was having trouble with all machines hanging up late in the day but > >> > found that the group policy for each workstation was set to auto renew > >> > the network login after logged on for approximately 6-8 hours. I > >> > turned off the auto-renew feature which was giving me trouble because > >> > the DNS is NOT the local network but that of the ISP. I have each > >> > machine set up with a static IP and in so doing I cannot change the > >> > DNS to automatic. I must specify it which I did as the ISP primary > >> > and secondary. It plays havoc with the auto-renew feature on the > >> > system. > > >> > Should I add the ISP DNS to the forwarder?? The only IP in the > >> > forwarder is 192.168.1.1 which is the router not the IP of my local > >> > server/DC which is 192.168.1.252. > > >> > I'm confused about this. My understanding of DNS is much like fuzzy > >> > logic. Can someone help me?? Thanks....- Hide quoted text - > > >> - Show quoted text - > > > This is Domain. NOT a workgroup. Domain is domain.local- Hide quoted text - > > - Show quoted text - Danny, Thank you so much for the explanation. I had already entered the ISP DNS intot he forwarder, But left my server id is preferred I'll make it 3rd in line after my ISP Primary and Secondary and see if that helps. You're discussion is exactlhy what I'm experiencing. Thanks once again.
Recommended Posts