Tag Info

New answers tagged

0

Try: restarting your web server clear your cache and the one of the people having trouble flush your DNS cache and the one of the people having trouble eventually, restart your DNS server reset your .htaccess file check if you have misconfigured something in your server check your firewall rules try changing the home IP address if you have a static one ...


3

I think it goes like this: Purchase the new domain name. Point the new domain name (A record) to your IP address / web server. Configure your web server (host headers) to accept both domain names to your IP address. You now have two domain names pointing to the same IP address / web server. The website can be accessed from a browser using either domain ...


1

You would first create the new site and make sure your content is available via that domain name. You may need to use a host file to test this. Your new domain name would use the same IP address as the old site. Apache and IIS, as well as others, examine the request packet to know which site a request is addressed for so this should work okay. Here is where ...


1

What you want is not possible. I'm assuming you're wanting to use a web browser to navigate to some file. The main problem is that an IP address represents a computer on a network (more specifically, a single network connection, of which there could be many of in a single server), and not a file. That said: if what you're wanting is for some user to type ...


1

Frames! You can search for a free host (such as 000webhost, HostYD or Hostinger) and create a page with the following content: <iframe src="https://dl.dropboxusercontent.com/u/user_nubmer/folder_name/index.html" style="position:fixed; top:0px; left:0px; bottom:0px; right:0px; width:100%; height:100%; border:none; margin:0; padding:0; overflow:hidden; ...


1

If the domain's contact details held by the registrar are accurate/verified and the domain owner is reachable by the registrar, but they do not respond to your complaint, there is not really anything further you can do in terms of direct contact with either the registrar or registrant since both parties are now aware but not interested in helping. If you can ...


2

You are in a tough spot. It is the responsibility of the registrar to pass all complaints to the domain owner. GoDaddy can contact me a variety of ways and has. A real e-mail, mailing address, and phone number has to be provided for private registration. And before the domain can go private, the registration information must be verified. But not all ...


1

I believe the EasyPHP "bundle" uses the Apache web server... in which case you need to either update httpd.conf (the main server config) and set the DocumentRoot and ServerName directives to the appropriate path and domain name, or set up a VirtualHost (preferred) in httpd-vhosts.conf, which will enable you to set up multiple sites. Restart Apache after ...


1

It requires two things; Add a file called CNAME at the root of the project which only contains the domain name, see the docs In your DNS server, add an entry. This is done at your domain name service provider, or named/bind zone file Follow the instructions on setting up a custom domain with GitHub pages


1

It's not strictly a DNS setting. You would have to change the settings on your web server. You will need to have the friendsmusic.com DNS A record point to the IP Address that mydomain.com/friend is hosted at. Then assuming you are using an Apache web server you can go into the configuration file example: /etc/apache2/apache2.conf and create a mod_rewrite ...


1

The only solution I can think of here is a server alias. A server alias points to your domain name on web server level. It can send the user somewhere without the URL changing But you must note: the domain should be hosted at your hosting company you should redirect all links to example.php/. Note the /, otherwise the real URL will be shown. It's a ...


0

Leave it 24 hours from when they fixed the NS issue as it can take a fair while to propagate to all name servers internet-wide. If your still having problems then use NSLOOKUP to query it from a number of different servers. Say for example your Internode Name Servers then say the Telstra ones and maybe a root server or 2 for good measure and make sure they ...


0

It's so they know who actually administers to the site. In the event someone compromises a website theres someone at least kinda accountable.


1

You need to set up a redirect from http://mywebsite.com/<whatever> to https://mywebsite.com/<whatever>. It's not a DNS issue at all, and how to do it is entirely dependent on exactly what web server software you're using and how it's configured. For example, if you use Apache you can create an .htaccess file in the root directory of your ...


4

The email address is part of the SOA record. It's second value is the email address of the administrator. As a minimum, the zone file must specify the Start of Authority (SOA) record with the name of the authoritative master name server for the zone and the email address of someone responsible for management of the name server. The email address in the ...


0

Without having to specify a domain in the circumstance that multiple domains point to the website root or that a production .htaccess rules can be applied to: RewriteCond %{HTTP_HOST} ^(.*)\.ANYdomain\.com [NC]


1

Personally, I would point the A record to the same server. No need to touch the CNAME (in this case, or indeed, many cases). Very simply: CNAME is basically an alias, a forwarder. So, a request comes in to the registrar, hits the CNAME which looks up the relevant A record. Now a days, we just create more A records so we can avoid the CNAME look up, the ...


1

From a SEO standpoint, running the same site on 2 different domains will not give you any potential advantage, Google avoids indexing copies of web pages. In fact, potential duplication issues might lead to penalties like Google Panda update. On the other hand, if you would like users typing in example.net to reach the same site, you might want to do a ...


0

Under normal circumstances, any domain name, regardless of what you do with it, should have an A record that ties the domain name to an IP address. Do not try and use a CNAME for this. Any sub-domain, and www is a sub-domain, should have an CNAME pointing to the parent domain or optionally an A record just like the parent domain. Using a CNAME is traditional ...


1

A CNAME is basically an alias to another DNS record. A not uncommon setup is something like this: example.com A xxx.xxx.xxx.xxx www.example.com CNAME example.com If someone hits www.example.com and the DNS result isn't cached, resolution of a setup like this is very slightly slower, since two DNS lookups are required (one for ...


0

You can only do this from DNS with a subdomain, not with subfolders. For subfolders, you need to do a proxy-pass - here's how it's done in Apache (version 2.4 and above): ProxyRequests Off ProxyPass /subfolder/ http://otherdomain.com/ ProxyPassReverse /subfolder/ http://otherdomain.com/ <Location /subfolder/> ProxyHTMLEnable On ProxyHTMLURLMap ...


2

This definitely can't be done with DNS. I think the real question you want to solve is "How do I allow cross-domain PHP and fonts?" To enable cross-domain PHP and font files (this is probably all you need) you would add the 'Access-Control-Allow-Origin' header to domain2's configuration, like so Apache: Header add Access-Control-Allow-Origin ...


0

This cannot be done via DNS. You either need to do it at the web server level (.htacess apache / rewrite rules IIS), or via a script that runs ASP.net, PHP, Perl etc. Essentially you need to change the response header to moved, and dns cannot do that.


1

I found the solution by going to the old portal. The correct CNAME is awverify.beta.myapp.com => awverify.myapp-beta.azurewebsites.net.


0

http://www.w3schools.com/html/html_urlencode.asp The domain = w3schools.com www is the host. The path is /html/ And the file is html_urlencode.asp



Top 50 recent answers are included