How to Setup/Configure DNS Server in 12.3

English Network/Internet
#1

I’m running openSUSE 12.3 and I’m trying to get a DNS server set up so I can access my Apache-based intranet using machine names instead of IP addresses, without rummaging around in every hosts file on the network.

But there doesn’t seem to be any straightforward tutorial availalbe. And those that do exist make reference to Yast modules for configuring DNS that I don’t have, and can’t find anywhere.

Pointers to a tutorial specific to openSUSE would be much appreciated. I’ve tried following a few general purpose setup articles, but files are named differently and are put in different locations, and I’d rather not spend a week wading through this.

#2

openSUSE 12.3 is now out of support (End of Life - https://en.opensuse.org/Lifetime) so you should opt to use 13.1 or 13.2 for that task.

The YAST2 module to setup a DNS server is called yast2-dns-server, so; zypper in -y -l yast2-dns-server && yast2 dns-server will get you on the road you want.

#3

Upgrading this machine is not an option.

Downloaded the yast2 module, ran it, watched it fail because - apparently - it doesn’t like NetworkManager.

#4

NM on a fixed system like a BIND server… is not a good idea.

#5

Well, that’s interesting, but it isn’t mentioned anywhere I’ve noticed. And it’s the default when installing openSUSE.

In the past, the default was and ifup-based system, and when I tried changing back to that and get rid of NetworkManager, I wound up having to flush my entire system down the toilet and reinstall it.

This sounds too hard. Too bad; Windows handles this sort of thing right out of the box, transparently.

#6

It isn’t if you do a server setup - ifup / wicked is the default for minimal server installations.

You most likely have run Windows all your life, if you were put in front of one without having any idea what you’re doing how long would it take you to setup a working DHCP / DNS server?

It takes me a few minutes on a Linux system - most of that time goes into inputting the DNS names if the clients don’t autoregister.

#7

Actually, I very rarely run Windows; I’ve been using Linux for about 15 years now, almost exclusively.

It remains a hobbyist’s OS in many regards. Windows, despite it’s many shortcomings, for the most part just works, and does so without any user involvement at all.

Never mind. It’s not a problem important enough for me to waste my time on. I’ve got better things to do than dumpster-dive through the OS.

#8

Just because you do not have the expertise or knowledge to do something does not make something a “hobbyist OS”. On the contrary, the requirement to know more than just waving a mouse to check mark a few buttons is the antitheses of a hobbyist - it means you have a deeper understanding of what makes something tick.

Also next time, install a system with server settings and not desktop - I doubt you’d install DNS on a Windows 7/8.1 box either.

#9

Seems I responded to this exactly same Q less than a week ago in another thread (another Forum?) for running the YAST HTTP Server configuration applet. The answer I gave there applies equally here).
https://forums.opensuse.org/showthread.php/503870-Vnstat-CGI-problem

Just ignore the NM warning and continue…
After making sure your NM is setting a static IP address and not configured to use DHCP.
(Or, configure a DHCP lease which is OK, too)

TSU

#10

On 2015-01-11 21:56, SixDegrees wrote:
>
> Miuku;2688555 Wrote:
>> openSUSE 12.3 is now out of support (End of Life -
>> https://en.opensuse.org/Lifetime) so you should opt to use 13.1 or 13.2
>> for that task.
>>
>> The YAST2 module to setup a DNS server is called yast2-dns-server, so;
>> zypper in -y -l yast2-dns-server && yast2 dns-server will get you on
>> the road you want.
>
> Upgrading this machine is not an option.

Well, you should, because DNS is a vulnerable service and you will not
get security patches.

And you would get an alternative new DNS server, dnsmasq, which is
terribly easy to setup and maintain.

> Downloaded the yast2 module, ran it, watched it fail because -
> apparently - it doesn’t like NetworkManager.

Well, obviously, YaST wants to handle network itself, not via a desktop
applet. Why you use network manager on a server is beyond my understanding.

On 2015-01-11 22:16, SixDegrees wrote:>
> Miuku;2688559 Wrote:
>> NM on a fixed system like a BIND server… is not a good idea.
>
> Well, that’s interesting, but it isn’t mentioned anywhere I’ve noticed.
> And it’s the default when installing openSUSE.

It is the default on machines detected as laptops, not servers.

> This sounds too hard. Too bad; Windows handles this sort of thing right
> out of the box, transparently.

That kind of comment will not get you a lot forward on a Linux forum.

It takes me minutes to setup networking in openSUSE, with a dns server.
Much faster than in Windows. In Windows, for starters, you’d have to buy
a server license, and it takes half an hour or more just to install the
services, even before configuring them. Of course, the integration with
AD is easier.

–
Cheers / Saludos,

Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)

#11

I set up my servers with and without NM.
There should not be an issue either way if you do so correctly according to your requirements.

The only time to strongly consider NM over Wicked (although IMO is not as absolute as before) and earlier “Classic” is when a wireless connection is involved.

IMO,
TSU

#12

On 2015-01-12 20:46, tsu2 wrote:
>
> I set up my servers with and without NM.

Well, yes, the connection can be started on boot.
But you need running the desktop to get access to the applet and
configure it.

And YaST tools have problems accessing that configuration from other
modules, as the OP found.

> The only time to strongly consider NM over Wicked (although IMO is not
> as absolute as before) and earlier “Classic” is when a wireless
> connection is involved.

I don’t know about wicked, but I have configured wifi using traditional
ifup, from YaST. It works fine; the complication is changing the config,
but obviously a server is static :slight_smile:

–
Cheers / Saludos,

Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)

#13

Configuring WiFi networks without NM actually should not be difficult (if you choose to do so).
I’ve written in these forums in the past that for a long time now wpa_supplicant is the foundation utility used to provide all wpa secured functionality… detection, management and security (although passcodes can be stored elsewhere like in kwallet). wpa_supplicant has been so rock-solid reliable for such a long time I’d wonder why anyone would choose some alternative even if the frontend changes (like using wicked).

I haven’t looked at whether wicked can read or understand changes made directly to wpa_supplicant, that’d be an interesting investigation if someone felt the time spent was worthwhile. The alternative could be to just use wpa_supplicant from the command line and forget about any frontend(it’s not that difficult and shortcuts can be created for your favorite configurations).

So, for instance if you’re running NM, you can open up your wpa_supplicant.conf in a text editor and see how your existing wireless networks are defined and stored. Note that even if you store your passwords in something like kwallet, normally the password hash is still there in wpa_supplicant.conf in ascii text. If you are brave enough, you can use the wireless network pattern to define a new wireless network from scratch.

Since most WiFi today is secured by wpa, this should often be sufficient.

But, if you deal with WEP or if you also want a lighter weight way to scan (all wireless networks including WPA) from the command line, you’ll likely want to install iw.

wpa_supplicant should be installed by default on practically all distros including openSUSE
iw is not typically installed by default but should be available in practically all distro repos.

Playing with these two apps can be a fun exercise for an afternoon and could be useful if your frontends don’t work for some reason.

TSU