Re: Case For Microsoft DNS v. BIND 9 - Or Best Practices For Coexisting

2009-02-08 Thread steve
Microsoft DNS can work well, HOWEVER much time needs to be spent understanding its operations. This is a VERY long winded post, so I hope no one gets upset, I realize this is not the MS DNS group LOL I am going to assume, that you are running an Active Directory Domain that includes

Re: Case For Microsoft DNS v. BIND 9 - Or Best Practices For Coexisting

2009-02-08 Thread Mark Andrews
One example in closing for ya, go try and get an RFC complient Bind server to respond to a request for name resoloution on a host that has an _ (underscore) in the name, MS allows this, and a zone transfer of this kinda stuff between and MS Server and a Bind server, can give you MUCH

Re: Case For Microsoft DNS v. BIND 9 - Or Best Practices For Coexisting

2009-02-07 Thread Danny Mayer
wiskbr...@hotmail.com wrote: The case the windows team made was ease of adding entries, you simply add into the MMC, or even easier, when you join a host into a domain, it adds itself. This is not even true. To add a host to a domain you have to register it manually, either by going into ADS

Case For Microsoft DNS v. BIND 9 - Or Best Practices For Coexisting

2009-02-06 Thread wiskbroom
Hello; My site is presently using a product derived from BIND-8 for internal DNS only. For years our Windows team has been arguing that they want to be non-dependent on the non-MS DNS servers; which they say causes them much grief on firmwide shutdown/bootups. Well, their concerns have

RE: Case For Microsoft DNS v. BIND 9 - Or Best Practices For Coexisting

2009-02-06 Thread Jeff Lightner
I don't see why it is either/or. Here we have Windoze DNS servers for internal lookups and Linux/BIND 9 DNS servers for external lookups. The internal servers refer all queries they aren't authoritative for to the external ones which in turn refer all queries for domains we don't own to the