Is it okay to use
app.mycoolname.local
for URLs that are private /
internal?
We have several applications that are
web based, but they are private apps and are not exposed to the
public.
We have been using ".net" for some of
these, which doesn't make sense since they could collied with a real URL on the
internet. That hasn't been a problem yet.
But
now I have a new group of applications and I want to name them using a "popular" name
that will definatly collide with a URL on the
internet.
Should I use
app.mycoolname.local
? I have it set up this way right now, and
it seems to be working. I have read a few places where it was encouraged, but then I saw
a few places where it wasn't working (some problem on Mac, but we don't have those, so
NBD).
Answer
It's perfectly acceptable to use
a .local zone. We have one for our internal network, mainly used for development sites,
but it works well.
Comments
Post a Comment