Home / user-144967

Arran Cudbard-Bell's questions

Martin Hope
Arran Cudbard-Bell
Asked: 2018-08-21 06:01:50 +0800 CST
  • 0

We have a VPN with multiple search domains. One component of these domains specifies the country in which the hosts are located.

  • servers.fr.internal.example.org. contains all the servers in France.
  • servers.ca.internal.example.org. contains all the servers in Canada.

The configured list of search domains is:

internal.example.org.

I've found multiple references to Partially Qualified Domain Names (PQDNs), but all the examples only show PQDNs as hostnames. I'm wondering if the DNS protocol/most widely deployed resolvers allow for PQDNs with multiple labels, i.e. foo.servers.ca.

I've tried this on my local machine macOS 10.13.6 and it doesn't appear to work, I just get NXDOMAIN.

Should this work? Is there a special format for PQDNs with multiple labels? I understand this works fine on other systems (Linux, Windows).

domain-name-system
Martin Hope
Arran Cudbard-Bell
Asked: 2015-08-13 08:55:45 +0800 CST
  • 1

I'm developing/have developed a unit file for systemd

[Unit]
Description=FreeRADIUS multi-protocol policy server
After=syslog.target network.target
Documentation=man:radiusd(8) man:radiusd.conf(5) http://wiki.freeradius.org/ http://networkradius.com/doc/

[Service]
EnvironmentFile=-/etc/sysconfig/radiusd
ExecStartPre=/usr/sbin/radiusd $FREERADIUS_OPTIONS -Cxm -lstdout
ExecStart=/usr/sbin/radiusd $FREERADIUS_OPTIONS -fm
Restart=on-abnormal

[Install]
WantedBy=multi-user.target

Experiencing an issue where calling systemctl radiusd start does not return an error code, even if /usr/sbin/radiusd -fm exits with one.

Is there a way to make systemctl act synchronously? i.e. waiting for a set period before returning and indicating the service was successfully/unsuccessfully started.

I'm fine with changing to Type=forking or any of the other options, like dbus (and writing the code to integrate with dbus) if that means systemctl will exit with an error indicating that the service failed to start.

To pre-empt the obvious question, yes, after start systemd does see the unit as failed.

bash-4.2# systemctl status radiusd
radiusd.service - FreeRADIUS multi-protocol policy server
   Loaded: loaded (/usr/lib/systemd/system/radiusd.service; enabled)
   Active: failed (Result: start-limit) since Wed 2015-08-12 12:26:18 EDT; 19s ago
     Docs: man:radiusd(8)
           man:radiusd.conf(5)
           http://wiki.freeradius.org/
           http://networkradius.com/doc/
  Process: 10610 ExecStart=/usr/sbin/radiusd $FREERADIUS_OPTIONS -fm (code=exited, status=1/FAILURE)
 Main PID: 10610 (code=exited, status=1/FAILURE)

and yes systemctl status radiusd does return a non 0 exit code. Just annoying to integrate this with salt stack. Currently, without synchronous start, the bundled saltstack pkg module reports the service as running, after applying config/code updates that cause service failures.

systemd