fns2 is dead, long live fns2! [2021-06-24]
OVH has finally refused to restore the service under old IP. Since they have not replied
to my questions regarding continued sponsorship, and since they have offered a compensation
voucher for the fire destruction, I have just bought a VPS on my own.
fns2.42.pl has new IPs: 51.38.99.90 & 2001:41d0:701:1100::66c
For most of you, things will just start working as they were before. But there will be
some that will have to fix the IP in various places, e.g.:
- firewalls
- hidden master DNS setup
- DNS server ACLs (allow-transfer, also-notify, etc)
- if you used your own NS name with old IP instead of fns2.42.pl name (update glue as well)
fns1 failure [2021-06-21]
I am very sorry for fns1 problems, they were totally on me this time: have not been tending to it for quite some time, and disks got full with logs. It is fixed now, with extra measures preventing this class of problems in the future.
fns2 failure [2021-03-10]
fns2 is hosted at OVH, unfortunately at SBG2 which was destroyed by the fire.
Awaiting replacements.
CAA records [2017-09-19]
FreeDNS now supports CAA records. You can enable them in user options.
FNS2 IP change [2017-01-23]
New IP for fns2.42.pl is 193.70.13.218 and 2001:41d0:1000:2ada::42
Everything should be working now. Please make necessary changes at your domain providers, ISPs, firewalls, etc.
FNS2 IP change [2016-12-27]
Current benefactor (after some ownership changes) no longer wishes to serve fns2 pro bono.
I am looking for a replacement right now. Please be ready to change the fns2 IP (zones, registrars, ACLs, etc.) by the end of January 2017.
There will be further announcements with details, of course. Stay tuned.
No more NOTIFY for slave zones.
The NOTIFY has been disabled for slave zones.
If you encounter problems with it, please email me.
Dynamic DNS
For automatic records update we use XML RPC; there is a simple
python script for easy IP changes.
It is enough to call the script as
freedns-dyndns.py --newaddress new.ip.add.ress
or even simpler
freedns-dyndns.py --newaddress <dynamic>
to update record to your public IP (watch for proxies!)
You may want
to fix default values in the script itself so you do not have to pass on the
params in the commandline. Old IP can be '*', no need to have it written down.
Another way is to use any dynamic dns service (like DynDNS), and have a CNAME
record pointing there.
Idea
Free DNS service for the self-reliant people who want to experiment on their
own, or keep all their zones in a single place.
We offer primary and secondary name server, automatic reloads every 15 minutes,
SRV, TXT and IPv6 support, and unique feature of web redirections / frames (see our
pseudo-record WWW).
All zones (both primary and secondary) served by primary server
— fns1.42.pl (79.98.145.34) — are automatically replicaated to our
secondary server — fns2.42.pl (193.70.13.218 and 2001:41d0:1000:2ada::42).
If registrar needs personal info and/or zone admin email, it would be yours,
not mine. It will be you maintaining the domain, not me. Do not put me as an
admin of your domain.
Contact me
If you have problems write me at
freedns at 42 pl. Please be patient — this is free service and I answer
questions when I have time.
