To the rest of the list, I'm sorry for letting this continue. This'll
really, honestly, truly be my last. You probably just want to hit
delete now.
On Mon, Mar 19, 2007 at 04:10:19PM +1100, Andrew Scott wrote:
>
> Tom,
>
> What drugs are you on, more than cold and flu that's for sure...
>
> DNS, is called a Domain Name Service as you damn well know. There is no fast
> rules on how to use this, except when you have a Domain Controller further
> up the link. If one like myself, and my System Administrator here at work,
> decides to create a DNS locally and internally for our servers and
> workstations then it is allowed, there is no improvement on the DNS.
Do you know that a Domain Name Server and a Domain Controller are
different things? Hint: one is a proprietary Windows concept, one is
standards-based.
> And what the hell is wrong or right about creating your own internal DC?
See above, we're talking about DNS here.
> Nothing, if that is what people want to do that is fine let them it still
> conforms to a standard it's just inside and internal / intranet / extranet
> system that's all. And you know something when was the last time you looked
> up a Blue Chip company, and looked at their DNS servers? I can tell you that
> every large bank in Australia has internal DNS servers setup along the names
> of something like:
>
> Exchange-mailserver.domaincontroller.machinename or something crazier.
>
> How is that breaking anything standard, it's a FQDN with the domain name as
> domaincontroller.machinename. Now that might be extreme, but who cares how
> someone sets up an internal DNS for their own use, they still have to create
> the zones and cnames correctly either way for it to work. And yes I used to
> work for the ANZ, so I know how their naming convention works for their
> internal systems, and my partner works in the deployment of the NAB systems
> and my best mate works for Westpac.
Meaningless name-dropping.
Do they set up a zone for google.com, then add their own entry for
anz.google.com? That was what I initially suggested would be a mistake,
and backed myself apologizing if I'd misunderstood. That is the concept
that you took offence to, that co-opting an external domain was a
mistake.
> And don't talk about the internet at large, my very first post asked the
> question is it for internal purposes before suggesting. So don't attack me
> for something you only half read. And yes you can still call it a DNS,
> because it is still a Domain Name Server, just that it is the Domain
> Controller in a private network, and there are no further controllers to
> connect to.
See above comments. A DNS server is not a Domain Controller.
> And as far as standards go, you're the one who attacked me with standards
> and now you're asking me what has standards got to do with it, I don't know
> you tell me. You seem to be on a mission to bring standards into it, or do
> you not read what you post?
Your first sentence in your prior post was:
What the hell does standards got to do with it if its internal
and not needed to be accessed outside of the company?
My quote that you're talking about was:
So "[w]hat the hell does(sic) standards got(sic) to do with it"?
As you can see, I was poking fun at your grammatical anomalies.
Apparently your reading comprehension leaves something to be desired as
well.
> Now I know you're full of something.
>
> Get a life, you can't win this one, its upto the individual to do what they
> think best suits them or their needs and it that means an Internal DNS
> server like 99.9% of Blue chip companies do then so be it.
An internal DNS server is fine. A caching, forwarding DNS server is
fine. A DNS server which is authoritative for a zone is fine. Taking
control of someone else's domain name is silly, if you plan to also
interact with the internet at large.
> Like I posted I have at home a DNS server that is internal, as stated in my
> first post it is internal and is not viewable by the outside world, and
> before I continued on I stated that if the person didn't want it accessible
> from outside the organisation they could do something like this as it is
> very legal.
>
> www.client1.dev
> www.client2.dev
>
> or
>
> client1.companyname.dev
>
> Internally we at work use the latter as I also stated, but at home on my
> personal network I use the former as I also stated.
>
> Man you are pissing me off, can you tell. And when was the last time you
> read on your MCSE Server Administrations books, people have been using this
> form of systems well before the internet became what is today, sure I could
> hook my DC up to my ISP's for domain propergation and delegation and have it
> server both external addresses and internal addresses but then if you actual
> studied your MCSE books you would know that too.
Hahahahaha, MCSE. You crack me up. That's why you can't seperate a
domain name server from a domain controller. Please do some reading.
Start with the DNS RFCs. Standards, not administration manuals for the
Microsoft tools which implement them, sometimes well, sometimes poorly.
> You call yourself a professional, how can you quote for a job with a client
> if you do not read the specifications to a job fully, and how can you call
> yourself a professional when you have no idea what role a Domain Controller
> can or can not play,
Have you worked out that we're not talking about Domain Controllers yet?
> and how the heel can you call youself a professional when you have no
> idea how a DNS server works, with or without a DC, now lets throw in
> the fact I also have a PDC and a BDC for my network at home as well as
> here, and the PDC has the ability to
I'm glad to note that you haven't called yourself a professional as yet.
You don't appear to be aware that the concept of a Domain Controller is
not central to DNS.
> propergate
The word you're looking for is "propagate". It's probably used a couple
of times in those MCSE manuals which you seem to think define the way
machines on a network should talk to each other.
> external IP addresses to rest of the world while internal IP addresses
> remain within the local network, but then hey if you're a professional
> you would know about routing tables too. But I guess you don't!!!!
Enough exclamation points there?
Would you like to drop some more names, some more concepts that you
barely understand? I can do that too!
RIP, Dijkstra's algorithm, CIDR, DHCP!!!!
See, I win, because I mentioned four extraneous concepts.
Again, for anyone but Andrew who made it this far, I'm sorry. I only
started into this hoping to prevent the OP from making a mistake. I'm
all done.
> Andrew Scott
> Senior Coldfusion Developer
> Aegeon Pty. Ltd.
> www.aegeon.com.au
> Phone: +613 8676 4223
> Mobile: 0404 998 273
Tom
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"cfaussie" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/cfaussie?hl=en
-~----------~----~----~----~------~----~------~--~---
