[TriLUG] OT: DSL for SOHO in Chapel Hill

[Jason Tower]

i never said that i "needed" a /29, just that i had one :-)  actually, 
there are many cases where it comes in handy.  admittedly, there are 
ways around some of these using enough networking-fu but i don't enjoy 
having to reconfigure my setup every time i want to do something 
different:

1. when i was hosting my own web and mail, it allowed me to run the 
public server on its own IP, rather than sticking it behing my nat 
router and messing around with port forwarding.

2. i build, configure, and test linux servers for my clients.  when i 
want to test out a mail server, i can just assign it a public IP and 
plug it in without affecting any other part of my network.

3. i was playing around with vmware last month, trying to set up 
multiple w2k sessions that would each have its own IP in a production 
setting.  with a /29 i just give each VM an IP from my pool and bridge 
them to the physical ethernet interface.  pretty hard to do that with a 
single public IP.  worked like a charm btw :-)

jason

On Tuesday 27 January 2004 10:39, Jim Ray wrote:
> What's the need for a /29 if you outsource dns?
>
> -----Original Message-----
> From: trilug-bounces at trilug.org [mailto:trilug-bounces at trilug.org] On
> Behalf Of Jason Tower
> Sent: Tuesday, January 27, 2004 10:32 AM
> To: Triangle Linux Users Group discussion list
> Subject: Re: [TriLUG] OT: DSL for SOHO in Chapel Hill
>
> > As for DNS, best to leave that to one of the well run third party
> > DNS providers.  Sure, it's something you can do yourself if you
> > want. But why bother when you have free providers like EveryDNS who
> > will do it for you for free?  And you can never hope to reach the
> > levels of redundancy that they can boast of.
>
> easyDNS rocks.  i recommend them to all of my clients, it's so much
> easier than doing it yourself or trusting your ISP or colo (who don't
> always get DNS right).  case in point - i'm working with a client
> right now who changed their MX record in order to start hosting their
> own mail.  however, a percentage of mail continued to be delivered to
> the old server well after the TTL had expired.  turns out the DNS
> provider only updated their primary DNS server, the secondary
> continued to spit out the old info.
>
> jason
>
> --
> TriLUG mailing list        :
> http://www.trilug.org/mailman/listinfo/trilug TriLUG Organizational
> FAQ  : http://trilug.org/faq/
> TriLUG Member Services FAQ : http://members.trilug.org/services_faq/
> TriLUG PGP Keyring         : http://trilug.org/~chrish/trilug.asc