| | At Large Membership and Civil Society Participation in ICANN |
|
| |
|
|
|
|
This discussion has been archived.
No new comments can be posted.
|
|
Anonymous ICANNwatch Messages Considered Harmful?
|
Log in/Create an Account
| Top
| 65 comments
|
Search Discussion
|
|
|
|
The Fine Print:
The following comments are owned by whoever posted them.
We are not responsible for them in any way.
|
|
 |
Given (for example) 192.5.5.241 coming from
the external view of where dot (.) is located.
The file /etc/dhcpd.conf becomes:
ddns-update-style ad-hoc;
subnet 192.5.5.0 netmask 255.255.255.0 {
range 192.5.5.1 192.5.5.240;
option domain-name-servers 192.5.5.241;
option routers 192.5.5.241;
}
This will then hand out DHCP addresses in
the range 192.5.5.1 to 192.5.5.240 which will
support most of your PCs and servers at your
site, assuming you have less than a few hundred.
in /etc/rc.local add
ifconfig eth1:0 192.5.5.241
New.Net has instructions on how to set up your
named files to pull in all of the pointers to
the TLD servers to your local domain name server.
You should of course have your Private Address
Bit (PAB) set in your packets.
See also IAHC PAB POC COM and NET on Google
|
|
|
|
[ Reply to This | Parent
]
|
|
|
Privacy Policy: We will not knowingly give out your personal data -- other than identifying your postings in the way you direct by setting your configuration options -- without a court order. All logos and trademarks in this site are property of their
respective owner. The comments are property of their posters, all the rest © 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008 by ICANNWatch.Org. This web site was made with Slashcode, a web portal system written in perl. Slashcode is Free Software released under the GNU/GPL license.
You can syndicate our headlines in .rdf, .rss, or .xml. Domain registration services donated by DomainRegistry.com
|
