Date: Fri, 25 Feb 2000 08:32:07 -0800 From: "Kevin Oberman" <oberman@es.net> To: Craig Burgess <craig-burgess@home.net> Cc: Walter Brameld <brameld@twave.net>, "'freebsd'" <freebsd-questions@FreeBSD.ORG> Subject: Re: question/register Message-ID: <200002251632.IAA21503@ptavv.es.net> In-Reply-To: Your message of "Thu, 24 Feb 2000 21:52:17 PST." <38B61891.CDDC136F@home.net>
next in thread | previous in thread | raw e-mail | index | archive | help
More specifically, the @Home AUP prohibits running public servers from a connected system although they do provide 5 MB of space for a web page on their systems. (If you use the 5 MB, you can buy more.) The problem is that cable systems are very asymmetric with lots of download bandwidth and very little in the other direction. To keep people from using the available uplink space they prohibit public servers and limit the uplink bandwidth to 128 Kb. As far as DNS is concerned, if you have a domain and a server anywhere, you can add a name that points to the @Home host. It's just an A record and there is nothing in DNS that limits the addresses pointed to in a zone from being in as many nets as you wish. That is what I do since I can't remember the name @Home gives my system. Works fine. The only limit (which you rarely care about) is that the reverse translation IS controlled by @Home and will always return your @Home name. But you don't see this, so really don't care. Systems that check IP address work by translating the address to a name and then checking that the name returns the same address which works fine. Is everyone really confused about DNS now? R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200002251632.IAA21503>