If your hosting company requires you to use their nameservers, or you run your own DNS server, you'll need to change the authoritative nameservers for your domain. Changing your nameservers from Porkbun to another DNS host will usually break any Porkbun-hosted services such as web hosting and email. Make sure that your new DNS host is set up to answer requests for these services before changing nameservers. Changes to your authoritative nameservers will take up to 48 hours to propagate worldwide. In practice, most places will see the change within a few hours. To track nameserver propagation, you can use a free service like www. Please note that if you wish to use an authoritative nameserver that is a subdomain of the domain itself, you'll first need to create a "glue" record in the "Domain Hosts" area under the gear. How to change your nameservers If your hosting company requires you to use their nameservers, or you run your own DNS server, you'll need to change the authoritative nameservers for your domain.
Follow these simple tips in order to smoothly transfer your domain name.
Please note : changes in NS servers and DNS-records may take effect after a period of time — from 4 to 72 hours. This is due to the storage of information about domains at Internet providers: they save all user's requests and store them for a certain time. UA, you need to: Place an order for name servers NS-servers for your domain on the " Name Servers " page: to activate name servers, you must confirm your contact mail: if you have not done this yet, then you will receive a letter from NIC. UA while ordering name servers; name servers are provided free of charge for the domains served by NIC. Set the NIC. UA name servers in the domain: if the domain is served by NIC.
Webmasters Stack Exchange is a question and answer site for pro webmasters. It only takes a minute to sign up. Connect and share knowledge within a single location that is structured and easy to search. Much more than web hosting, DNS hosting is a commodity service, so as long as the DNS provider is competent, there's not much difference from one provider to another. The reasons are:. So for me, cost and convenience are the biggest factors. And it's typically cheapest and most convenient to use the web host's DNS servers. I typically register my domains through my web host as well since it's another commodity service, and web hosts are a lot less shady on average than registrars , so I can manage nearly everything from one control panel. When I register a new domain, it's automatically added to my account, the DNS entries are created, and the vhost is set up on the web server. On projects that demand higher security, I might look for a web host that supports DNSSEC though this is irrelevant if you're using one of the many TLDs whose root nameservers don't support it.
Server Fault is a question and answer site for system and network administrators. It only takes a minute to sign up. Connect and share knowledge within a single location that is structured and easy to search. I was considering switching to Amazon EC2 to host my website to handle more traffic. It seems like I would have to update DNS records to point to the new server but I was wondering if there was a way to avoid having to wait for the new DNS record to propagate. Putting the code on both hosts would not work for me since the app writes to a database pretty frequently.