A .भारत (.bharat) domain is an internationalised country code domain for India, operated by NIXI, and you register one through a .in accredited registrar that supports it. The website side works through a standard conversion to an ASCII form (xn--h2brj9c for the Devanagari .भारत), while email is where problems tend to appear. Here is how to set it up and what to test first.
IANA's root zone database lists .भारत as a country code top level domain designated for the two letter code IN, with the National Internet Exchange of India (NIXI) as manager and registry services at registry.in. The ASCII form used inside the DNS is xn--h2brj9c.
NIXI's IDN page lists the .Bharat string in a table covering several Indian scripts, including Devanagari, Bengali, Telugu, Gujarati, Tamil, Gurmukhi, Kannada, Oriya, Malayalam and Arabic script for Urdu, and says seven scripts were launched in 2014. NIXI's FAQ adds that sunrise registration for several further languages opened on 16 March 2020, with general first come, first served availability from 15 June 2020. So there is more than one .bharat, one per script, each with its own punycode form.
According to NIXI's FAQ, you register an IDN through a .in accredited registrar, and the registrar sets the retail price. Not every registrar sells them. GoDaddy's own .in help page, for example, lists internationalised names as not supported for .in, so check support for the script you want before choosing a registrar.
Ask the registrar three things: does it sell the exact script version you want, does the registrant verification step apply (NIXI's IDN page links its eKYC portal and says KYC is mandatory, while Domain India tells customers to ask support what applies to .bharat), and does its DNS manager accept IDN names. Verification and suspension work as described in our .in eKYC guide, so apply that to your .bharat name until your registrar says otherwise.
Pick a name carefully. Think about the spelling that people will type on a phone keyboard, and consider registering the equivalent Latin script name too. Our guide to regional language websites covers content and fonts, and our domain extensions guide covers where IDNs fit among the rest.
The DNS itself only carries ASCII. Each non Latin label is converted to Punycode and prefixed with xn--, using the IDNA standard, so a name written in Devanagari is looked up in its xn-- form while browsers display the native script to users. Nothing about the DNS infrastructure changes.
In practice you add the same records you would for any domain: A or CNAME for the site, MX for email, TXT for SPF and DKIM. The DNS checker and how to check DNS records will show them. When you type the name into a checker or a control panel, try the xn-- form if the native script is rejected. Hosting control panels and certificate tools differ in how they accept IDNs, so test one name end to end before you build the site, and ask your host and the certificate provider to confirm they issue for the xn-- form.
Nameserver changes work as normal. If you are unsure how to point a domain at a host, read what a nameserver is. Also note a security point: the same script can contain lookalike characters, an IDN homograph attack, which is a reason to buy obvious variants of your own name.
There are two separate questions, and they have different answers. If only the domain is in Devanagari and the part before the @ is plain English letters (info@yourname.bharat), the domain converts to its xn-- form and ordinary mail systems can handle it, so MX records and the setup in how to set up MX records apply as usual.
If the part before the @ is also in Devanagari, every server in the path must support SMTPUTF8 (internationalised email, the RFC 6530 series). Wikipedia's summary of international email describes support as rolling out only slowly, and notes announcements from Google (2014, for Gmail) and Microsoft (December 2017 for Office 365, January 2018 for Exchange Online). Those announcements are several years old and do not show how any provider behaves today. There is no general ASCII fallback for a non ASCII local part, so a receiving server that does not support it may reject the mail.
The safe approach is to use ASCII mailbox names on the .bharat domain, send test messages to Gmail, Outlook and your own customers before printing anything, and keep an alias on an ASCII domain as a backup. See SPF, DKIM and DMARC for authentication, which still matters for IDN domains.
It depends on your audience. For a business serving Hindi or other regional language speakers, a name in their script can be easier to read and trust. The price is friction: some registrars do not sell it, some tools handle the xn-- form poorly, and email needs testing. Many businesses keep a conventional .in or .com domain as the primary address for email and use the Indian script name as an additional front door that redirects to the main site.
If you go ahead, record the xn-- form in your documentation so whoever manages DNS later can find it. This is general information, so confirm current availability and rules with the registry or your registrar.
HostBible's DNS checker lets you look up the records on any domain, including the xn-- form of an Indian script name, so you can confirm what is published before you rely on it.
Open the DNS checker