Naming my home lan domain

Is it acceptable/advisable to name my rfc1918 lan with the domain name
I have registered at DynDNS.org?

I'll use "example" instead of my real domain name, since we all have
to pretend some level of anonymity.

For years now, I've had my own lan with DNS, etc. To date it has been
called "example.invalid" because it's rfc1918, etc. Last Spring I
purchased "example.net" from DynDNS.org, so I own a real domain name,
even if it does point to a dhcp cable modem address. I also have mail
forwarding, so I can keep a stable address if/when I change ISP, etc.

I'm about to set up Kerberos and LDAP, and that's going to make my
domain name become *really* sticky. I could change it now, in about
an hour. After Kerberos/LDAP, it would require tear-down/rebuild.

So at this point, I'm tempted to rename my lan to "example.net" so
my lan looks like a natural extension of the Internet. My external
email addresses don't match account names - I rewrite them, so that
would still be necessary, but only for the name, not the domain.

Are there compelling reasons to/not-to do this?

Thanks,
Dale Pontius

(E-Mail Removed) wrote:
> Is it acceptable/advisable to name my rfc1918 lan with the domain name
> I have registered at DynDNS.org?

If you have a domain name available for your home network I would always
recommend using it. Your internal DNS does not (and often should not)
match what you tell the rest of the world.

In my case, you really don't need to know about avon.roaima.co.uk,
aire.roaima.co.uk, humber.roaima.co.uk, etc. All you need to know is how
to email me (and, should I provide one, how to get to my website). You
don't need to know my actual internal username either, as long as the
email gets through.

Because my internal DNS is split from my external DNS, I can have
all these names in my internal DNS, yet you can't see them from "the
outside". More usefully still, my external MX for roaima.co.uk is
different to the internal one (external MX points to my ADSL router;
internal MX points to the mail server).

> Last Spring I
> purchased "example.net" from DynDNS.org, so I own a real domain name,
> even if it does point to a dhcp cable modem address. I also have mail
> forwarding, so I can keep a stable address if/when I change ISP, etc.

Good stuff.

> So at this point, I'm tempted to rename my lan to "example.net" so
> my lan looks like a natural extension of the Internet.

Yes. Do it. Don't be shy.

> My external
> email addresses don't match account names - I rewrite them, so that
> would still be necessary, but only for the name, not the domain.

Great.

> Are there compelling reasons to/not-to do this?

Yes. It makes (semantic) sense to do so.
Chris

chris-(E-Mail Removed) wrote:
> (E-Mail Removed) wrote:
>
>>Is it acceptable/advisable to name my rfc1918 lan with the domain name
>>I have registered at DynDNS.org?
>
>
> If you have a domain name available for your home network I would always
> recommend using it. Your internal DNS does not (and often should not)
> match what you tell the rest of the world.
>
> In my case, you really don't need to know about avon.roaima.co.uk,
> aire.roaima.co.uk, humber.roaima.co.uk, etc. All you need to know is how
> to email me (and, should I provide one, how to get to my website). You
> don't need to know my actual internal username either, as long as the
> email gets through.
>
> Because my internal DNS is split from my external DNS, I can have
> all these names in my internal DNS, yet you can't see them from "the
> outside". More usefully still, my external MX for roaima.co.uk is
> different to the internal one (external MX points to my ADSL router;
> internal MX points to the mail server).
>
>
>>Last Spring I
>>purchased "example.net" from DynDNS.org, so I own a real domain name,
>>even if it does point to a dhcp cable modem address. I also have mail
>>forwarding, so I can keep a stable address if/when I change ISP, etc.
>
>
> Good stuff.
>
>
>>So at this point, I'm tempted to rename my lan to "example.net" so
>>my lan looks like a natural extension of the Internet.
>
>
> Yes. Do it. Don't be shy.
>
>
>>My external
>>email addresses don't match account names - I rewrite them, so that
>>would still be necessary, but only for the name, not the domain.
>
>
> Great.
>
>
>>Are there compelling reasons to/not-to do this?
>
>
> Yes. It makes (semantic) sense to do so.
> Chris

How will this affect people who attempt to email him or use a web page
of his? If his IP is changing, won't all the DNS servers have trouble
keeping up and every so often people wont be able to get to his servers?


CL

--
Respectfully,


CL Gilbert

"Verily, verily, I say unto you, He that entereth not by the door() into
the sheepfold{}, but climbeth up some other *way, the same is a thief
and a robber." John 10:1

GnuPG Key Fingerprint:
82A6 8893 C2A1 F64E A9AD 19AE 55B2 4CD7 80D2 0A2D

For a free Java interface to Freechess.org see
http://www.rigidsoftware.com/Chess/chess.html

"CL (dnoyeB) Gilbert" <(E-Mail Removed)> wrote:
> How will this affect people who attempt to email him or use a web page
> of his?

You quoted the whole of my reply, so I'm not sure which bit you're
questioning..?

> If his IP is changing, won't all the DNS servers have trouble
> keeping up and every so often people wont be able to get to his servers?

DynDNS. But I wouldn't expect it to change too often anyway.

Chris

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 2004-11-04, chris-(E-Mail Removed) <chris-(E-Mail Removed)> wrote:
>
> If you have a domain name available for your home network I would always
> recommend using it. Your internal DNS does not (and often should not)
> match what you tell the rest of the world.

That's absolutely true, which is why I use a 10-character domain
internally instead of my 26-character registered domain.

- --keith

- --
kkeller-(E-Mail Removed)
(try just my userid to email me)
AOLSFAQ=http://wombat.san-francisco.ca.us/cgi-bin/fom

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFBipWhhVcNCxZ5ID8RAg6TAJ9E0g56JLbsn8OJss/Ft+xy77B2DQCbB1/T
aVpZl1+2ydfv0QcAMrXZovQ=
=v9qI
-----END PGP SIGNATURE-----

On 2004-11-04, chris-(E-Mail Removed) <chris-(E-Mail Removed)> wrote:
> If you have a domain name available for your home network I would always
> recommend using it. Your internal DNS does not (and often should not)
> match what you tell the rest of the world.

Keith Keller <kkeller-(E-Mail Removed)> wrote:
> That's absolutely true, which is why I use a 10-character domain
> internally instead of my 26-character registered domain.

Now you're confusing /me/! You appear to be agreeing with my sentiment
and at the same time providing an opposite to my reasoning!

Heaven help the OP :-)

If I were you, (given your posting address wombat.*.us), I'd probably be
running machines like foo.wombat.*.us and bar.wombat.*.us on my internal
network. These would be available in my internal DNS but certainly not
visible externally.

Chris

In article <0eCdnU-PCulbuRfcRVn-(E-Mail Removed)>,
"CL (dnoyeB) Gilbert" <(E-Mail Removed)> writes:
> chris-(E-Mail Removed) wrote:
>> (E-Mail Removed) wrote:
>>
>>>Is it acceptable/advisable to name my rfc1918 lan with the domain name
>>>I have registered at DynDNS.org?
>>
>>
>> If you have a domain name available for your home network I would always
>> recommend using it. Your internal DNS does not (and often should not)
>> match what you tell the rest of the world.
>>
<snip>
>> Yes. Do it. Don't be shy.
<snip>
>>
>>>My external
>>>email addresses don't match account names - I rewrite them, so that
>>>would still be necessary, but only for the name, not the domain.
>>
>>
>> Great.
>>
>>
>>>Are there compelling reasons to/not-to do this?
>>
>>
>> Yes. It makes (semantic) sense to do so.
>> Chris
>
> How will this affect people who attempt to email him or use a web page
> of his? If his IP is changing, won't all the DNS servers have trouble
> keeping up and every so often people wont be able to get to his servers?
>
I have my domain registered with DynDNS.org, and though my DHCP address
is pretty stable, I keep it properly updated with them. Though in
reality the only thing my domain does is forward my family's mail. We
have a cable ISP, and they have a "no servers at all" policy. In the
past I have opened heavily filtered ports to allow me to access my home
systems from work or relatives' homes, and I may do so again in the
future. I may also have my incoming mail relay through DynDNS instead
of my ISP's POP box.

But I never anticipate giving open access for anything to my domain.

Dale Pontius

In article <(E-Mail Removed)>,
Keith Keller <kkeller-(E-Mail Removed)> writes:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 2004-11-04, chris-(E-Mail Removed) <chris-(E-Mail Removed)> wrote:
>>
>> If you have a domain name available for your home network I would always
>> recommend using it. Your internal DNS does not (and often should not)
>> match what you tell the rest of the world.
>
> That's absolutely true, which is why I use a 10-character domain
> internally instead of my 26-character registered domain.
>
My external domain is shorter than my internal one. (*.net vs *.invalid)
Using the external name makes things nicer for me.

Dale Pontius