[nsd-users] Building Up DNS server with NSD; Migration
Mukul Shukla
mukulmanet at gmail.com
Mon Jun 7 06:31:41 UTC 2021
Dear All,
It is good you shared some detail.
- I did this because I wanted to be specific in what I expect from
migration to NSD (or any other DNS server for that matter).
DNS has good ways of implementing redundancies and achieving high
availability.
- What are those like?
You can set up new separate servers and test their functionality thoroughly
[like Kaulkwappe described], even before telling any outsider about them.
- I have already setup the new separate servers. But that is exactly the
problem. I want to decide as to whether NSD will serve my needs for a long
run? Is there any other DNS software which is more suitable for us?
I'm just afraid getting the necessary public IP (IPv4) addresses might be
an issue for you - if your organisation really only has 16 -- [1]
- We will work to get an alternate ISP connection with 8 more Public IPs
with it.
One of the important ways towards high availability is to *not* put all the
authoritative name servers in the same place (ie all eggs in the same
basket).
This seems to be the case currently [2].
More elaborate advice is in RFC2182 -- [3].
- Yes, this is the problem with our setup currently. As mentioned above, we
will get an alternate Internet connection with a different ISP so that we
have 8 more Public IPs on the different subnet.
It looks like all current authoritative servers are in direct sequential IP
addresses and one could guess that probably the outage of one router could
cause all of them to become unreachable.
- Yes, that is the case right now. We will sort it out.
- Meantime, we can continue with whatever we have, with high risk of course.
I'd try to get a friendly organisation or your upstream provider to provide
secondary name service for your domain(s). with automatic updates of zone
data / changes from you to that server.
- With more Public IP on a different subnet, I think the above will get
sorted out.
This is of course not what you were asking (how to run *your* servers),
- Obviously not. I said we are running the setup, with all the above
constraints, for past 10 years. Yes there are problems, not that something
serious has happened. We are not running mission critical server back
there. A small amount to downtime is acceptable.
but valid consideration for the person/team responsible for the overall
availability of the domain in DNS.
- Did not get what does that mean. I am only looking for how NSD, and will
it help me, if I replace djbdns with NSD?
But since this is the mailing list for NSD, I should mention that another
mailing list:
https://lists.dns-oarc.net/mailman/listinfo/dns-operations
would be more appropriate for the general DNS questions.
- I want to more of NSD and hence have posted here. But since NSD is a DNS
software, some relevance of DNS and other similar soft wares are bound to
come. Moreover, the general questions will disappear, once I come to know
more about NSD. As I mentioned before, there is no concise manual for
beginners, I have to join the mailing list and post the questions. For the
other softwares, eg. djbdn, I learnt that without even knowing a mailing
list for it exists.
I will be posting some direct questions to know more about NSD and it's
features. By knowing that I want to get a feel as to whether I will be able
to successfully migrate my DNS setup to NSD.
Thanks a lot for the reply.
Mukul
On Mon, Jun 7, 2021 at 2:39 AM Frank Habicht via nsd-users <
nsd-users at lists.nlnetlabs.nl> wrote:
> Hi Mukul,
>
> it is good you shared some detail.
>
> DNS has good ways of implementing redundancies and achieving high
> availability.
>
> You can set up new separate servers and test their functionality
> thoroughly [like Kaulkwappe described], even before telling any outsider
> about them.
> I'm just afraid getting the necessary public IP (IPv4) addresses might
> be an issue for you - if your organisation really only has 16 -- [1]
>
> One of the important ways towards high availability is to *not* put all
> the authoritative name servers in the same place (ie all eggs in the
> same basket).
> This seems to be the case currently [2].
> More elaborate advise is in RFC2182 -- [3].
>
> It looks like all current authoritative servers are in direct sequential
> IP addresses and one could guess that probably the outage of one router
> could cause all of them to become unreachable.
> I'd try to get a friendly organisation or your upstream provider to
> provide secondary name service for your domain(s). with automatic
> updates of zone data / changes from you to that server.
>
> This is of course not what you were asking (how to run *your* servers),
> but valid consideration for the person/team responsible for the overall
> availability of the domain in DNS.
>
> But since this is the mailing list for NSD, I should mention that
> another mailing list:
> https://lists.dns-oarc.net/mailman/listinfo/dns-operations
> would be more appropriate for the general DNS questions.
>
> Regards,
> Frank
>
> [1]
> inetnum: 14.139.250.80 - 14.139.250.95
>
> [2]
> dig sgsits.ac.in. ns
>
> [3]
> https://datatracker.ietf.org/doc/html/rfc2182
>
>
>
> On 06/06/2021 22:16, Mukul Shukla via nsd-users wrote:
> > Dear All,
> >
> > Let me give me a little background as to what I am trying to achieve.
> >
> > 1. The domain which I want the Authoritative Name serve to serve for is
> > sgsits.ac.in <http://sgsits.ac.in>.
> > 2. The ERNET India (ac.in <http://ac.in>) is the domain name registrar
> > for academic institutes here in India.
> > 3. We are hosting our Website, Email and Moodle servers for which right
> > now djbdns is acting as a authoritative name server.
> > 4. Although, djbdns is working fine since last ten years (I must say its
> > a brilliantly crafted DNS server), it lacks some security features
> > which are now a must (eg. DNSSEC).
> > 5. I want to migrate this name server to NSD, with al the security
> > feature and high availability so that it meets the current requirements.
> >
> > Can anybody please tell me how to plan for this migration so that I have
> > a minimum downtime. Moreover, I want to build a setup with NSD so that
> > it runs smoothly for the next 10 years. Of course want to know how to
> > keep on upgrading will be an issue, I need to consider.
> >
> > I am reading the only source of information, the man pages on NLNET's
> > website, although there are few tutorial available (eg. Calomel)
> >
> > Thank you all.
> >
> > Mukul
> >
> >
> >
> > On Mon, Jun 7, 2021 at 12:02 AM Mukul Shukla <mukulmanet at gmail.com
> > <mailto:mukulmanet at gmail.com>> wrote:
> >
> > Hi Ondřej,
> >
> > Thanks for such encouraging words.
> > Gave me a lot of confidence.
> > It's decided at my end. I will try to migrate my University DNS
> > authoritative setup to much improved NSD setup, of course with the
> > help of all the members here.
> > Thanks again.
> >
> > Mukul
> >
> > On Sun, Jun 6, 2021 at 10:57 PM Ondřej Surý <ondrej at sury.org
> > <mailto:ondrej at sury.org>> wrote:
> >
> > Hi Mukul,
> >
> > don’t worry - the community here is friendly and helpful and you
> > should not run into any hard problems. Take it as an opportunity
> > to learn something new!
> >
> > Ondřej
> > - former Knot DNS team lead
> > - current BIND 9 team lead
> > --
> > Ondřej Surý <ondrej at sury.org <mailto:ondrej at sury.org>> (He/Him)
> >
> >> On 6. 6. 2021, at 18:50, Mukul Shukla via nsd-users
> >> <nsd-users at lists.nlnetlabs.nl
> >> <mailto:nsd-users at lists.nlnetlabs.nl>> wrote:
> >>
> >>
> >>
> >> Dear All,
> >>
> >> There are very few articles/tutorials on NSD. This is making
> >> me nervous to adapt it for a long use. If I am stuck, there is
> >> no help to refer to. Man pages are just not sufficient for the
> >> people like me who don't have much experience of the system
> >> administration and implementing DNS Authoritative Server in
> >> particular. Other DNS implementations have very good manuals.
> >> The kind of software NSD is, there should have been books
> >> written on them.
> >>
> >> Mukul
> >>
> >> On Sun, Jun 6, 2021 at 9:06 PM Anand Buddhdev via nsd-users
> >> <nsd-users at lists.nlnetlabs.nl
> >> <mailto:nsd-users at lists.nlnetlabs.nl>> wrote:
> >>
> >> On 06/06/2021 16:26, mj via nsd-users wrote:
> >>
> >> Hi MJ,
> >>
> >> > Actually: we are in a similar situation. We're currently
> >> running bind9,
> >> > and were interested in to switching to NSD for the
> >> authorative dns
> >> > services, but it seems that you have to compile newer
> >> releases (with
> >> > security fixes etc) yourself, or there is a repo
> >> somewhere we're missing?
> >> >
> >> > We're on debian 10. It recommended to simply install the
> >> NSD that debian
> >> > comes with, and rely on debian for the security fixes?
> >>
> >> Debian packages are often well behind upstream releases.
> >> For example,
> >> Debian 10 (buster) still has NSD 4.1.26, whereas the
> >> upstream version is
> >> 4.3.6.
> >>
> >> However, for Debian, there's usually a repository called
> >> backports. If
> >> you enable it, you can get newer versions of packages. For
> >> example,
> >> "buster-backports" currently has NSD 4.3.5 in it. You
> >> could also enable
> >> the "experimental" repo and get the latest 4.3.6 release.
> >>
> >> Regards,
> >> Anand
> >> _______________________________________________
> >> nsd-users mailing list
> >> nsd-users at lists.nlnetlabs.nl
> >> <mailto:nsd-users at lists.nlnetlabs.nl>
> >> https://lists.nlnetlabs.nl/mailman/listinfo/nsd-users
> >> <https://lists.nlnetlabs.nl/mailman/listinfo/nsd-users>
> >>
> >> _______________________________________________
> >> nsd-users mailing list
> >> nsd-users at lists.nlnetlabs.nl <mailto:
> nsd-users at lists.nlnetlabs.nl>
> >> https://lists.nlnetlabs.nl/mailman/listinfo/nsd-users
> >> <https://lists.nlnetlabs.nl/mailman/listinfo/nsd-users>
> >
> >
> > _______________________________________________
> > nsd-users mailing list
> > nsd-users at lists.nlnetlabs.nl
> > https://lists.nlnetlabs.nl/mailman/listinfo/nsd-users
> >
> _______________________________________________
> nsd-users mailing list
> nsd-users at lists.nlnetlabs.nl
> https://lists.nlnetlabs.nl/mailman/listinfo/nsd-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.nlnetlabs.nl/pipermail/nsd-users/attachments/20210607/702832ad/attachment-0001.htm>
More information about the nsd-users
mailing list