Tag Info

Hot answers tagged

13

From ServerFault: The requirement to run two nameservers comes from ยง4.1 of RFC 1034, and is indeed for redundancy. There are numerous providers who will offer you very cheap "secondary DNS" service where they transfer the zone file from your primary server using AXFR. For example, in the UK we have a well-known provider who'll do secondary service ...


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 ...


6

Nothing. "Name Server" is short for "Domain Name Server", which is what "DNS" stands for.


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 ...


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

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 ...


3

Some domains allow you to hide your details, such as .co.uk address, .com address hiding your credentials isnt. However, in a number of webhosting places, they actually own the domain on your behalf, as a result your details are then hidden because only the webhoster knows.


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

Assuming you're using Linux/OS X, you can do dig @nameserver.to.test a www.mydomain.com on the command line, which should do what you want.


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

No ISP DNS is required. Just setup your local DNS to use 8.8.8.8 and 8.8.4.4. If necessary you can set your router to distribute those addresses and bypass your local ISP altogether.


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 ...


3

AFAIK unless somethings changed you arent able to use Namesevers as they are used for the main domain, you will have to use a A domain or a CNAME to cover the domain. Sorry to break the news to you.


2

Unless you have a static IP, you should just point the domain to your web host's nameservers. Even if you've purchased a unique IP, the IP can change if your web host decides to move you to a different server (e.g. a temporary relocation while the server is being fixed or upgraded) or restructure their network. Very rarely would you ever want to manually ...


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

The alternatives are for just this case, for when the main nameserver isn't available. However that only works if your site isn't on the same datacenter as the first and second nameservers.


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

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

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

I like to use http://www.whatsmydns.net to check the propagation of DNS settings it checks across about 20 different DNS servers



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