Hot answers tagged

51

Yes, most browsers from the last 5-10 years will try the other A records if one fails to respond. This is sometimes called "browser retry" or "client retry" apparently. You'll pretty much only find stuff about it in the context of the various browser exploits which this feature enables against sites not using it (see DNS rebinding and DNS pinning, anti-dns ...


16

Depending on the feature set of the Registrar you're using, it may be advantageous to host your DNS elsewhere. If for example you require Dynamic DNS services (DNS records that are updated automatically when a destination's IP changes), or wildcard DNS (allowing <anything>.yourdomain.com to point to a certain IP), many Registrars do not offer these ...


9

You should host your DNS elsewhere. It will save your behind when you switch registrars, it will allow you to control TTLs like crazy so you actually have close to 0 perceived downtime for users when you change hosting, etc. I personally recommend DNS Made Easy. Have been with them for about 3 years now and they rule (at their price point).


7

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


7

If your site gets big enough where it's a problem (or your registrar sucks enough where it's a problem) then you should host DNS servers with another company. One that is known for such things. Otherwise, stay with the hosting provider. Hosting providers (especially the inexpensive ones) don't put the same effort into DNS as the companies that Do It For ...


7

Registrars and DNS servers for DNS management use a zone file which keeps all your DNS records for things such as A and AAAA records. Zone files are naturally unrestricted in the amount of information they can hold. However.... Some registrars have limits within their standard DNS management and require users to upgrade to a premium/pro DNS manager which ...


7

Working just within the browser, I couldn't tell if a particular direction was due to DNS or the webserver. To view webserver redirects in browsers, open up Developer Tools (either from the browser's menu, or by pressing F12), and click on the Network tab. It's a good idea to look for a Disable Cache option and check this so that all requests are done ...


6

It will remain fr.somewhere.com unless you have rewrite conditions configured correctly: RewriteCond %{HTTP_HOST} =fr.somewhere.com RewriteRule ^(.*)$ http://www.somewhere.com/$1 [R=permanent,L] I have a cname record created for blog.legoservices.com which just points to tumblr, but all you see is blog.legoservices.com.


6

Let's try with dig: $ dig -t NS tohid.ir.tc ; <<>> DiG 9.7.3 <<>> -t NS tohid.ir.tc ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 45593 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0 ;; QUESTION SECTION: ;tohid.ir.tc. IN NS ;; AUTHORITY ...


5

You don't have to set a CNAME. You could just set an A record pointing to the same IP address. In the hosting panel of your website you have then set the second domain as an alias.


4

The short answer is that Cloudflare is safe. Cloudflare is essentially nothing more than a content delivery network (CDN). The theory behind it is that they will cache copies of your website to their servers, which are spread across different locations. When a visitor visits your site the server that is closest to them is chosen and the connection has less ...


4

It's a little hard to tell without any context for the screenshot, but I think you've setup your DKIM record on _domainkey.board67.com.board67.com, instead of _domainkey.board67.com: $ dig TXT _domainkey.board67.com +short (no result) $ dig TXT _domainkey.board67.com.board67.com +short "t=y\;o=~\;" You shouldn't be entering the full hostname in the first ...


4

Whoops - misread your original question - take 2: According to my co-worker Mike Price -you need to switch your nameservers to crazydomains default ones to change your A record and your A record should point to the IP in the WP Engine User Portal. Then add to domains page in the WP engine User Portal. Finally, Change home/site URL 2. Also, You can also ...


4

The software 'WebsitePanel' does not allow you to make subdomains of a subdomain. You could use a sub-domain to create a new web site, but you cannot create another sub-domain based on it. From http://www.websitepanel.net/documentation/users-guide/domains/#ManagingSub-Domains


3

The approach of using a wildcard DNS record is probably the correct one for your use case. When you configure a wildcard DNS record, all requests to any subdomain will be resolved to the IP address of your webserver. You can then further process the request on your webserver. This approach is known as Virtual Hosting. Your webserver will decide which ...


3

It's a complicated answer if it's explained clearly. The domain's DNS will have to point the subdomain to the IP of the subdomain's DNS server (new DNS server explicitly for subdomain). If you require a simple answer, yes. Absolutely. You can have another DNS server. No problems. You should explicitly specify in the DNS of the domain to point this subdomain ...


3

Presumably, your registrar where you registered your domain name and likely where you modify your DNS records is known as the authority for your domain with a SOA statement of authority record. All registrars are a bit different, but assuming that you do not share your username and password with anyone, only you and your registrar can actually change the ...


3

It will depend on your DNS hosting is done. I personally use Zonomi. They have a DNS API. I can issue a request like https://zonomi.com/app/dns/dyndns.jsp?action=SET&name=mynewsubdomain.example.com&value=10.0.0.1&type=A&api_key=apikeyvaluehere to set the IP address for a new subdomain.


3

Most registrars will host your DNS records for the price of a domain name. Sorry this is not the case here. You may have to pay more for this. I cannot find specific information on this so you may have to ask. The whole offering seems rather ala' carte. Your www.dadb.com.au entry pointing to 8.8.8.8 is not a valid entry. This is not the IP address of ...


3

I reviewed your record and the error was because of the spaces( ) in the keys. the key must be in a single line without space. Look closely and remove all spaces and it will work properly. p= ...


3

SPF needs to list all sources of email. In addition to Freshbooks, you also need to list any other systems that also send email on behalf of your domain. The SPF you have entered will permit email from: a = a record for the domain include = allows email from freshbooks So right now, any email coming from the A record for your domain and Freshbooks will ...


3

This may be kind of easy! Your: ServerName www.mydomain.com ServerAlias mydomain.com ...is backwards, should be: ServerName mydomain.com ServerAlias www.mydomain.com Also, verify your DNS settings, just in case. You should have: A record for mydomain.com that is an IP address Either a CNAME or A record where: _The CNAME is an alias ...


3

The Windows flushdns option only clears your local DNS cache. The next time you request a web address your system will make a new query to your remote DNS servers for the IP address. If your remote DNS servers haven't picked up the new IP address then your system will re-cache the old IP locally. There's generally nothing you can do to force remote DNS ...


3

If your hosting account is configured to use the domain example.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.exampleA.com to ns.exampleB.com). The DNS will then be handled by your hosting provider, which should already ...


3

It will change for sure -- it just can take up to 48 hours for changes to propagate (you have to check TTL (time to live) value for your DNS records). Most likely you (your computer) still see the old cached details. When cache will expire you will get proper up-to-date details. When you accessing it via mobile device/another country, these details were ...


3

Relocating the webserver to the US will hugely improve server response time for US users. Investing in better DNS servers will also improve response time, but only for the first request. The following analysis shows where your speed bottlenecks are at present. (Short version: most of the 1-2 seconds is the time it takes to reach the webserver, not the DNS ...


3

There are two separate elements to make DNSSEC work. Generate keys and sign the DNS records. Put the hash of the key in your parent zone (.se for example.se) via the DS record. The latter is possible with .se and a growing number of other TLDs (refer to DNSSEC deployment on wikipedia or subscribe to the dnssec-deployment mailing list). In regards to ...


2

Regarding your question about whether or not to inform Google of this issue: no, this appears to clearly be a technical issue on the hosting side. After resolving it on your side, it'll automatically get resolved as Google recrawls your URLs. If this were a web-spam issue (which from your description does not appear to be the case), you could submit a ...


2

This is basic DNS load balancing distribution technique: DNS Round Robin. This has nothing to do with browser, it depends on the implementation of the resolver , and the local/remote cache of the DNS address. Changes are that if a server fail, due to caching in the DNS layer your website may be inaccessible. See here for a basic explanation about Round ...


2

One advantage of using the name servers from the registrar is that they are very highly distributed, and that can effect the speed of lookups and global propagation. For instance, Godaddy and Enom host so many domain names that the time to live of for newly purchased domains and for DNS modifications is SUPER fast.



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