Hot answers tagged dns
This just might be the shortest answer I have ever written... You need to create a CNAME record in your DNS that points www.xyz.tk to xyz.tk.
You seem to have 2 A records for example.com pointing to very different IP addresses, one of which is the one that www.example.com resolves to (which is the wrong one). My guess is that it's picking the first one that it finds!?
It sounds like you may have initially changed the NAMESERVERS which broke the Windows Exchange CNAME. If the domain is hosted on GoDaddy then you need to access the DNS records, this is where the Windows Exchange CNAME is held. You should see an A record entry like A example.com 126.96.36.199 example.com will be your domain, the IP will be the GoDaddy ...
What you need to do is make a temporary subdomain using an A record pointed to the new shared server. Call it something like testing.example.com and point it to the new servers IP. Then ftp in, open or create an .htaccess, and point the request to whatever folder it needs to run using something like following. We will assume for this example that it's a ...
Some hosts/registrars allow you to create NS records. You could then create a record like this: subdomain.domain.tld NS ns3.domain.tld This will delegate the request for the lookup to another nameserver. Naturally, passing that request will require contacting the nameservers of the primary domain, which is probably not something you want. To be honest ...
Don't mind, I solved it! It was enough add the define( 'NOBLOGREDIRECT', '' ); in wp-config.php right below the multisite rules! I managed to insert my website homepage between '' To explain it better: if you insert a url between the '', when an user goes to a not exsisting subdomain such hello.example.com, he'll be redirected to the url you inserted; ...
Yes, just change the name servers and you won't have any downtime as long as you leave the original server up. Keep in mind that changes on one server won't be reflected on the other server, so that if you have a mailling list for people to join and they join on the old server, unless you sync data it will be lost. Also be aware that the new nameserver will ...
After much pulling-out-of-hair, I got this message today: I logged into my router to check the DNS settings like we discussed. I just happened to click on security and noticed the "firewall" box was checked. I un-checked the box, clicked save, opened a new tab and entered our domain. Eureka! our site opened right up! It was my router.
You can't set nameservers and CNAME records. Go to Namecheap.com --> Manage Domains and click on the domain you want to manage. Then, go to All Host Records and change the settings to this.
Only top voted, non community-wiki answers of a minimum length are eligible