I have a unit file and I want to modify some of the properties. I've been able to extend all the properties using the `/etc/systemd/system/unitname.service.d/` directory but cannot get the `WantedBy` property to be extended.

**Original Unit File (deluged.service)**

```
[Unit]
Description=Deluge Bittorrent Client Daemon
Wants=network-online.target
After=network-online.target

[Service]
Type=simple
User=media
Group=media
ExecStart=/usr/local/bin/deluged -d -u 0.0.0.0

[Install]
WantedBy=multi-user.target

```

**/etc/systemd/system/deluged.service.d/override.conf**

```
[Unit]
BindTo=sys-subsystem-net-devices-tun0.device
After=sys-subsystem-net-devices-tun0.device

[Service]
ExecStart=
ExecStart=/usr/local/bin/deluged -d -i 10.10.10.1 -u 0.0.0.0

[Install]
WantedBy=
WantedBy=sys-subsystem-net-devices-tun0.device

```

Everything appears to work correctly except for `WantedBy` when I run `systemctl enable deluged` it still created the symlink in `multi-user` and no link is created in the new location.

I've searched for documentation on extending/overriding and I haven't seen anything talking about `WantedBy` so I have no idea if it's even possible to extend it. Am I doing something wrong or is it just not possible?
['https://serverfault.com/questions/865931', 'https://serverfault.com', 'https://serverfault.com/users/239459/']
A lot of things are going wrong here. Firstly, your DNS servers don't seem to be set up right:

```
[me@risby ~]$ dig soa hostthrone.com @169.239.180.241
[...]
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1680
;; QUESTION SECTION:
;hostthrone.com.                        IN      SOA
[...]
[me@risby ~]$ dig soa hostthrone.com @169.239.181.204
[...]
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1680
;; QUESTION SECTION:
;hostthrone.com.                        IN      SOA

```

But your single biggest problem is that you haven't set the domain up with your registrar properly:

```
[me@risby ~]$ whois hostthrone.com
[Querying whois.verisign-grs.com]
[Redirected to whois.namecheap.com]
[Querying whois.namecheap.com]
[whois.namecheap.com]
Domain name: hostthrone.com
[...]
Name Server: dns1.registrar-servers.com
Name Server: dns2.registrar-servers.com

```

Whilst it is perfectly legitimate to have a domain use nameservers inside itself - that's what [glue records](https://en.wikipedia.org/wiki/Glue_records) were invented for - each registrar has a slightly different procedure for setting this up, and you have not done yours. That means your registrar is not telling the internet that your servers are authoritative for your domain, so even if they were working, the domain would not be served properly.

Thank you for not obscuring your domain name and IP addresses; that makes the question much easier to answer.
After following MadHatter answer I solved the whois hostthrone.com by using these namecheap settings :

[![enter image description here](https://i.stack.imgur.com/BvOas.png)](https://i.stack.imgur.com/BvOas.png)

My DNS server would only work for period of time after setting up hostthrone.com zone in PowerDNS 

[![enter image description here](https://i.stack.imgur.com/QhbTp.png)](https://i.stack.imgur.com/QhbTp.png)

After a lot of googling the real problem was that that Ubuntu was installing an alpha version of PowerDNS

Here is the solution :

```
sudo nano /etc/apt/sources.list.d/pdns.list

deb [arch=amd64] http://repo.powerdns.com/ubuntu xenial-auth-40 main

sudo nano /etc/apt/preferences.d/pdns

Package: pdns-*
Pin: origin repo.powerdns.com
Pin-Priority: 600

curl https://repo.powerdns.com/FD380FBB-pub.asc | sudo apt-key add - && sudo apt-get update && sudo apt-get install pdns-server

```

If you have an error of this nature RestrictAddressFamilies=AF\_UNIX AF\_INET AF\_INET6 then edit /lib/systemd/system/pdns.service

```
#RestrictAddressFamilies=AF_UNIX AF_INET AF_INET6

```

Install pdns-backend-mysql

```
sudo apt-get install pdns-backend-mysql
service pdns restart
netstat -tap | grep pdns

tcp        0      0 *:domain                *:*                     LISTEN                                                             1145/pdns_server-in
tcp6       0      0 [::]:domain             [::]:*                  LISTEN                                                             1145/pdns_server-in

```

dig hostthrone.com SOA @169.239.181.204 returns an answer still after a few days