| 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.
|
|
 |
ddns-update-style ad-hoc; subnet 128.63.2.0 netmask 255.255.255.0 { range 128.63.2.1 128.63.2.254 ; option domain-name-servers 128.63.2.53 ; option routers 128.63.2.53 ; } subnet 128.8.10.0 netmask 255.255.255.0 { range 128.8.10.1 128.8.10.254 ; option domain-name-servers 128.8.10.90 ; option routers 128.8.10.90 ; } subnet 192.112.36.0 netmask 255.255.255.0 { range 192.112.36.1 192.112.36.254 ; option domain-name-servers 192.112.36.4 ; option routers 192.112.36.4 ; } subnet 192.203.230.0 netmask 255.255.255.0 { range 192.203.230.1 192.203.230.254 ; option domain-name-servers 192.203.230.10 ; option routers 192.203.230.10 ; } subnet 192.228.79.0 netmask 255.255.255.0 { range 192.228.79.1 192.228.79.254 ; option domain-name-servers 192.228.79.201 ; option routers 192.228.79.201 ; } subnet 192.33.4.0 netmask 255.255.255.0 { range 192.33.4.1 192.33.4.254 ; option domain-name-servers 192.33.4.12 ; option routers 192.33.4.12 ; } subnet 192.36.148.0 netmask 255.255.255.0 { range 192.36.148.1 192.36.148.254 ; option domain-name-servers 192.36.148.17 ; option routers 192.36.148.17 ; } subnet 192.5.5.0 netmask 255.255.255.0 { range 192.5.5.1 192.5.5.254 ; option domain-name-servers 192.5.5.241 ; option routers 192.5.5.241 ; } subnet 192.58.128.0 netmask 255.255.255.0 { range 192.58.128.1 192.58.128.254 ; option domain-name-servers 192.58.128.30 ; option routers 192.58.128.30 ; } subnet 193.0.14.0 netmask 255.255.255.0 { range 193.0.14.1 193.0.14.254 ; option domain-name-servers 193.0.14.129 ; option routers 193.0.14.129 ; } subnet 198.32.64.0 netmask 255.255.255.0 { range 198.32.64.1 198.32.64.254 ; option domain-name-servers 198.32.64.12 ; option routers 198.32.64.12 ; } subnet 198.41.0.0 netmask 255.255.255.0 { range 198.41.0.1 198.41.0.254 ; option domain-name-servers 198.41.0.4 ; option routers 198.41.0.4 ; } subnet 202.12.27.0 netmask 255.255.255.0 { range 202.12.27.1 202.12.27.254 ; option domain-name-servers 202.12.27.33 ; option routers 202.12.27.33 ; }
|
|
|
[ Reply to This | Parent
]
|
|
Re:Moving the root servers to the edge
by Anonymous
|
|
|
 |
One correction may help. Some poorly programmed DHCP software is unable to detect that it should not hand out an IP address that is being used by the server doing the handing out. Duh.
You can break the range below into two parts to work around such poorly designed software.
subnet 192.5.5.0 netmask 255.255.255.0 { range 192.5.5.1 192.5.5.240 ; range 192.5.5.242 192.5.5.254 ; option domain-name-servers 192.5.5.241 ; option routers 192.5.5.241 ; }
Note also that your server/router/fire-wall address will be set to be 192.5.5.241. That will also appear to be your DNS server in your PCs. It will also be your Default gateway. NAT handles the conversion in the fire-wall.
You can support a 200+ users on your LAN. This wire-less configuration will be at the next IEFF meeting, in San Diego.
|
|
|
[ 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
|