Ray, 1. Remove the root domain ( the forward lookup zone with a single . ) from your DNS server. After that the server should forward queries using root hints to the root servers. After you remove the root domain, you can srt your DNS server to use a forwarder, such as the IP address of your ISP's DNS server. You will probably find this faster than just hitting the root servers on the Internet. 2. I think XP doesn't try to resolve using the second server because it doesn't work that way. That second server is for when your client does not get a response from the primary DNS server. XP Pro uses DNS exclusively to participate in an AD domain. Here is a little experiment. Make your AD DNS server your primary. Then right click my computer and select "Manage". After that, try to add a domain user account to a local user group. No problem, right? Now, remove your AD DNS server as the primary (in fact, delete it from your TCP/IP settings all together. Now try to do the same thing. No dice! You shouldn't even be able to select the domain to add users from! -Rob -----Original Message----- From: windows2000-bounce@xxxxxxxxxxxxx [mailto:windows2000-bounce@xxxxxxxxxxxxx] On Behalf Of Ray at home Sent: Monday, January 27, 2003 10:35 PM To: windows2000@xxxxxxxxxxxxx Subject: [windows2000] Home DNS Server Hi list, Two questions: 1. I asked this before like a year ago, but now I forget and do not have any e-mails saved. Damn me! How can I use my own DNS server at home? I was doing it before until I had to rebuild my server due to lots of hardware failure. I installed Active Directory and DNS on my server. When using my server as my DNS server, I cannot resolve any Internet addresses. There was something I had to do to tell my server to forward all requests that it cannot answer. When looking at the DNS properties on the Forwarders tab, that option is grayed out indicating that the option is not available because the server is a root server. There was something that I did before that I know at least involved an asterisk I think! 2. What's the point of the alternate DNS option that has always existed on Windows clients? Right now, if I do not use my home server as my DNS server, I cannot be authenticated in the domain (probably because my domain name is an actual Inernet domain and it's trying to authenticate me out there. Whoops.). So, in order to map a drive to a share on my server, I need to change my DNS to my server. But then I cannot resolve addresses (see above). So, I figure, fine, DNS entry #1 is my server. DNS server #2 is my ISP's DNS server. Well, with that setting, when DNS #1 cannot resolve and address, I just get that "cannot resolve..." Why doesn't Windows (XP in this situation) try the second DNS entry which can resolve the name? Thanks a lot, Ray at home ******************************************************************** This Week's Sponsor: RTO Software - TScale TScale increases Terminal Server capacity. Get 30-40% more users per server to save $$$ and time. Add users now! - Not more servers. If you're using Citrix, you must learn about TScale! Free 30-day eval: http://www.rtosoft.com/Enter.asp?ID=80 ================================== To Unsubscribe, set digest or vacation mode or view archives use the below link. http://thethin.net/win2000list.cfm ******************************************************************** This Week's Sponsor: RTO Software - TScale TScale increases Terminal Server capacity. Get 30-40% more users per server to save $$$ and time. Add users now! - Not more servers. If you?re using Citrix, you must learn about TScale! Free 30-day eval: http://www.rtosoft.com/Enter.asp?ID=80 ================================== To Unsubscribe, set digest or vacation mode or view archives use the below link. http://thethin.net/win2000list.cfm