Have a question that pertains to 2000 server domains and DNS. Looking for any and all opinions on the subject.
I'm a working consultant and I run across this issue so often and i'm sure many others do too. 2000 server with domain and DNS not configured properly (or not at all).
Keep in mind, I normally work with smaller networks, 5 to 50 machines.
When I setup a server, I ask the client if there's anything special he/she needs. Do they have a website and where is it located. Most likely, the domain name is registered thru verisign or what have you, and the actual site is on their ISP web hosting. Nothing really special right? No need for shared domains...
So I ordinarily set up the DNS as domain.local. Takes a half hour to set up, test it for errors with a win2k workstation, and move on. No errors on the server, no errors on workstations, everyones happy and the client saves money that could have gone into troubleshooting...
What's everyones take on this? i'm curious
Thanks.
~ Whether you think you can or can't, you're right. Henry Ford~
I'm a working consultant and I run across this issue so often and i'm sure many others do too. 2000 server with domain and DNS not configured properly (or not at all).
Keep in mind, I normally work with smaller networks, 5 to 50 machines.
When I setup a server, I ask the client if there's anything special he/she needs. Do they have a website and where is it located. Most likely, the domain name is registered thru verisign or what have you, and the actual site is on their ISP web hosting. Nothing really special right? No need for shared domains...
So I ordinarily set up the DNS as domain.local. Takes a half hour to set up, test it for errors with a win2k workstation, and move on. No errors on the server, no errors on workstations, everyones happy and the client saves money that could have gone into troubleshooting...
What's everyones take on this? i'm curious
Thanks.
~ Whether you think you can or can't, you're right. Henry Ford~