On 2013-05-10 16:39, b...@bitrate.net wrote:
On May 10, 2013, at 01.18, Dave Warren wrote:
On 2013-05-08 11:13, btb wrote:
it's also mildly humorous that they used to quite religiously endorse .local, in some
documents even categorizing use of the same domain name on an internal and external
On May 10, 2013, at 01.18, Dave Warren wrote:
> On 2013-05-08 11:13, btb wrote:
>> it's also mildly humorous that they used to quite religiously endorse
>> .local, in some documents even categorizing use of the same domain name on
>> an internal and external network as a "security risk".
>
>
On 2013-05-08 11:13, btb wrote:
it's also mildly humorous that they used to quite religiously endorse
.local, in some documents even categorizing use of the same domain
name on an internal and external network as a "security risk".
Keep in mind that this was before ubiquitous, always-on TCP/I
On 2013-05-09 11:27, Jeremy P wrote:
I certainly didn't intend to spark off such a firestorm with my
original question. I have learned a lot from the debate though.
On the question of what to use with students, it is a fine thing to
say "we should only do things the way they are done in real
Too often its the corner office friend!
You are right, those other people may get hired, but not by people who know
how to interview. I ran an IT department for 10 years prior to teaching
and my goals of hiring were always first, don't hire jerks. Second, hire
people who know their stuff inside
> From: Jeremy P
> In my experience the students who "get it" and comprehend the
> concepts are able to heed the warnings of "in real life, we would do
> this a little different". The students who don't "get it" are gonna
> misconfigure regardless of what TLD I tell them to use in the lab.
>
I certainly didn't intend to spark off such a firestorm with my original
question. I have learned a lot from the debate though.
On the question of what to use with students, it is a fine thing to say "we
should only do things the way they are done in real life so students don't
learn bad habits",
Matus UHLAR - fantomas wrote:
> > > On 09.05.13 10:21, Tony Finch wrote:
> > > > Right. Give each student a subdomain of some existing domain, even
> > > > if the subdomains aren't publicly delegated.
>
> > Matus UHLAR - fantomas wrote:
> > > yes, so they will start using it in their job and hom
On 09.05.13 10:21, Tony Finch wrote:
> Right. Give each student a subdomain of some existing domain, even if the
> subdomains aren't publicly delegated.
Matus UHLAR - fantomas wrote:
yes, so they will start using it in their job and home.
On 09.05.13 16:01, Tony Finch wrote:
They shouldn't
-Original Message-
From: Tony Finch
Date: Thursday, May 9, 2013 11:01 AM
To: Matus UHLAR - fantomas
Cc: "bind-users@lists.isc.org"
Subject: Re: architecture question
>Matus UHLAR - fantomas wrote:
>> On 09.05.13 10:21, Tony Finch wrote:
>> > Right. Give
Matus UHLAR - fantomas wrote:
> On 09.05.13 10:21, Tony Finch wrote:
> > Right. Give each student a subdomain of some existing domain, even if the
> > subdomains aren't publicly delegated.
>
> yes, so they will start using it in their job and home.
They shouldn't do that if the teacher has proper
On 5/8/13 9:33 AM, Jeremy P wrote:
> However, there are times where registering a real domain just isn't
> practical. For example, I'm not going to ask all of the students in my
> courses to go out and register a .com for the semester.
Michael McNally wrote:
The flip side of this is that wha
Michael McNally wrote:
> On 5/8/13 9:33 AM, Jeremy P wrote:
> >
> > However, there are times where registering a real domain just isn't
> > practical. For example, I'm not going to ask all of the students in my
> > courses to go out and register a .com for the semester.
>
> The flip side of this
On 2013-05-08 20:58, Michael McNally wrote:
The flip side of this is that whatever you teach them they are going
to take out into the wider world with them. If you teach them to use
.local or .lan, some of them (at least) are going to continue using
.local or .lan long after your class is over,
On 5/8/13 9:33 AM, Jeremy P wrote:
However, there are times where registering a real domain just isn't
practical. For example, I'm not going to ask all of the students in my
courses to go out and register a .com for the semester. It would be a
waste of money as their systems never leave the loc
Though there are plenty of students who are capable of getting their own
domains, and some temporary web presence.which popup for SGA
electionsand probably are only needed for a couple of weeks.
Plus after the class, what would stop them from using the domain for something
else
OTO
On 2013-05-08 13:50, Mike Hoskins (michoski) wrote:
The spirit of education is often saving money based on a former life as a
lab tech. While cheap, the proposal to "just go register a real one!"
seems good for $registrar, but potentially bad for the Internet (will we
end up with a bunch of garb
-Original Message-
From: Jonathan Reed
Date: Wednesday, May 8, 2013 4:38 PM
To: Jeremy P
Cc: bind-users
Subject: Re: architecture question
>It would be a waste of money as their systems never leave the local
>network, except through a NAT connection.
>
>Godaddy is selli
>
> It would be a waste of money as their systems never leave the local
> network, except through a NAT connection.
Godaddy is selling .coms for $0.99 right now (US/Canada). In the spirit of
an educational setting, it might be a viable exercise for students to
understand how easy and affordable i
Years ago we decided to create a private TLD of .campus
What we did was make all our caching nameservers also be authoritative for this
private TLD. And, this worksexcept for delegated subdomains, which are
handled through using forwarding zones.
later when the needed to be able to get re
Jeremy P wrote:
>
> I will switch to something more "out there" in the future. I take it that
> .lan is safe?
Don't use .lan either - it is very popular with malware and is likely to
get you blacklisted. Use a real domain.
Tony.
--
f.anthony.n.finchhttp://dotat.at/
Forties, Cromarty: East,
On 2013.05.08 13.33, Jeremy P wrote:
I understand letter of the law, spirit of the law and playing it safe to
avoid headaches.
However, there are times where registering a real domain just isn't
practical. For example, I'm not going to ask all of the students in my
courses to go out and registe
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I personally use localdomain. I'm not sure how safe it is, but I use
it at home so it probably doesn't matter.
On 05/08/2013 01:47 PM, Steven Carr wrote:
> You could ask your institution for a subdomain to be reserved from
> their domain?
>
> .lan is
On 2013.05.08 13.20, Steven Carr wrote:
On 8 May 2013 18:09, wrote:
This just came up with a site I support. Thanks to this list and the
DNS-OARC list, I know better. Hopefully, I can redirect them to use
something below their real domain for Active Directory such as
ad.example.org.
FWIW: M
You could also make a sub domain of your main domain and use that for
all students, unless of course the purpose is to teach how to set this up.
I have used .home my self, now I would take something that
nobody would ever think of using in the "real" world, in old days I did
consider .xxx, that is
-Original Message-
From: Jeremy P
Date: Wednesday, May 8, 2013 1:33 PM
To: Steven Carr
Cc: bind-users
Subject: Re: architecture question
>I understand letter of the law, spirit of the law and playing it safe to
>avoid headaches.
>
>However, there are times where regist
You could ask your institution for a subdomain to be reserved from their domain?
.lan isn't AFAIK reserved for anything or in the process of being
considered by ICANN.
.test is reserved and will never be advertised on the internet (as are
.example, .invalid and .localhost)
On 8 May 2013 18:33, J
I understand letter of the law, spirit of the law and playing it safe to
avoid headaches.
However, there are times where registering a real domain just isn't
practical. For example, I'm not going to ask all of the students in my
courses to go out and register a .com for the semester. It would be
On 8 May 2013 18:09, wrote:
> This just came up with a site I support. Thanks to this list and the
> DNS-OARC list, I know better. Hopefully, I can redirect them to use
> something below their real domain for Active Directory such as
> ad.example.org.
FWIW: MS now advises not to use .local for
> From: b...@bitrate.net
> on a side note, i would strongly discourage you from using .local in
> dns. .local is a "pseudo" tld, reserved for use with mdns.
This just came up with a site I support. Thanks to this list and the
DNS-OARC list, I know better. Hopefully, I can redirect them to use
Understood. This is an isolated lab full of openBSD boxes, so I'm not too
worried about it. The lab will be torn down in a month or two.
I will switch to something more "out there" in the future. I take it that
.lan is safe?
On Wed, May 8, 2013 at 11:03 AM, wrote:
>
> On May 8, 2013, at 10.
On May 8, 2013, at 10.56, Jeremy P wrote:
> I am building a lab environment where there are several separate domains, all
> of them ending in .local
on a side note, i would strongly discourage you from using .local in dns.
.local is a "pseudo" tld, reserved for use with mdns.
-ben
_
Don't forget that Bonjour actually uses .local and will be very sour if
it is sued for other purposes, I have tried.
On 08/05/13 16:56, Jeremy P wrote:
> I am building a lab environment where there are several separate
> domains, all of them ending in .local
>
> I've setup a server for the .loc
Enable recursion on your .local TLD server and point the domain1.local
server to that server for DNS. Recursion will handle any internet
queries and as .local is authoritative it will provide responses when
queried.
On 8 May 2013 15:56, Jeremy P wrote:
> I am building a lab environment where ther
I am building a lab environment where there are several separate domains,
all of them ending in .local
I've setup a server for the .local TLD, but I'm undecided (or perhaps
ignorant) as to the best way to have the individual domains (domain1.local,
domain2.local, etc) refer to the local zone on my
35 matches
Mail list logo
