When I'm accessing any host via IP address, it is showing SSL error.
Example.com => 192.168.1.1 (IP address)
Suppose if I want to access https://example.com, it works fine.
If on the other hand, accessing the hosts by its IP address like https://192.168.1.1, it shows SSL Error.
Is there any configuration missing here. Do I need to add the IP address in SAN configuration?
If you want to access a web site by IP address you need to first configure your web server to actually provide this web site on this IP address and then you have to include the IP address as SAN into the certificate served at this IP address. Note that there are different types of SAN: DNSName and IPAddress. The correct type would be IPAddress but some clients actually wrongly expect type DNSName - so you better add the IP address with both SAN types.
Related
I use an application the makes calls to apps reunning on other servers. I would like to get the IP address of one of those servers and the source page doesn't reference either the called URL or IP address.
My idea is to ping the currect page to get the server IP address.
I have built a FreeIPA nameserver that is accessible from within my internal network, however I am unable to get this working for external traffic.
My domain name server setting has been updated with my domain registrar to use my name server. The domain algobuilder.co.uk is set to use nameserver ns1.algobuilder.co.uk and my public static ip address (31.125.181.141). A simple ping from outside my network confirms that algobuilder.co.uk is resolving to my public static IP address.
It appears that external traffic is not using the nameserver ns1.algobuilder.co.uk to resolve to my nameserver. I have opened port 53 on my router and forwarded it to the internal ip address of my nameserver.
I need CertBot to be able to access my nameserver txt records, but it doesn't seem to be able to find them.
Any clues to what I am doing wrong. Thank you.
There was some public dns server that creates dns records on the fly, for example 127.0.0.1.something.com that resolves to 127.0.0.1, I searched a lot on Google but I can't find it. Any idea?
xip.io is gone as of June 2021.
http://nip.io is a working alternative. It works in a similar fashion to xip, so the information below is still valid (changing any references from xip.io to nip.io).
$ nslookup asdf.10.0.0.1.nip.io
Server: 127.0.0.53
Address: 127.0.0.53#53
Non-authoritative answer:
Name: asdf.10.0.0.1.nip.io
Address: 10.0.0.1
Original answer:
You are talking about http://xip.io/
What is xip.io?
xip.io is a magic domain name that provides wildcard DNS
for any IP address. Say your LAN IP address is 10.0.0.1.
Using xip.io,
10.0.0.1.xip.io resolves to 10.0.0.1
www.10.0.0.1.xip.io resolves to 10.0.0.1
mysite.10.0.0.1.xip.io resolves to 10.0.0.1
foo.bar.10.0.0.1.xip.io resolves to 10.0.0.1
...and so on. You can use these domains to access virtual
hosts on your development web server from devices on your
local network, like iPads, iPhones, and other computers.
No configuration required!
How does it work?
xip.io runs a custom DNS server on the public Internet.
When your computer looks up a xip.io domain, the xip.io
DNS server extracts the IP address from the domain and
sends it back in the response.
127.0.0.1 is loopback address, it is like localhost, always is your pc but that is not in a dns server.
If you want your pc accessible from internet and don't pay for a dns addres use dyndns or no-ip
the best part of this sites are that no mind if you have a dynamic ip they always point to your pc
I have Static IP, i would like to access website using static IP as well using domain name.
I have below DNS entries to for my domain, i am not sure what setup i need to do to make it works.
when user access my site using domain name they should be able to access. Also when someone want to access using IP address they should be able to do that.
www 14400 IN CNAME example.com
example.com 14400 IN A 50.63.147.111
If anybody have idea please let me know.
Thank you
Regards,
Mona
If you can't access your IP address, then it isn't because of your DNS. DNS stands for domain name system and translates domain names TO IP addresses. Thus, you must already have a reachable IP address for your A record to be meaningful. Make sure that you've configured your server correctly (Apache?) and that the necessary ports are open in your firewall (iptables).
Check that your domain registrar is pointing its name servers to the authoritative name server (the server with your zone file) for your domain.
I am unsure Whether both DNS server and Host file are the same or different.
I Hosted an application in IIS and created A host name as website1.domain.com and tried to browse it and it didn't work.
When searching on net i found that we need to make entry in DNS server or Host file.
As in most of the sites that I saw mentioned DNS server or host file. I am unsure Whether the both are same or they both are different.
A hosts file is used by Operating Systems to manually specify the IP addresses for specific domains/subdomains - think of it as an override.
DNS however is a server - think of it as a registry - that keeps track of records pertaining to domains, such as A records, MX records etc.
For the purposes of a local test site, an entry in your hosts file would be sufficient, however for a live site, a DNS entry relating to the domain you wish to have your site hosted on would be required.
Choosing which to use comes down to a few things. Does the server upon which your hosting the site use its own DNS server, i.e. a DNS server on the same network, which the connections to the server will be using as well? Does the domain name the site uses have its nameserver set to one that is externally available (i.e. 123-reg.co.uk). If either of these cases are true, you could probably use a DNS server.
If not, is the server hosting the site running on the same machine as the client that will be viewing the site? If so, you can probably use a hosts file, pointing your domains to the localhost IP of 127.0.0.1, ensuring the domains match the bindings in IIS.
Dns server is a server that will help to resolve dns names. ie when you type google.com in your browser , the name will be passed to the dns server provided by your isp. then it will be resolved to ip address by the dns server and your request will be routed to the google ip address by isp network. host file is different one. if you add www.mydomian.com entry in your host file and map it to an ip address 192.168.0.1 then your computer will check ion your host file when you type www.mydomain.com, whether there is any entry for mydomain.com in your host file, and if exists it will be routed to that ip address. in case if there is dns server and you set that server ip in your hnetwork configuration in your pc, then all the domain name request will be sent to that dns server(if there is no host entry exists)