Archived from groups: microsoft.public.win2000.dns (More info?)
In news:MPG.1c05be89cd5dd6d9989a7d@news-server.columbus.rr.com,
Leythos <void@nowhere.org> made a post then I commented below
> In article <#E8TXjQzEHA.3708@TK2MSFTNGP14.phx.gbl>,
> lanwench@heybuddy.donotsendme.unsolicitedmail.atyahoo.com says...
>>> So, here's a question for you: Have you tried it exactly like I
>>> describe and seen the problem on YOUR networks? I'm not talking
>>> about some text- book lab example, I'm talking about a network with
>>> 50+ active nodes and multiple servers.
>>
>> I wouldn't dream of trying it. I don't see the point, when setting
>> it up in 'textbook fashion' works as well as it does. If your
>> internal DNS servers are falling down going boom on their own all
>> the time, that's another story!
>>
>> But again, to each his own.
>
> But this is what separates the brave, or sometimes stupid (not meaning
> you) from the rest of the world. I started working with DNS on Windows
> before I could find a good paper on it and before MS provided clear
> papers on it. The setups have been working for many years with nothing
> to report on as problems.
>
> I've learned a couple things, and don't take this wrong, I love the
> Windows platform, have many of them and make a living from them, but
> there is this old saying "There is the right way, the wrong way, and
> the Microsoft way". In my case, it's not the MS way, but it does not
> appear to be the wrong way in actual operation, at least not in any
> of the networks I've setup like this.
>
> I'll take everything under consideration, and I've not discounted any
> of it, but it's hard to see a reason to change when the current
> method is not degrading performance, has been working for years, and
> does not cause any unnecessary external traffic.
>
> Thanks for your time.
>
>
> --
I know this is late and haven't been following the thread, but as everyone's
trying to point out, you've been lucky with your configuration of not having
followed the recommended 'best practices' that everyone is suggesting and
the MS docs suggest.
Honestly, we like to recommend these and all best practices for anyone that
posts for help or suggestions here in these forums. This helps us in helping
them in eliminating the obvious when diagnosing a problem.
Even if you decide to continue your current configuration, with all due
respect, I really hope and ask of you that if you respond to posts here to
help others, that you recommended "best practices", for no matter what sort
of configuration, but especially DNS and AD.
Thank you.
Happy Thanksgiving.
--
Regards,
Ace
Please direct all replies ONLY to the Microsoft public newsgroups
so all can benefit.
This posting is provided "AS-IS" with no warranties or guarantees
and confers no rights.
Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft Windows MVP - Windows Server - Directory Services
Security Is Like An Onion, It Has Layers
HAM AND EGGS: A day's work for a chicken;
A lifetime commitment for a pig.
--
=================================
In news:MPG.1c05be89cd5dd6d9989a7d@news-server.columbus.rr.com,
Leythos <void@nowhere.org> made a post then I commented below
> In article <#E8TXjQzEHA.3708@TK2MSFTNGP14.phx.gbl>,
> lanwench@heybuddy.donotsendme.unsolicitedmail.atyahoo.com says...
>>> So, here's a question for you: Have you tried it exactly like I
>>> describe and seen the problem on YOUR networks? I'm not talking
>>> about some text- book lab example, I'm talking about a network with
>>> 50+ active nodes and multiple servers.
>>
>> I wouldn't dream of trying it. I don't see the point, when setting
>> it up in 'textbook fashion' works as well as it does. If your
>> internal DNS servers are falling down going boom on their own all
>> the time, that's another story!
>>
>> But again, to each his own.
>
> But this is what separates the brave, or sometimes stupid (not meaning
> you) from the rest of the world. I started working with DNS on Windows
> before I could find a good paper on it and before MS provided clear
> papers on it. The setups have been working for many years with nothing
> to report on as problems.
>
> I've learned a couple things, and don't take this wrong, I love the
> Windows platform, have many of them and make a living from them, but
> there is this old saying "There is the right way, the wrong way, and
> the Microsoft way". In my case, it's not the MS way, but it does not
> appear to be the wrong way in actual operation, at least not in any
> of the networks I've setup like this.
>
> I'll take everything under consideration, and I've not discounted any
> of it, but it's hard to see a reason to change when the current
> method is not degrading performance, has been working for years, and
> does not cause any unnecessary external traffic.
>
> Thanks for your time.
>
>
> --
I know this is late and haven't been following the thread, but as everyone's
trying to point out, you've been lucky with your configuration of not having
followed the recommended 'best practices' that everyone is suggesting and
the MS docs suggest.
Honestly, we like to recommend these and all best practices for anyone that
posts for help or suggestions here in these forums. This helps us in helping
them in eliminating the obvious when diagnosing a problem.
Even if you decide to continue your current configuration, with all due
respect, I really hope and ask of you that if you respond to posts here to
help others, that you recommended "best practices", for no matter what sort
of configuration, but especially DNS and AD.
Thank you.
Happy Thanksgiving.
--
Regards,
Ace
Please direct all replies ONLY to the Microsoft public newsgroups
so all can benefit.
This posting is provided "AS-IS" with no warranties or guarantees
and confers no rights.
Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft Windows MVP - Windows Server - Directory Services
Security Is Like An Onion, It Has Layers
HAM AND EGGS: A day's work for a chicken;
A lifetime commitment for a pig.
--
=================================
Facebook
Twitter
Instagram