Simon, We can't be sure what exactly is missing from the DNS in your case, but here are the specific requirements for the DNS for a .FR name
Zone configuration: 1. the zone is installed in all the name servers (at least two) given in the installation request ticket sent to the [EMAIL PROTECTED] address, 2. the primary server name in the SOA record corresponds to the first server given in the list of servers to install, 3. the zone contact (RNAME) is valid and must be contactable by e-mail, 4. the zone serial number is the same on each server, 5. the "refresh" time is at least one hour, 6. the "retry" time is at least one hour, 7. the "expire" time is at least a week, and much higher than the "refresh" time, 8. the "TTL" time in the SOA specifies the TTL for negative responses (NXDOMAIN) and must not exceed one day, 9. the "TTL" time is at least one hour for SOA and NS records, 10. the list of zone name servers returned by the server corresponds to the list of servers requested in the ticket, 11. there is one MX for the zone, using a message service relay with a legal name that must be (or must point to) an Internet address (A record); any alias (CNAME) will be refused in accordance with the RFCs, 12. the [EMAIL PROTECTED] or [EMAIL PROTECTED] mailbox must be contactable, 13. the contents of the zone conform to the RFCs. Configuration of name servers: 1. the server must have international IP connectivity, 2. the server must be online 24 hours a day, 7 days a week, 3. the DNS service must be accessible on port 53 in UDP and TCP, and to ICMP echo packets, for packets sent from any machine on the Internet, 4. the server must have authority for the requested zone, 5. the server must obtain the correct list of name servers corresponding to each of the ".fr / .re", ".in-addr.arpa" and "." zones, and must not have authority unless it is mentioned in this list. The addresses of the servers mentioned must be correct, 6. the server obtains the correct address for each of the other servers in the zone, 7. the server calculates checksums for UDP packets and generates its IP packets with a TTL of at least 64, 8. the server does not forward requests to AFNIC servers, 9. it must be possible to obtain the server names based on their IP addresses. Messaging: 1. the VRFY command is implemented in accordance with RFC1123, 2. the return code must be of type "2xx" in accordance with RFC1893, 3. the [EMAIL PROTECTED] or [EMAIL PROTECTED] address can be delivered to on the first message service relay, 4. it must be possible to deliver to the zone contact address specified in the SOA record on the first message service relay. Network database (RIPE - RADB) : For each server mentioned: 1. there is an "inetnum" record for the network to which it belongs, 2. there is a "route" record for the network to which it belongs, For each zone registration request: 1. the first technical contact is located at the requesting registrar, 2. the identifier of the first technical contact is a NIC-HDL of a role object in the FRNIC database. For more information on NIC-HDLs and role objects, please consult this document and course material. Greg Frank Product Manager, TLDs Tucows -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of xperience Sent: Saturday, April 15, 2006 4:40 PM To: [email protected] Subject: [domains-gen] .fr DNS Requirements Hi, We're having problems registering .fr domains - we're getting an error: f: No SOA record found on server Anyone know what we might be missing? Simon _______________________________________________ domains-gen mailing list [email protected] http://discuss.tucows.com/mailman/listinfo/domains-gen _______________________________________________ domains-gen mailing list [email protected] http://discuss.tucows.com/mailman/listinfo/domains-gen
