I'm designing a website for domain registration and hosting company using wordpress...I have designed the website and added the plugin for domain name search...now my question is
1) Is that plugin is enough to search and find available domain names globally ?
or
I need pay for someone like go daddy or name cheap or who is to find out the available domain name in my website ?
There are many domain name registries. For example .com TLD is distributed by Verisign whereas a .uk TLD is distributed by Nominet (this will include domain extensions like .co.uk or .org.uk etc...)
So the question is are you directly talking to the domain registries or are you resellers of other brands. For example you could be a reseller of Go Daddy or 101domains or 123-reg. Which basically means (as an example) you will talk to their API for a domain name availability and as long as they support that domain extension, they will come back to you on whether it is available or not.
Your question is too general to be answered specifically.
Related
I have a website hosted on a cPanel, I need to change it to Cloudflare nameservers and then the dns records so the main domain will be pointed to a vps ip address and the mx records keep using cPanel records. The problem is I found a lot of TXT records created by the cPanel and I don't know what I should take or leave since they look so random.
My cPanel DNS Zone Editor:
Notice:
I have two active domains on my cPanel, the first is the main domain which I would like to transfer to point to my vps, the second should keep working on the cPanel. but I found related txt records in the first domain, looks like this caldav._tcp.DOMAIN2.tn.DOMAIN1.tn. (check screenshot)? Why does it even exists in the main domain records?
I just need to move the main domain and keep the mailing service with cPanel! Which TXT records should I create on Cloudflare after I change the domain nameservers?
If you are planning on keeping your eMail where it is but only plan on changing the web site to use CloudFlare you should really leave ALL of these TXT records as they are.
SPF = Sender Policy Framework (which is a list of servers or services that can send eMail using your domain name)
DKIM = Domain Key Identified Mail (is a form of anti-alteration system to stop eMails being altered in transit)
DKIM is unique to each domain and subdomain so if you have a eMail service on the second domain you should have an SPF & DKIM record for them too.
As for the bottom rules I don't know what they are.
Can I add multiple hosts name servers for the same domain?
Let's say I have a domain on Godaddy, can I set WordPress Name Servers AND AWS Name Servers on it?
Specific Scenario:
I have static pages on Wordpress
I have django application behind an ELB on AWS
I want both to be on new.example
I want the static pages served by new.example
I want app.new.example to serve the django application.
Can I add multiple hosts name servers for the same domain?
Technically, yes (all domain names have typically at least two nameservers), but in the context of your question, no, as it would not operate the way you think it does.
You delegate your domain name to a set of nameservers that have all the content of the zone. It does not matter where the content pointed by records in the zone are handled, it can be elsewhere.
You will have to choose one company to provide DNS service to you, and then through their web panel or equivalent you will point new.example to point to your static pages on WordPress, and app.new.example to point to ELB on AWS.
I recently bought a domain name from Names.co.uk.
My home internet has Dynamic IP and I want to link this ip with my domain name.
Is there a way?
PS: I have a No-Ip.org account as well..
will this help to set everything together?
Thank you all for any help or advice
Kind regards
Yiannis
Can I Use My Own Domain Name with No-IP?
Upgrading to No-IP Plus Managed DNS lets you use your own domain
name(s) with No-IP.
To add your own domain visit our Managed DNS services page. You’ll be
prompted to add the domain name(s) that you want added to our system.
Pricing for this service can be found on our pricing page.
I manage a hosting server using WHM. I have two cPanel accounts on this server, one for exampletest.com (account name is exampletest) and one for example.com (account name example). We have a Wordpress site that was working well at exampletest.com but we keep running into problems when we try to migrate it to example.com. I believe it has to do with one WordPress plugin that doesn't migrate well.
So we had the idea to simply take the example.com domain and point it to the exampletest cPanel account, then update the domain for WordPress in the database. However, one potential issue I can see is that we have many active email addresses on the example account. I fear that associating the example.com domain to the exampletest account will break the email addresses.
Keeping the above in mind, I have a couple questions:
Will associating the example.com domain to the exampletest account break the emails? If so, is there a workaround (moving the email addresses to the new account somehow?)
Is there a better way to go about doing this that I'm not thinking of?
The best way of transferring your wordpress site would be to copy the files, create a database user with the same login details and import the database. Wordpress shouldn't be able to tell the difference.
One way would be to assign a static IP address to exampletest and point example.com's A record to that IP.
Due to the way WHM's DNS and port binding is set up it will not let you set up the same domain on two seperate accounts.
You could treat www. as a seperate subdomain and add the subdomain www.example.com to exampletest as an addon domain and remove the www A record from example first. Redirect all web traffic from example.com to www.example.com or use another sub-domain such as www2.
Another option would be transfer the emails, you can either use the transfer tools in WHM > Transfers or use http://imapsync.lamiral.info/
I am working on an ASP.NET MVC web app that allows people to publish content, but other than publish the content to a remote server, I want to allow people to use their domain name directly. For example, the user "Tom" can have his domain name TomSite.com point to http://www.mywebapp.com/user/tom, but the sub path will also be mapped. For example, TomSite.com/path will be mapped to www.mywebapp.com/user/tom/path, and this is transparent to the web visitor. The visitor will never see "mywebapp.com" anywhere on TomSite.com.
I think Smugmug.com provides such service, to allow people to use their own domain name for the photo portfolio. I want to achieve the same result.
How can I do this? Thanks!
This require multiple steps.
First you have to find out how your users will configure their domain to have a CNAME record for you site. You can archieve this in a number of ways where the best is education. Making partnerships with hosting providers requires a great deal of volume.
In IIS this will require you to either add each host name manually (however this could also be archieved through scripting) or have a dedicated IP address only for you site.
There is also a need for the domain to be associated with an account. The user has to add this themselves and you would probably add a check in the interface which confirms the domain is pointed at your server. The code for this would look like (remember to include the System.Net namespace).
if (Dns.GetHostEntry("www.user.example.com").HostName == "www.example.com")
{
// www.user.example.com is a CNAME for www.example.com
}
In you ASP.NET MVC project you need to implement routes for this particular purpose. Create a custom class inheriting from Route which also takes the domain into account.
Smugmug (who you mentioned) get their users to setup a CNAME record that will alias the url for the user's personal photo section. For most users this will probably require them contacting their host or looking up help files in order to get it all setup.
So, while www.tomsite.com could transparently serve up pages hosted at www.mywebapp.com the users will have to put some kind of effort in. To make it a completely seamless you will need some kind of arrangement with the users web host (Smugmug appear to have such an arrangement with GoDaddy).
I doubt you will be able to setup such integration with all the web hosts out there, so the only complete solution would be to host the websites of your users yourself (I do not know enough about your wider situation to determine if that is a reasonable solution).
Note: setting up an alias on your own web server (aka url rewriting) will not work, unless you host their site yourself, as obviously people fetching from your user's domain will not arrive at your server in the first place.
Have each customer's friendlyname pointed at the external ip address of your webserver.
Use IIS to resolve the friendlyname specified in the host header request to the logical website you want delivered to that friendlyname. IIS will happily map both a website and a virtual folder to the same folder in the file system. Create a website for each customer. Then bind that website to the customer's friendlyname.
Remember to map the default website only to your own friendlyname(s). If you leave it in promiscuous mode (mapped to "*") results will be unpredictable.
To set host header mapping
Select Default Web Site under the Sites node. In the Actions pane at top right click on Bindings... to open the Site Bindings dialog. There will be a list of bindings, probably containing a single entry that says http * 80. Select this and click the Edit... button. Set Host name to your own friendlyname.
Run IIS7 Manager and for each customer site create a website under the Sites node. Set both file path and host header binding while you are creating each web site. Obviously the host header binding (host name) should be that customer's friendlyname.
Just make a new record in your webserver setting tomsite.com directly to your mywebapp.com/user/tom/ path ?
See it like an alias :)
Ofcourse, since you're asp.net/windows based, i think you'll have to digg deep into IIS to automate this kind of stuff. If you were on apache it would be adding 3 simple lines to httpd.conf.