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.
Related
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.
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 trying to set up my own nameserver on hp cloud VPS for the domain "appwared.com".
I added ns1.appwared.com from my registrar control panel to point to my server's public ip address.
I installed NSD3 as my DNS software and configured the zone files. It is up and running but as you may see, the domain is not resolving.
here you can see the zone file: http://pastebin.com/z0094kja
This is my first attempt to set up my own Name Server, maybe you can peoint out what I am doing wrong.
Thanks!
HP was blocking the UDP 53 port that used in DNS.
I have a mail server running on a linux server.
Internally, I can access it via https://192.168.0.253/webaccess and externally I can access it via https://webmail.mydomain.com/webaccess
I'd like to be able to access webmail.mydomain.com internally, the problem is that a DNS lookup to this address goes to the public IP of our network and from within, that won't work.
I have bind9 installed on our linux server (internal) and can use that for DNS lookups - that server is my primary DNS address. Could anyone please describe how I can configure bind to resolve webmail.mydomain.com to 192.168.0.253?
Configure Bind to use a different view for the internal users; see http://www.cyberciti.biz/faq/linux-unix-bind9-named-configure-views/
in /etc/hosts (or equivalent for the OS) on the client you can set webmail.mydomain.com to 192.168.0.253, as the hosts file is checked before any DNS servers.