Great News Mr Admin!

Hosting Support
1

i Use Microsoft CoPilot and Open AI a lot when i am researching and studying, and i thought to ask if it were possible to use Microsoft Azure to create domain names for free to public userend users; this is that conversation:

“Is it possible to use Microsoft azure to create domain name for userend users with free to public services like infintyfree and ifast?”

Yes, you can use Microsoft Azure to create domain names for end users and integrate them with free public services like InfinityFree and iFastNet. Here’s a general overview of how you can achieve this:

Create a Custom Domain in Azure:
First, you’ll need to register a domain name with a domain registrar. You can use any accredited domain registrar for this purpose.
Once you have your domain name, you can add it to your Azure account. You can follow the steps outlined (Add your custom domain - Microsoft Entra | Microsoft Learn) to add your custom domain to Azure.

Configure DNS Settings:
After adding your custom domain to Azure, you’ll need to configure the DNS settings. This involves creating DNS records such as A, CNAME, and TXT records to point your domain to the appropriate IP addresses or services.

You can find detailed instructions on how to create DNS records for a web app in Azure ( Tutorial: Create custom Azure DNS records for a web app)
Integrate with InfinityFree:

  • InfinityFree allows you to bring your own domain name or use a free subdomain. You can follow the steps provided (https://www.infinityfree.com/)

By following these steps, you can create and manage custom domain names using
Microsoft Azure and integrate them with free public services like InfinityFree and iFastNet. If you have any specific questions or need further assistance, feel free to ask!

And in regard to SLL Certificates, Microsoft Azure offers Free-to-public Services of the sort but have restrictions which i found completly awesome for my usage of your service!

“Does Microsoft Azure provide or support SSL certificates which the free-to-public userend users can use on their respective domains, not unlike ZeroSSL, GoGetSLL, GoogleTrust?”

Yes, Azure can be used to provide SSL certificates for custom domains, which can be beneficial for end users. Here are a few ways you can achieve this:
Yes, Microsoft Azure does provide free SSL certificates for custom domains through its App Service Managed Certificates. These certificates are easy to set up and renew automatically, making them a convenient option for securing custom domains (Add and manage TLS/SSL certificates - Azure App Service | Microsoft Learn)

They don't support wildcard certificates.
They can't be used as client certificates.
They don't support private DNS.
They aren't exportable.
They aren't supported in an App Service Environment.
They only support alphanumeric characters, dashes (-), and periods (.).
They only support custom domains of up to 64 characters

(Do we have free SSL Certificate's in the Azure service's? like ACM certs in AWS - Microsoft Q&A)

If these limitations are acceptable for your use case, Azure’s free managed certificates can be a great option for securing your custom domains. If you need more advanced features, you might consider using third-party SSL certificate providers like ZeroSSL, GoGetSSL, or Google Trust Services.

I found this really awesome and rushed over to the IF form to tell everyone!

:stuck_out_tongue:

2

As a random noobie, what i need from this is the “.resume” domain extension!

3

Hello,

The text that comes after the final dot is a TLD, not a domain name. .resume currently does not exist as a TLD, you can view the current list here: List of Internet top-level domains - Wikipedia

7 Likes
4

When I read the output of that conversation, the answer clearly appears to be “no”:

You can “create” a domain in Azure just like you can “create” one on your hosting account: you can link a domain you already own.

Which also boils down to no. Azure provides free SSL certificates for websites hosted on their Azure App Service. And crucially:

Meaning you can’t host them here.

All in all: yes, you can host your domain with InfinityFree, and you can host your domain with Azure. But Azure doesn’t provide anything that could be useful while using our service.

We already provide DNS hosting and we already provide free SSL certificates. What are you hoping to gain by adding Azure to the mix?

7 Likes
5

I am hoping to ad more user end safety and user ability to communicate through a bad com infrastructure in decaying economical and political circumstance (It is the good i am trying to take from all the crap locally).

i interpreted the meaning of copilots posts as “The domain server can simply write the domain extensions and certificates so long as it meet their usage policies.”

which to me meant a greater diversity of domain extensions and a greater acceptance of ssl certificates, due to Microsoft and Google basically “making” and supporting the entire concept.

i will try to get my resume page up again, my back ups are all over the place and it is getting harder and harder to not have my data endlessly stolen.

The concept is important to me because i need a user account which takes a user name
and a resume in a .txt file and post it to www.username.resume at a rate per month/year and market via resume workshop companies.

simply iframe a text file to a domain and that is what i wanted in regard to an online resume. however JohnDoe.zt.er just is not right for the context, in my opinion, where .resume is just perfect.

6

Ah, unfortunately domains are not free, and you can’t just create a new TLD.

So you can’t have .resume, and anything that is <something_here>.TLD costs money

Some services (Like IF) will give you <something_here>.domain.TLD for free (like you can create “mysite.rf.gd” for example)

Hey discourse, “domain” is not a valid HTML element, don’t treat it as such

7 Likes
7

I am not a hugely experienced computer programmer, and my research leads me to believe that all you need is a dns resolver server of your own to create and support domain extensions and all the rhetoric in regard is a simple rule of thumb and that doing so would give you a bigger market edge and a more diverse array of extensions.

I have this theory that the extensions that are offered on IF and IFAST are important locally to the servers. where here in Canada; .net .ca .gov .edu .com are social logically considered important by the markets where a url written like 'cake.bussiness.what.kj" would get no traffic at all regardless if it was a great website with good services or not.

If you created a url like “my.business.ca” or “www.JohnDoes.Resume” that domain would be much more likely to “trend” as it is called these days and there for leave IF in a greater position to apply transaction interest fees and benefit from user end support which would in turn supports the free-to-public services.

In the case of a free-to-public services like IF and ifast, more diverse arrays of available names, which can be arranged in a simile of relevance to the users usage of them as well as importantly marketed to relevant distributors would be hugely stabilizing on the business end of things.

For example the .resume extension being marketed to resume writing startups for their free-to-public services because you can batch market resume hosting to those that write them for people who cant do that themselves, which is a market that is mostly 14-30.

100 name.resume addresses for 40$/month would work for social services usage of employment training markets and job seeker programs. which honestly, in the current system of things, that same $40/m is just massively stolen by every sort of bastard wearing cloths out there and is ultimately not helping the clients with any notable spending proficiency.

the high ball market of unemployment services is about 2billion people in 5200 state/provinces in 230ish countries and territories. Where the united states spends about 7trillion dollars per annum for their social service programs. which as i said is mostly stolen and therefor leaves a great market potential in that the government pays the bills for the 2billion clients and statistically would like to get clients training, jobs, and stable housing and domains can do all of the above in a unique manor.

If i created 1 Ifast dns in every cottage town than you could do whatever with domain extensions as 2million resolvers is substantially bigger than anyone else with an opinion, which is useful to me because my target markets are the fallen lives landing on the door steps of churches, social services and other similar social networks. which prevents a full fall to a sidewalk some times but more often than not the clients get stuck there and spiritually rot there.

You could probably use vpn services to create an international network of dns servers, and there for you can write and support ssl certificates and various domain extensions yourself without regard for the rest of the “name holders”.

Just brain storming is support as my personal finances are uber fked right now will that is going on.

In conclusion, marketing your service to schools, resume workshops and social services would ultimately help in offering more free-to-public services.

I will try to crunch out an example for “name.resume” right now and post it in a comment when completed.

-Jedi

8

here is a first draft of a “resume domain”
http://christophermancini.my-style.in/

It is one of my old resumes.

i try very hard to not vsync the server host due to local happenings.
could use a upload and download button probably.

i will try to nickel and dime a better example out.

9

That is incorrect. It is technically possible to “host” a TLD with the proper private DNS servers, but a setup like that would only be usable internally- by you and anyone else connected to your network. I actually don’t think I’d recommend doing it at all in most cases, as it’s a huge hassle for something without much advantage.

Running a TLD/extension that other people can actually use to visit your website via the internet? That’s a lot more involved. I would go more into it, but I think the admin explained it well enough last time you brought it up.

5 Likes
10

True, but then you are the only one who can access them.

If someone else wants to access your domain, they would have to change their DNS resolver to yours.

Creating a new TLD that is globally available is neither easy or cheap. The last time ICANN accepted ideas was back in 2012, and approved ideas required proof of backend services, and a lot of money.

See:

6 Likes
11

Yes, i noticed that the auction of words is huge within the domains markets. It is the same competition as stock name ticker symbols literally. though i think that in the prospect of “resumes” .work, .job , .carrer and things of that sort might work just as well. These other “name sellers” seem to just batch buy/sell bulk words, which kinda of sucks because simple tasks get dinged with ridiculous prices.

12

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.