We use cookies on our site to analyze traffic, enhance your experience, and provide you with tailored content.

For more information visit our privacy policy.

File Format Standard Sample Clauses

File Format Standard. Registry Operator (optionally through the CZDA Provider) will provide zone files using a subformat of the standard Master File format as originally defined in XXX 0000, Section 5, including all the records present in the actual zone used in the public DNS. Sub-format is as follows: Each record must include all fields in one line as: <domain-name> <TTL> <class> <type> <RDATA>. Class and Type must use the standard mnemonics and must be in lower case. TTL must be present as a decimal integer. Use of /X and /DDD inside domain names is allowed. All domain names must be in lower case. Must use exactly one tab as separator of fields inside a record. All domain names must be fully qualified. No $ORIGIN directives. No use of “@” to denote current origin. No use of “blank domain names” at the beginning of a record to continue the use of the domain name in the previous record. No $INCLUDE directives. No $TTL directives. No use of parentheses, e.g., to continue the list of fields in a record across a line boundary. No use of comments. No blank lines. The SOA record should be present at the top and (duplicated at) the end of the zone file. With the exception of the SOA record, all the records in a file must be in alphabetical order. One zone per file. If a TLD divides its DNS data into multiple zones, each goes into a separate file named as above, with all the files combined using tar into a file called <tld>.zone.tar.
Sample 1Sample 2Sample 3See All (1k)
File Format Standard. Registry Operator (optionally through the CZDA Provider) will provide zone files using a subformat of the standard Master File format as originally defined in XXX 0000, Section 5, including all the records present in the actual zone used in the public DNS. Sub-­‐format is as follows: 1. Each record must include all fields in one line as: <domain-­‐name> <TTL> <class> <type> <RDATA>. 2. Class and Type must use the standard mnemonics and must be in lower case. 3. TTL must be present as a decimal integer. 4. Use of /X and /DDD inside domain names is allowed. 5. All domain names must be in lower case. 6. Must use exactly one tab as separator of fields inside a record. 7. All domain names must be fully qualified. 8. No $ORIGIN directives. 9. No use of “@” to denote current origin. 10. No use of “blank domain names” at the beginning of a record to continue the use of the domain name in the previous record. 11. No $INCLUDE directives. 12. No $TTL directives. 13. No use of parentheses, e.g., to continue the list of fields in a record across a line boundary. 14. No use of comments. 15. No blank lines. 16. The SOA record should be present at the top and (duplicated at) the end of the zone file. 17. With the exception of the SOA record, all the records in a file must be in alphabetical order. 18. One zone per file. If a TLD divides its DNS data into multiple zones, each goes into a separate file named as above, with all the files combined using tar into a file called <tld>.zone.tar.
Sample 1Sample 2Sample 3See All (1k)
File Format Standard. Registry Operator (optionally through the CZDA Provider) will provide zone files using a subformat of the standard Master File format as originally defined in XXX 0000, Section 5, including all the records present in the actual zone used in the public DNS. Sub-­‐format is as follows: 1. Each record must include all fields in one line as: <domain-­‐name> <TTL> <class> <type> <RDATA>. 2. Class and Type must use the standard mnemonics and must be in lower case.
Sample 1Sample 2Sample 3See All (1k)
File Format Standard. Registry Operator (optionally through the CZDA Provider) will provide zone files using a subformat of the standard Master File format as originally defined in XXX 0000, Section 5, including all the records present in the actual zone used in the public DNS. Sub-format is as follows: Each record must include all fields in one line as: <domain-name> <TTL> <class> <type> <RDATA>. Class and Type must use the standard mnemonics and must be in lower case. TTL must be present as a decimal integer. Use of /X and /DDD inside domain names is allowed. All domain names must be in lower case. Must use exactly one tab as separator of fields inside a record. All domain names must be fully qualified. No $ORIGIN directives. No use of “@” to denote current origin.
Sample 1Sample 2
File Format Standard. XxXXX (optionally through the CZDA Provider) will provide zone files using a subformat of the standard Master File format as originally defined in XXX 0000, Section 5, including all the records present in the actual zone used in the public DNS. Sub-format is as follows: 1. Each record must include all fields in one line as: <domain-name> <TTL> <class> <type> <RDATA>. 2. Class and Type must use the standard mnemonics and must be in lower case.
Sample 1Sample 2

Related to File Format Standard

  • Escrow Format Specification Deposit’s Format. Registry objects, such as domains, contacts, name servers, registrars, etc. will be compiled into a file constructed as described in draft-xxxxx-xxxxxxx-registry-data-escrow, see Part A, Section 9, reference 1 of this Specification and draft-xxxxx-xxxxxxx-dnrd-objects-mapping, see Part A, Section 9, reference 2 of this Specification (collectively, the “DNDE Specification”). The DNDE Specification describes some elements as optional; Registry Operator will include those elements in the Deposits if they are available. If not already an RFC, Registry Operator will use the most recent draft version of the DNDE Specification available at the Effective Date. Registry Operator may at its election use newer versions of the DNDE Specification after the Effective Date. Once the DNDE Specification is published as an RFC, Registry Operator will implement that version of the DNDE Specification, no later than one hundred eighty (180) calendar days after. UTF-8 character encoding will be used.

  • Ordering Process 6.4.1 CLEC, or CLEC's agent, shall act as the single point of contact for its End User Customers' service needs, including without limitation, sales, service design, order taking, Provisioning, change orders, training, maintenance, trouble reports, repair, post-sale servicing, Billing, collection and inquiry. CLEC's End User Customers contacting Qwest in error will be instructed to contact CLEC; and Qwest's End User Customers contacting CLEC in error will be instructed to contact Qwest. In responding to calls, neither Party shall make disparaging remarks about each other. To the extent the correct provider can be determined, misdirected calls received by either Party will be referred to the proper provider of local Exchange Service; however, nothing in this Agreement shall be deemed to prohibit Qwest or CLEC from discussing its products and services with CLEC's or Qwest's End User Customers who call the other Party seeking such information. 6.4.2 CLEC shall transmit to Qwest all information necessary for the ordering (Billing, Directory Listing and other information), installation, repair, maintenance and post-installation servicing according to Qwest's standard procedures, as described in the Qwest Product Catalog (PCAT) available on Qwest's public web site located at xxxx://xxx.xxxxx.xxx/wholesale/pcat. Information shall be provided using Qwest's designated Local Service Request (LSR) format which may include the LSR, End User Customer and resale forms. 6.4.3 Qwest will use the same performance standards and criteria for installation, Provisioning, maintenance, and repair of services provided to CLEC for resale under this Agreement as Qwest provides to itself, its Affiliates, its subsidiaries, other Resellers, and Qwest retail End User Customers. The installation, Provisioning, maintenance, and repair processes for CLEC's resale service requests are detailed in the Access to OSS Section of this Agreement, and are applicable whether CLEC's resale service requests are submitted via Operational Support System or by facsimile. 6.4.4 CLEC is responsible for providing to Qwest complete and accurate End User Customer Directory Listing information including initial and updated information for Directory Assistance Service, white pages directories, and E911/911 Emergency Services. The Ancillary Services Section of this Agreement contains complete terms and conditions for Directory Listings for Directory Assistance Services, white pages directories, and E911/911 Emergency Services. 6.4.5 If Qwest's retail End User Customer, or the End User Customer's New Service Provider orders the discontinuance of the End User Customer's existing Qwest service in anticipation of the End User Customer moving to a New Service Provider, Qwest will render its closing xxxx to the End User Customer, discontinuing Billing as of the date of the discontinuance of Qwest's service to the End User Customer. If the Current Service Provider, or if the End User Customer's New Service Provider orders the discontinuance of existing resold service from the Current Service Provider, Qwest will xxxx the Current Service Provider for service through the date the End User Customer receives resold service from the Current Service Provider. Qwest will notify CLEC by Operational Support System interface, facsimile, or by other agreed-upon processes when an End User Customer moves from the Current Service Provider to a New Service Provider. Qwest will not provide the Current Service Provider with the name of the New Service Provider selected by the End User Customer. 6.4.6 CLEC shall provide Qwest and Qwest shall provide CLEC with points of contact for order entry, problem resolution and repair of the resold services. These points of contact will be identified for both CLEC and Qwest in the event special attention is required on a service request. 6.4.7 Prior to placing orders on behalf of the End User Customer, CLEC shall be responsible for obtaining and having in its possession Proof of Authorization (POA), as set forth in the POA Section of this Agreement. 6.4.8 Due Date intervals for CLEC's resale service requests are established when service requests are received by Qwest through Operational Support Systems or by facsimile. Intervals provided to CLEC shall be equivalent to intervals provided by Qwest to itself, its Affiliates, its subsidiaries, other Resellers, and to Qwest's retail End User Customers.

  • Content Standards You agree that you will not upload or provide content or otherwise post, transmit, distribute, or disseminate through the Zelle® Payment Service any material that: (1) is false, misleading, unlawful, obscene, indecent, lewd, pornographic, defamatory, libelous, threatening, harassing, hateful, abusive, or inflammatory; (2) encourages conduct that would be considered a criminal offense or gives rise to civil liability; (3) breaches or infringes any duty toward or rights of any person or entity, including rights of publicity, privacy or intellectual property; (4) contains corrupted data or any other harmful, disruptive, or destructive files; (5) advertises products or services competitive with Zelle®, as determined by Zelle® in its sole discretion; or (6) in Zelle®’s or our sole judgment, is objectionable, restricts or inhibits any person or entity from using or enjoying any portion of the Zelle® Payment Service, or which may expose us, Zelle® or our respective affiliates or customers to harm or liability of any nature.

Most Referenced Clauses

Most Referenced Definitions