Tag Info

Hot answers tagged

12

Typically no, most major registrars will implement NS updates very quickly (minutes, or just a few hours). What remains is the TTL (time to live) value set on records served by your existing name servers that resolve your domain to its IP. The typical cache period is 4 hours, however ISP's are free to ignore that, and continue to serve the old IP sometimes ...


5

As a practical matter, I like using What's My DNS, an online tool that samples a number of DNS servers across the planet which will give some idea who's got what, where. It's a great way to get a kind of an answer to the question "has my DNS propagated?"


5

There are several steps to this process: Find your server IP's I'm assuming you have WHM here? Open http://IP/whm (or the path to your server control panel installation) then go to IP Functions >> show IP address usage & check your primary and secondary IP Address. Make a note of these two IP's Register your Nameservers You need to register your ...


5

Nameservers comes first. The browser asks who knows about domain.com and the answer comes back with the nameservers that the domain is configured with (via the registrar). Then those nameservers are asked about DNS information for domain.com and www.domain.com and they return the IP. So if it's not working then the problem is with the DNS records for the ...


5

It sounds like your domain records have not propagated yet. This means that the domain name servers around the world that store a record of your domain information haven't updated with the latest details, so they are still 'sending' visitors to your old server. The solution is to wait. It can take between 0 and 48 hours for domain name changes to update ...


5

You answered your own question. They said to set CNAME or A record. As for the Nameservers, unless GitHub says otherwise, you are going to ask what the A Record or CNAME should be set on your domain name. Then, if you don't know how, ask your Domain Register about setting the CAME or A Record to what it needs to be for your domain name.


4

You just need set up an MX (mail exchange) record on your Web24's DNS through the management panel to point to the mailserver. CheapDomains will have to tell you just what the email server is called so you can do that. You can leave your domain's nameserver to continue to point to Web24's nameservers.


4

I think a better way to have handled this is not to have changed the nameservers but simply to have changed the A record for the domain to be the IP address of the new web host. Then after the domain was renewed I would have changed the name servers to the new web host. Simpler and maybe less complicated. But either way the change should have occurred ...


3

Under "Add a CNAME Record", enter secure.randomdomain.com. in the "Name" field and secure.mydomain.com. in the "CNAME" field and click "Add CNAME Record". Don't put anything in the "Add an A Record" fields. The CNAME record just means that the browser (OS really) will look up the first domain (the one in the "Name" field) and find a second domain name (the ...


3

Basically, what happens when you change your nameservers at your registrar is that they submit the changes to the registry, which keeps a WHOIS database as well as an authoritative nameserver for that TLD. So, in theory, the AS for your TLD is the first to know about the changed nameservers via updated NS records. That is where the DNS propagation begins. ...


3

Larry you need to add the domain to your new host. If you are using cPanel, then there would be a option for you to add the addondomain. Over there add the domain name and the directory from where you want the domain to run. If the newly added domain is pointing to your new host name servers, then it will start running from the directory you specified.


3

If your hosting account is configured to use the domain site.com (presumably specified when you setup the hosting account), then you just need to change the NAMESERVERs at your domain registrar to point to your hosting provider (ie. change ns.a.com to ns.b.com). The DNS will then be handled by your hosting provider, which should already have been configured ...


3

Suppose I have a domain such as example.com and I configure the domain's primary and secondary nameserver to be ns1.example2.com and ns2.example2.com. Prior to configuring nameservers for your domain, you would need to register each nameserver at your domain's registrar, which requires the hostname and the IP address for the nameserver. Example steps for ...


2

You have to get the DNS servers from Network Solutions and set them in the GoDaddy control panel (under Domains, click on the domain in question, then click set nameservers). It should be something like: dns1.networksolutions.com dns2.networksolutions.com (In my screenshot, I have ns1.dreamhost.com ns2. ns3.) You can put more that 3 nameservers in the ...


2

Regarding the DNS settings, sure, you will need to add two NS servers, if you don't own any nameservers , I suggest you to try namecheap freedns service, they will host your dns settings and provide you with a control panel, then, you can add your records. @domain.com A (IP ADDRESS OF WEB SERVER) www A (IP ADDRESS OF WEB SERVER) @ MX ...


2

this support article from your new hosts support site discusses the different kinds of domains you can add via their cpanel (parked, addon etc) and there is also a tutioral on adding an addon domain (which is what I suspect you need to do). Let us know if you need any more help.


2

My question is what ports do i need to portforward for a fully working server, with both SSL, SSH and mail working? You need to set up ports 80, 443 (for SSL if you want it), port 22 (SSH/Telnet) and maybe port 21 for FTP if you want that. Mail: POP3 - port 110 IMAP - port 143 SMTP - port 25 Secure SMTP (SSMTP) - port 465 Secure IMAP (IMAP4-SSL) - port ...


2

There isn't a database beyond the whois - which won't help you as it isn't updated frequently enough. Try www.iptools.com, they have a wide variety of tools for checking your domain's DNS settings and more besides. I would also reccommend mxtoolbox.com for checking mx records and email blacklists.


2

You can currently only use the two CloudFlare nameservers at your registrar. While you could theoretically add another to your registar, this would then mean that some of those requests would not be proxied by CloudFlare (you would also likely get a notification from us that your nameservers have changed). We are considering allowing for additional ...


2

I think you've got some of the terminology a little confused but not to worry. What you mean is: Should I use Network Solutions (my registrar's) nameservers and point my A Record to godaddy's webserver IP? OR Should I change the Nameserver setting on Network Solutions to point to Godaddy's nameservers and have Godaddy's nameservers point to Godaddys ...


2

The answer is YES, unless you also copy all your current DNS records to the new DNS server too. You should do that before you move your name servers, although some control panels don't allow that until they are officially named as your name server. In that case, you make the changes ASAP although mail flow will be delayed while they propagate. Why don't you ...


2

Not a command line tool, but if you visit http://www.gwebtools.com/ns-spy/ and add your nameserver after the trailing slash e.g. http://www.gwebtools.com/ns-spy/udns1.ultradns.net or http://www.gwebtools.com/ns-spy/ns1.servage.net and then select the domain you need to view, you'll be able to see that information.


2

Some have two, some have four (which is the maximum). Pinging my hosts NS addresses shows that each one is hosted on a different IP. The reason for the requirement is failover - if the first NS fails the second is used and so on down the list. So, you can set both the nameservers to the same address but bear in mind you won't have any backup if your ...


2

Unless you're running your own DNS server (typically BIND), you don't need to muck about with your nameserver settings inside of namescheap. Running BIND is a fairly complicated matter requiring significant DNS engineering skills, so it's unlikely that this is your situation. I would suggest restoring your domain's nameserver settings back to normal and ...


2

You have long way to go now. You'll need to understand DNS thoroughly. Just buy any good DNS book( DNS and BIND, 5th Edition - O'Reilly Media is good enough) and learn how to configure it. You can use Webmin to configure you VPS but it's little buggy. I also tried like you, but later switched to Managed VPS with Cpanel due to shortage of time(I now pay ...


2

For something to be identified as a nameserver it must be one. This means that the server at superexample.com must be running both an HTTP server (HTTPD) and a DNS server (BIND) with a publicly reachable address and port.. You can see this with a lot of hosting sites, they run their own DNS servers and set themselves as the nameserver. Here is the record ...


2

It needs a couple of things to be done: Find out IP Address, ns1.somehosting.com is pointing to. Create a Child Name Server say ns1.superexample.com pointing to the same IP Address. Modify NS of superexample.com to ns1.superexample.com Some, DNS does not allow single NS entry, in that case find two IP addresses being pointed by ns1.somehosting.com and ...


2

Browsers cache DNS which is separate from just clearing the cache which deletes temporary files. To delete the DNS cache in Firefox follow these easy steps: Enter about:config into the address bar If you receive an acknowledge warning click next Find a option that is labeled network.dnsCacheExpiration and set its value to 0 Restart Firefox In the event ...



Only top voted, non community-wiki answers of a minimum length are eligible