DNS vs Windows Domains
-
I've been fighting a long battle to make DNS work in Win2K. Most of the problem is certainly my own ignorance, but perhaps someone here can enlighten me. My server and its rarely used clients are members of the Windows domain "myplace.com," and I have registered an Internet domain by the same name. My registrar, Register.com, maintains the primary DNS SOA for the Internet domain, but when Windows installs DNS it creates a default zone and insists on making itself the SOA. This seems to be a conflict, as only one SOA can exist for a zone. My only reason for using DNS locally is that I want to gain experience with Active Directory, and AD requires a DNS server. The symptoms of the problem are two-fold: the netdiag utility reports that there are no DC records for this Domain Controller registered with any DNS system [fatal error], and the System log fills completely every two or three days with 5774 errors. I've exhausted every MS KB article that mentions this error and none come close. Is there any way to resolve this? It would seem from my research that no one else in the entire world has ever run into this scenario, and I find that hard to believe. The DNS books and chapters I've read imply that it's a simple matter of setting up a zone, but the instructions don't work, and none mention the fact that Windows creates its own default site, nor give any suggestions about what to do with it. Any clues would be most welcome! "Please don't put cigarette butts in the urinal. It makes them soggy and hard to light" - Sign in a Bullhead City, AZ Restroom
-
I've been fighting a long battle to make DNS work in Win2K. Most of the problem is certainly my own ignorance, but perhaps someone here can enlighten me. My server and its rarely used clients are members of the Windows domain "myplace.com," and I have registered an Internet domain by the same name. My registrar, Register.com, maintains the primary DNS SOA for the Internet domain, but when Windows installs DNS it creates a default zone and insists on making itself the SOA. This seems to be a conflict, as only one SOA can exist for a zone. My only reason for using DNS locally is that I want to gain experience with Active Directory, and AD requires a DNS server. The symptoms of the problem are two-fold: the netdiag utility reports that there are no DC records for this Domain Controller registered with any DNS system [fatal error], and the System log fills completely every two or three days with 5774 errors. I've exhausted every MS KB article that mentions this error and none come close. Is there any way to resolve this? It would seem from my research that no one else in the entire world has ever run into this scenario, and I find that hard to believe. The DNS books and chapters I've read imply that it's a simple matter of setting up a zone, but the instructions don't work, and none mention the fact that Windows creates its own default site, nor give any suggestions about what to do with it. Any clues would be most welcome! "Please don't put cigarette butts in the urinal. It makes them soggy and hard to light" - Sign in a Bullhead City, AZ Restroom
I have done this once before and set it up (Using Microsoft Small Business Server) so that the external domain and the internal domain were different. For example, the external domain hosted by my ISP was set up for 'companyname.com' and the internal domain was set up for 'companyname.local'. All that needs to be done then is to have the ISP point the MX records to the IP address of the server for email name resolution (and some other things need to be done inside of Exchange as well). Here is a decent tech note to get you started: http://support.microsoft.com/default.aspx?scid=kb;EN-US;296250[^]
Paul Watson wrote: "At the end of the day it is what you produce that counts, not how many doctorates you have on the wall." George Carlin wrote: "Don't sweat the petty things, and don't pet the sweaty things." Jörgen Sigvardsson wrote: If the physicists find a universal theory describing the laws of universe, I'm sure the asshole constant will be an integral part of that theory.
-
I have done this once before and set it up (Using Microsoft Small Business Server) so that the external domain and the internal domain were different. For example, the external domain hosted by my ISP was set up for 'companyname.com' and the internal domain was set up for 'companyname.local'. All that needs to be done then is to have the ISP point the MX records to the IP address of the server for email name resolution (and some other things need to be done inside of Exchange as well). Here is a decent tech note to get you started: http://support.microsoft.com/default.aspx?scid=kb;EN-US;296250[^]
Paul Watson wrote: "At the end of the day it is what you produce that counts, not how many doctorates you have on the wall." George Carlin wrote: "Don't sweat the petty things, and don't pet the sweaty things." Jörgen Sigvardsson wrote: If the physicists find a universal theory describing the laws of universe, I'm sure the asshole constant will be an integral part of that theory.
I hadn't seen that before, though I spent 4 years trying to make a SBS4.5 network do anything at all correctly. Worst technical recommendation I ever made... I'd really like to find a solution that doesn't require renaming the internal network, as that has a lot of repercussions I don't want to deal with. Surely there's some way to accomplish this - it isn't that unusual a situation. If nothing else works, though, I guess I'll have to resort to doing so. "Please don't put cigarette butts in the urinal. It makes them soggy and hard to light" - Sign in a Bullhead City, AZ Restroom