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
Related
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.
I was wondering if someone can answer this question. I have already searched everywhere and couldn't find the answer anywhere, some of you might have already implemented this solution.
Here is what I have on my home network:
Software used: bind9 on Ubuntu 18.04
Home/Cloud DNS Server: xyz.com ( in a master / slave configuration : 2 servers using internal IP addresses 192.168.1.10 (master) , 192.168.1.11 (slave) )
On my namecheap account: I purchased a domain (xyz.com) , added A+ Dynamic DNS record pointing to my IP address provided by ISP, it is also updated using ddclient. I also have several subdomain under xyz.com such as : a11.xyz.com , a12.xyz.com, a13.xyz.com and so on.
On my primary DNS server at home:
└─<>──» nslookup xyz.com 0 < 10:25:03
Server: 192.168.1.10
Address: 192.168.1.10#53
Name: xyz.com
Address: 192.168.1.10
But, if you look for a11.xyz.com - I want this to search locally first and then look externally for the DNS records on public DNS servers such as Google, Namecheap and others.
Server: 192.168.1.10
Address: 192.168.1.10#53
** server can't find a11.xyz.com: NXDOMAIN
Now, question is:
Q1. ) Is it possible to have such a configuration at home wherein home DNS server domain name is same as the one purchased at registrars like Namecheap and Godaddy ?
Q2. ) If internal domains are same as external domain names, can this mix be handled such that it will search locally first and then look outside for any records in the public dns servers.
Q3. ) if nslookup / dig response depends on the client configuration, Can the home DNS servers serve both bogus domains and real domains purchased ?
I haven't seen such a documentation on digital ocean or any other cloud providers.
Thanks again for the help.
I solved the problem by isolating internal domains from external domains. In the example above, if I have a domain on namecheap/godaddy as : xyz.com then same domain name CANNOT be used internally for home network since there will conflict in resolution so,
I created a domain specifically for internal device lookups : homelan.com and all devices inside the home network will have default domain homelan.com. This way, all subdomains of xyz.com can also resolve using forwarders as well as internal devices using homelan.com.
I was under the impression that if both external and internal domains are same, then bind will automatically resolve to external domains if it cannot find a record internally.
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.
I have the IP address of the DNS server from the WebHost. Since we do not own the Domain Name (Its the client's DN) I would like to query the WebHost DNS directly to see if it works before asking the client to point his DN to the WebHost DNS.
Am I missing something here? I'm kinda confused when it comes to configures online services.
From Windows Command Prompt:
nslookup
server x.x.x.x (put the WebHost DNS IP address there)
www.yourdomain.com (type the name of the domain you want resolved)
quit
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.