Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 7 years ago.
Improve this question
I resigstered a new domain visitsoonvalley.com but now I can see that there is a sub-domain support.visitsoonvalley.com which I didn't create and I can't find in the cpanel too. This page is showing ads and the first advertisement is of the company that I registered my domain with. Is it possible that they created this sub domain? Are they allowed to do this without notifying me?
UPDATE: I just checked going to help.visitsoonvalley.com and same result. Why are these sub domains existing?!
You cannot register subdomains. You cannot really create them. You can only use them.
Most likely there is a "wildcard DNS resolution" for your domain. That would be something your provider has done and it actually does make some sense, since most people want that. Why don't you simply ask them? They will probably remove it from your DNS settings if you ask them.
A "wildcard DNS resolution" means that all DNS resolution requests to hostnames within your domain are resolved to the same IP address, without any specific rule existing. So it is a kind of "fallback".
Why there are ads shown in your page is nothing we can say. Might be some default content your provider puts in as a placeholder until you create content. Or they simply created a DNS resolution as a palceholder until you name an IP address the domain should be resolved to. Again: why don't you ask your provider? You pay them for their service, so usually that means the have to give support...
Certainly that is not exactly a "nice" behavior if that really is not mentioned anywhere in their policy. But on the other hand it does no harm and is only temporary...
Related
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 1 year ago.
Improve this question
This is a security question regarding a URL
If I have this URL https://www.wikipedia.org and I place an # symbol on the end of the URL followed by a domain like so https://www.wikipedia.org#google.com why does this redirect me to google.com and not just fail. This is a major security risk as people can be redirected to alternative URL's. Can anyone please explain why this is a feature in Google Chrome?
The # symbol in a URL is used to specify authentication details, as per RFC 3986 Section 3.2.1. Usually, you'd see it appear similar to http://username:password#domain.com to pass username and password to a domain.
In your example, the www.wikipedia.org (before the # symbol) would be sent in the HTTP Authorization header to sites expecting it. It isn't redirecting to another domain. It's sending the part before the # symbol to the stated domain (in your case, google.com).
This is perfectly valid per the HTTP specification. This doesn't really present a particular security risk, since the full domain is visible to the user before they submit the request. It's not injected or added without the user's knowledge. This would be no more of a security risk than if someone decided to create a multi-level subdomain on their site like http://wikipedia.com.someothersite.com. Deceptive maybe, but no more of a security risk than the inherent risk in using the internet.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 3 years ago.
Improve this question
I am taking over a wordpress site for a company. They don't know who is currently hosting their wordpress site, all they have is the domain name hoster and the wordpress site admin login info.
You need to check the DNS the domain name is pointed to. You may check the nameservers (=DNS) in public Whois database: https://www.whois.net/
Also, this resourse should help: http://www.whoishostingthis.com/
I have used quite a few, but depending on the database they work with, some deliver wrong info. The best one currently is Hosting Checker and Who Is Hosting This comes second.
see this website http://www.whoishostingthis.com/ It worked for me
It sounds to me like you already know who hosts the domain, you're just looking to find out where the actual files are being served from. If that's correct, you should try:
ping theirdomain.tld
When you ping the domain, it will give you the IP address where the files are hosted. You can plug that IP address back into whois, you'll find out who actually owns that IP address.
For example, if I want to find out where my company's website is located, I would do:
ping 0708scompany.tld
copy the ip address.
whois ip.address.from.ping
You can use the whois yourdomain.com and it should give you the relevant information. It will provide you with the DNS, who the domain name is registered with, and a whole lot more.
You can use whois. Just google whois and you can figure out how. If you have it installed, type whois domain.com in a terminal. You could also use whois.icann.org or other whois sites.
whois tells name, address, and other things. You can use it on any site, so it is indeed very useful.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 8 years ago.
Improve this question
An 101 question about whireshark:
I first flushed my DNS and then started capturing my interface with wireshark.
Then I opened google chrome and searched for a webpage.
Finally, wireshark except the first query about the url makes some additional queries for related names/urls.
for example :
Searched for www.aueb.gr and dns makes an additional query for art.aub.gr.
Why is this happening?
Thank you in advance.
Try using console application for DNS resolution (for example nslookup) during wireshark capture, it should give you exactly what you want. Web browsers or other applications can try to resolve some additional DNS entries, which may be the cause of the issue you are seeing.
For example:
nslookup www.aueb.gr
As for the behavior of chrome, web browsers will try to fetch additional resources (like images, cascading style sheets, scripts) in order to be able to display the web page correctly. If it happens that the resource is hosted in some other domain (like art.aueb.gr), the web browser will have to first resolve that domain name - and that is why you see additional DNS queries.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
Closed 8 years ago.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
This question appears to be off-topic because it lacks sufficient information to diagnose the problem. Describe your problem in more detail or include a minimal example in the question itself.
Improve this question
A novice here. The support from mediaTemple and my current host have been quite unhelpful, so stackOverflow may be my hero.
My problem is that entering "www" before the domain and leaving it out direct to different servers.
The background on this is that I first registered the domain with mediaTemple and had a plan with their gridHosting, but after finding their service unsatisfactory, I cancelled my gridhosting plan and moved to another host. This problem occurs even after updating the nameservers. In short, the web server is hosted by proMinecraftHost, but the domain is registered under mediaTemple.
Support from both sides say it's due to dns and the nameservers needing 24-48 hours to update, but I'm fairly skeptical that it really is the cause.
Summarizing, www.mscraft.org directs to the correct server, but mscraft.org(mscraft.org) alone does not.
If anyone could help me, I'd greatly appreciate it.
Thanks in advance.
It's possible you just have the old DNS info in your cache. Try clearing your browser's cache, and also flushing your DNS. On Windows you could do ipconfig /flushdns in a command prompt. Also you could try pinging both addresses (with and without www). You should see the same IP address for both, as I got 198.154.108.107 when I tried them. In other words, I think it's working properly - you are just going to the old location because your machine is remembering too much.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 12 years ago.
Improve this question
When one registers for a blog in blogger.com, a sub-domain gets created i.e. your_blog_name.blogger.com
My question is - Is there no limit to the number of sub-domains you can create with a single domain name?
I am just curious as to how blogger (or any other blog hosting platform) does this?
This can be done by a catch-all A record rule in your DNS server configuration. For example, in bind, you would use something like this:
*.example.com. IN A 127.0.0.1
This would make anything.example.com resolve to 127.0.0.1. Then, using an appopriate VHost on your http server, you can redirect all requests to a particular server-side script (for example PHP), which can then detect the hostname that was used, and respond with the content required.
There are restrictions on the characters that can be used (actually, two separate sets of restrictions due to the way IDNs work). There are practical limitations in terms of length. Beyond that no. Indeed, it's not much different for the entity in charge of .blogger.com to create a subdomain of that than for the entity in charge of .com to do so, and there were 80,000,000 of those at the start of last year .