Keyboard Shortcuts
Thread View
j
: Next unread messagek
: Previous unread messagej a
: Jump to all threadsj l
: Jump to MailingList overview
[apops] Filtering Previously Unallocated Addresses
_______________________________________________________________________
Filtering Previously Unallocated Addresses _______________________________________________________________________
APNIC recognizes that as the IANA pool of unallocated IPv4 addresses nears exhaustion, there may be increasing community concern about the quality of the new address blocks made available for distribution.
It is important that you ensure your router Access Control Lists (ACLs) are updated so addresses are not mistakenly filtered through your routers. It may also be time to consider whether you should stop any form of BOGON filtering.
This is especially important for newly allocated address blocks:
* 1.0.0.0/8 * 14.0.0.0/8 * 27.0.0.0/8 * 36.0.0.0/8 * 42.0.0.0/8 * 49.0.0.0/8 * 101.0.0.0/8 * 223.0.0.0/8
Keep informed about IANA allocations at:
http://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xml
For those with recently allocated address space here are several tips to check whether your IP Addresses are filtered:
* Your own firewall might be blocking the new IP addresses by default, if you set up your servers to block bogon IP ranges. To avoid blocking potential new customers, consider whether you should stop any form of BOGON filtering.
* Run a traceroute to see if the new IP is consistently blocked along the same network path. It is advisable also, to test forward and reverse paths. Use of technology like the Routing Information Service (RIS) is highly recommended to assist in identifying routing conditions for prefixes under test.
http://www.ripe.net/projects/ris/index.html
* Do a search on your IP address and contact those organizations that appear to be blocking you. You may be blocked due to activity of one of your customers.
http://whatismyipaddress.com/blacklist-check
* Use a looking glass service as part of the diagnostic tool, set to detect network filters.
http://www.ris.ripe.net/cgi-bin/lg/index.cgi
Ongoing testing ---------------
As part of our service commitment to our Members and the wider community, APNIC is working hard to evaluate the usability of address space allocated to APNIC before it is distributed.
For further information on Resource Quality Assurance and the testing results, visit:
For further assistance, contact:
helpdesk@apnic.net
Regards Sunny
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
FYI, there was a thread on janog that claimed there are many named.conf out there that deny queries from these newly allocated space.
That's hard to notice.
Regards, Seiichi
Srinivas Chendi wrote:
Filtering Previously Unallocated Addresses _______________________________________________________________________
APNIC recognizes that as the IANA pool of unallocated IPv4 addresses nears exhaustion, there may be increasing community concern about the quality of the new address blocks made available for distribution.
It is important that you ensure your router Access Control Lists (ACLs) are updated so addresses are not mistakenly filtered through your routers. It may also be time to consider whether you should stop any form of BOGON filtering.
This is especially important for newly allocated address blocks:
* 1.0.0.0/8 * 14.0.0.0/8 * 27.0.0.0/8 * 36.0.0.0/8 * 42.0.0.0/8 * 49.0.0.0/8 * 101.0.0.0/8 * 223.0.0.0/8
Keep informed about IANA allocations at:
http://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xml
For those with recently allocated address space here are several tips to check whether your IP Addresses are filtered:
* Your own firewall might be blocking the new IP addresses by default, if you set up your servers to block bogon IP ranges. To avoid blocking potential new customers, consider whether you should stop any form of BOGON filtering. * Run a traceroute to see if the new IP is consistently blocked along the same network path. It is advisable also, to test forward and reverse paths. Use of technology like the Routing Information Service (RIS) is highly recommended to assist in identifying routing conditions for prefixes under test. http://www.ripe.net/projects/ris/index.html * Do a search on your IP address and contact those organizations that appear to be blocking you. You may be blocked due to activity of one of your customers. http://whatismyipaddress.com/blacklist-check * Use a looking glass service as part of the diagnostic tool, set to detect network filters. http://www.ris.ripe.net/cgi-bin/lg/index.cgi
Ongoing testing
As part of our service commitment to our Members and the wider community, APNIC is working hard to evaluate the usability of address space allocated to APNIC before it is distributed.
For further information on Resource Quality Assurance and the testing results, visit:
http://www.apnic.net/rqa
For further assistance, contact:
helpdesk@apnic.net
Regards Sunny
Hello, folks,
Today, JPRS announced to Japanese Internet community for fixing the Bogon issue on authoritative DNS servers.
(in Japanese) Inappropriate Bogon filters on authoritative DNS server considered harmful http://jprs.jp/tech/notice/2010-11-02-authdns-bogon-filter.html
Regards, -- Yasuhiro 'Orange' Morishita
-- Yasuhiro 'Orange' Morishita yasuhiro@jprs.co.jp Technical Specialist, Internet Engineering and Operations Japan Registry Services Co., Ltd. (JPRS) URI: http://jprs.co.jp/en/ | http://www.dns.jp/
From: Seiichi Kawamura kawamucho@mesh.ad.jp Date: Tue, 02 Nov 2010 12:00:27 +0900
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
FYI, there was a thread on janog that claimed there are many named.conf out there that deny queries from these newly allocated space.
That's hard to notice.
Regards, Seiichi
Srinivas Chendi wrote:
Filtering Previously Unallocated Addresses _______________________________________________________________________
APNIC recognizes that as the IANA pool of unallocated IPv4 addresses nears exhaustion, there may be increasing community concern about the quality of the new address blocks made available for distribution.
It is important that you ensure your router Access Control Lists (ACLs) are updated so addresses are not mistakenly filtered through your routers. It may also be time to consider whether you should stop any form of BOGON filtering.
This is especially important for newly allocated address blocks:
* 1.0.0.0/8 * 14.0.0.0/8 * 27.0.0.0/8 * 36.0.0.0/8 * 42.0.0.0/8 * 49.0.0.0/8 * 101.0.0.0/8 * 223.0.0.0/8
Keep informed about IANA allocations at:
http://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xml
For those with recently allocated address space here are several tips to check whether your IP Addresses are filtered:
* Your own firewall might be blocking the new IP addresses by default, if you set up your servers to block bogon IP ranges. To avoid blocking potential new customers, consider whether you should stop any form of BOGON filtering. * Run a traceroute to see if the new IP is consistently blocked along the same network path. It is advisable also, to test forward and reverse paths. Use of technology like the Routing Information Service (RIS) is highly recommended to assist in identifying routing conditions for prefixes under test. http://www.ripe.net/projects/ris/index.html * Do a search on your IP address and contact those organizations that appear to be blocking you. You may be blocked due to activity of one of your customers. http://whatismyipaddress.com/blacklist-check * Use a looking glass service as part of the diagnostic tool, set to detect network filters. http://www.ris.ripe.net/cgi-bin/lg/index.cgi
Ongoing testing
As part of our service commitment to our Members and the wider community, APNIC is working hard to evaluate the usability of address space allocated to APNIC before it is distributed.
For further information on Resource Quality Assurance and the testing results, visit:
http://www.apnic.net/rqa
For further assistance, contact:
helpdesk@apnic.net
Regards Sunny
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32)
iEYEARECAAYFAkzPfsoACgkQcrhTYfxyMkIX8gCfWaqKuuEWx4cdv1kwm/wdspym AiEAn19bJLTYttxtVFGrugMxdXJtrcop =J7S0 -----END PGP SIGNATURE----- _______________________________________________ apops mailing list apops@apops.net http://mailman.apnic.net/mailman/listinfo/apops Website: www.apops.net
Activity Summary
- 5182 days inactive
- 5182 days old
- apops@apops.net
- 3 participants
- 2 comments