F-Root Sites
ISC sites are named after the nearest IATA airport code, followed by a number.
If you think your users would benefit from the improved DNS stability that a local F Root Server would bring, but there is no F-Root Server listed for your city or region, let us know. We are in the process of adding more sites.
If you are a researcher and your research involves F.root-servers.net in any way, please contact us at [email protected] and we will be happy to provide you with information on many aspects of F-root, first hand.
| Site Code | Location | IPv4/IPv6 | Node Type |
| AKL1 | Auckland, New Zealand | IPv4 and IPv6 | Local Node |
| AMS1 | Amsterdam, The Netherlands | IPv4 and IPv6 | Global Node |
| ATL1 | Atlanta, GA, USA | IPv4 and IPv6 | Local Node |
| BCN1 | Barcelona, Spain | IPv4 and IPv6 | Local Node |
| BNE1 | Brisbane, Australia | IPv4 and IPv6 | Local Node |
| CAI1 | Cairo, Egypt | IPv4 | Local Node |
| CCS1 | Caracas, Venezuela | IPv4 and IPv6 | Local Node |
| CDG1 | Paris, France | IPv4 and IPv6 | Local Node |
| CGK1 | Jakarta, Indonesia | IPv4 and IPv6 | Local Node |
| DAC1 | Dhaka, Bangladesh | IPv4 and IPv6 | Local Node |
| DAR1 | Dar es Salaam, Tanzania | IPv4 and IPv6 | Local Node |
| DXB1 | Dubai, UAE | IPv4 | Local Node |
| EZE1 | Buenos Aires, Argentina | IPv4 | Local Node |
| FRA1 | Frankfurt, Germany | IPv4 and IPv6 | Local Node |
| GRU1 | São Paulo, Brazil | IPv4 and IPv6 | Local Node |
| HKG1 | Hong Kong, China | IPv4 and IPv6 | Local Node |
| JNB1 | Johannesburg, South Africa | IPv4 and IPv6 | Local Node |
| KBP1 | Kyiv, Ukraine | IPv4 and IPv6 | Local Node |
| KHI1 | Karachi, Pakistan | IPv4 | Local Node |
| KIX1 | Osaka, Japan | IPv4 | Local Node |
| KUL1 | Kuala Lumpur, Malaysia | IPv4 and IPv6 | Local Node |
| LAD1 | Luanda, Angola | IPv4 | Local Node |
| LAX1 | Los Angeles, CA, USA | IPv4 and IPv6 | Local Node |
| LCY1 | London, UK | IPv4 and IPv6 | Local Node |
| LCY2 | London, UK | IPv4 and IPv6 | Local Node |
| LIS1 | Lisbon, Portugal | IPv4 and IPv6 | Local Node |
| LGA1 | New York, NY, USA | IPv4 and IPv6 | Global Node |
| LOS1 | Lagos, Nigeria | IPv4 | Local Node |
| MAA1 | Chennai, India | IPv4 | Local Node |
| MAD1 | Madrid, Spain | IPv4 | Local Node |
| MTY1 | Monterrey, Mexico | IPv4 | Local Node |
| MVD1 | Montevideo, Uruguay | IPv4 and IPv6 | Local Node |
| NBO1 | Nairobi, Kenya | IPv4 | Local Node |
| ORD1 | Chicago, IL, USA | IPv4 and IPv6 | Global Node |
| OSL1 | Oslo, Norway | IPv4 and IPv6 | Local Node |
| PAO1 | Palo Alto, CA, USA | IPv4 and IPv6 | Global Node |
| PAP1 | Port-au-Prince, Haiti | IPv4 | Local Node |
| PEK1 | Beijing, China | IPv4 | Local Node |
| PEK2 | Beijing, China | IPv4 and IPv6 | Local Node |
| PNH1 | Phnom Penh, Cambodia | IPv4 and IPv6 | Local Node |
| PRG1 | Prague, Czech Republic | IPv4 and IPv6 | Local Node |
| ROM1 | Rome, Italy | IPv4 | Local Node |
| SCL1 | Santiago de Chile, Chile | IPv4 and IPv6 | Local Node |
| SEL1 | Seoul, Korea | IPv4 and IPv6 | Local Node |
| SIN1 | Singapore, Singapore | IPv4 and IPv6 | Local Node |
| SJC1 | San Jose, CA, USA | IPv4 | Local Node |
| SJC3 | San Jose, CA, USA | IPv4 and IPv6 | Global Node |
| SJO1 | San Jose, Costa Rica | IPv4 | Local Node |
| SUV1 | Suva, Fiji | IPv4 | Local Node |
| SVO1 | Moscow, Russia | IPv4 and IPv6 | Local Node |
| SXM1 | Philipsburg, Saint Maarten, Netherlands Antilles | IPv4 and IPv6 | Local Node |
| TGD1 | Podgorica, Montenegro | IPv4 | Local Node |
| TLV1 | Tel Aviv, Israel | IPv4 | Local Node |
| TPE1 | Taipei, Taiwan | IPv4 | Local Node |
| TRN1 | Torino, Italy | IPv4 and IPv6 | Local Node |
| UIO1 | Quito, Ecuador | IPv4 and IPv6 | Local Node |
| ULN1 | Ulan Bator, Mongolia | IPv4 | Local Node |
| WAW1 | Warsaw, Poland | IPv4 | Local Node |
| YOW1 | Ottawa, ON, Canada | IPv4 | Local Node |
| YYZ1 | Toronto, ON, Canada | IPv4 and IPv6 | Local Node |
Which F-root node am I using?
To ensure that your users have access to an appropriate local root server it can be useful to find out which instance of the F-Root Nameserver you are currently using. If there is a site listed close to you but you do not appear to be using it, ask your ISP to contact us so we can make the local site available to their customers.
To find out which F-Root site is answering your queries, try one or both of the following:
traceroute F.ROOT-SERVERS.NET
The route your packets take to reach F should give you some information about which site you are using. The site code used to name the ISC routers at the end of the trace can be looked up in this page.
dig +norec @F.ROOT-SERVERS.NET HOSTNAME.BIND CHAOS TXT
This command sends a query to the F root nameserver, asking it to reveal the name of the particular server which answers the query. The hostname will contain a site code, allowing the location of the server to be identified. The dig utility is distributed with ISC BIND 9.
