I'm not sure this is even a question to be asked here, but I'll give it a shot anyway.
So I have an ubuntu server, and I recently purchased a domainname.
Now I have forwarded the domain to my IP, but whenever I reach the server, the browser shows the IP adress instead of the domain.
Is this something I should configure in Apache, or from godday (where I got the domainname)
Thanks in advance :)
Start with checking your setup at Godaddy. What you probably need is an A entry.
The good news is that your setup seems to work since you get an answer from you server!
Perhaps this can help
http://support.godaddy.com/help/article/680/managing-dns-for-your-domain-names
Related
I've set up Strongswan VPN with StrongMan(web-interface manager) on AWS.
It works great, my company employees can access contry-restricted site without any issues. But now I need to implement split-tunneling, because we also have to send terabytes of data, daily, to non-restricted sites.
I've coded small C# app that automaticaly manages split-tunneling routes with next command.
route ADD siteIP MASK 255.255.255.255 10.10.10.1 IF VPNInterfaceID
And it doesn't work like i'd like it to work.
Problem is: my DNS are leaking in split-tunnel mode.
If i route to "www.whatismyip.com" thru VPN, it masks my IP, so it works,
but i can't access restricted sites.
So i routed "www.dnsleaktest.com" thru VPN, and i can see that my DNS are in fact leaking.
I've found an app "Simple DNSCrypt", which fixed my problem, but i really dont want to use third-party software.
I'am very new to this topic, so any help would be appreciated.
I cant figure out how to hide my DNS.
Even overriding to 8.8.8.8 and 8.8.4.4 doesnt help.
What can i do? What should i read and learn? What could be the problem?
Sorry for my poor use of English.
Thank you in advance!
I've figured it out. Maybe, this answer will help someone someday.
You have also route DNS adresses thru VPN (in my case 8.8.8.8 and 8.8.4.4),
and "disabling" default ethernet adapter DNS by setting them to 127.0.0.1.
Dont forget to revert them back after disconnecting from VPN!
I am kinda stuck with an usual issue (or is it usual?). Let me explain.
I have two Debian VPS boxes. The first one is a pure VPN (OpenVpn) and the second one is my regular server with emails, websites and all. I also have a machine "at home" that can easily connect to these two boxes.
Now I need to connect like this: my machine at home to -> my VPS that runs VPN only and then to -> my regular VPS server.
I thought it would be easy, but I was mistaken. I allowed my VPN's static IP address through my firewall (iptables) on my regular VPS server but I didn't work. I flushed all the iptables just to see if it helps but.. it still doesn't work (it always times out, I use ssh keys to connect). I can only connect to either my VPS that runs my VPN only or to my regular VPS, but my route of home->VPN->regular VPS just doesn't work. How can I possibly do it? These two VPS boxes are working fine: My VPS with VPN is working perfectly well and my regular VPS is also working perfectly well. I would be really grateful for any pointers / suggestions / advices at all. Many thanks in advance!
Let me answer my own question. Not sure why it works this way but it works. I simply allowed "password logins" and it all started working perfectly well. It connects using ssh keys anyway without any password prompts but.. nonetheless allowing password logins in ssh solved the issue (I had it turned off earlier). Hope it will help someone too.
I have a bit of a problem. I setup several new domains on VestaCP, but they all point to the same default website. Part of the problem I guess is that all DNS records point to the same IP, but Vesta doesn't seem to know which website to take you to, so it takes you to a default website.
However, this problem only happens with HTTP, HTTPS forwards to the correct website. I don't know why. Is there a .conf somewhere that needs to be edited, or am I doing something wrong in VestaCP?
My setup is running on Digital Ocean -- Ubuntu 18.04, Nginx + php-fpm
Your help appreciated.
Chceck if all DNS goes to IP of server with VestaCP. If yes, try look into /home/yourloginname/web Is there every your website? If yes, try to look to aliases. If you have subdomains, maybe head domain have alias *.domain.com .
And if your answer was no for some of questions above, try look into /etc/bind/named.conf where should have every domain 1 row for example:
zone "domain.eu" {type master; file "/home/admin/conf/dns/domain.eu.db";};
If not, add this one. Hope will be helpful.
I have an application stored in a hosting that has Cloudflare's protection. The application in the client's side, from javascript does an ajax request to the page http://ipinfo.io and get the ip, location and some information of the visitor. Nevertheless the result is similar to:
IP: 141.101.75.82
Hostname: No Hostname
ISP: AS13335 CloudFlare, Inc.
Since you will see, the information does not belong to the visitor, the information is of Cloudflare.
Someone knows how this problem can be solved?
Sorry for orthographic failures, regards.
Thanks for reply but I've solved it. I disabled this option:
Regards.
Have you installed something like mod_cloudflare to restore the original visitor IP? That should work.
At time of writing, the connecting IP can be found in the 'HTTP_CF_CONNECTING_IP' header
I have installed WordPress on a subdomain that currently resides on an unpropogated domain. (It can only be accessed via IP address.) Is it possible for me to access any subdomains that have been created, eg: subdomain.mysite.com/wp-admin via IP, or do I have to wait till the domain has been propogated?
This is my first question, I apoligize if I have not explained my self thoroughly enough. Thanks in advance for any help.
you can use http://[IP]/~[username]/[domain.tld]/ to access your site by IP.
Where [IP] is the IP of your server and [username] is your username for the hosting site. [domain.tld] is the name of the folder on which you have mapped your subdomain.
You may be able to check it with an anonymous proxy?
I use http://anonymouse.org/anonwww.html to check sites as in Australia it normally takes a little longer to propagate over to here.
Please note: You will only be able to check it's existence, you would not use this to make site modifications through the back end. That would best be done once the domain propagates.
Hope this helps ;)