dnsmasq redirection config rewrite to systemd-networkd configuration
Clash Royale CLAN TAG#URR8PPP
up vote
0
down vote
favorite
I updated my Ubuntu 16.04LTS to 18.04LTS, first I noticed that systemd-networkd is colliding with dnsmasq because it's using the port 53. After some research, I learned that the systemd-networkd is a system daemon that manages network configurations. Of course, I want to solve my problem with the native tools that come with the distro, therefore, I wanted to configure systemd-networkd to do the same thing my dnsmasq did, redirecting DNS queries to a specific name server.
For example, the configuration I was using in dnsmasq for redirecting all the request that came on 'intranet' were going over the '10.17.1.1' name server:
server=/intranet/10.17.1.1
I was trying to do something similar with the network configuration in systemd-networkd with the options "DNS" for the DNS server and "Domains" for the domain I want to resolve over the name server:
[Match]
Name=test
[Network]
DNS=10.17.1.1
Domains= ~intranet
I am not sure if its possible to actually do something like that in systemd-networkd and after reading the documentation and playing around with it I didn't come up with any solution, could someone help me with an example?
configuration dnsmasq systemd-networkd
add a comment |Â
up vote
0
down vote
favorite
I updated my Ubuntu 16.04LTS to 18.04LTS, first I noticed that systemd-networkd is colliding with dnsmasq because it's using the port 53. After some research, I learned that the systemd-networkd is a system daemon that manages network configurations. Of course, I want to solve my problem with the native tools that come with the distro, therefore, I wanted to configure systemd-networkd to do the same thing my dnsmasq did, redirecting DNS queries to a specific name server.
For example, the configuration I was using in dnsmasq for redirecting all the request that came on 'intranet' were going over the '10.17.1.1' name server:
server=/intranet/10.17.1.1
I was trying to do something similar with the network configuration in systemd-networkd with the options "DNS" for the DNS server and "Domains" for the domain I want to resolve over the name server:
[Match]
Name=test
[Network]
DNS=10.17.1.1
Domains= ~intranet
I am not sure if its possible to actually do something like that in systemd-networkd and after reading the documentation and playing around with it I didn't come up with any solution, could someone help me with an example?
configuration dnsmasq systemd-networkd
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I updated my Ubuntu 16.04LTS to 18.04LTS, first I noticed that systemd-networkd is colliding with dnsmasq because it's using the port 53. After some research, I learned that the systemd-networkd is a system daemon that manages network configurations. Of course, I want to solve my problem with the native tools that come with the distro, therefore, I wanted to configure systemd-networkd to do the same thing my dnsmasq did, redirecting DNS queries to a specific name server.
For example, the configuration I was using in dnsmasq for redirecting all the request that came on 'intranet' were going over the '10.17.1.1' name server:
server=/intranet/10.17.1.1
I was trying to do something similar with the network configuration in systemd-networkd with the options "DNS" for the DNS server and "Domains" for the domain I want to resolve over the name server:
[Match]
Name=test
[Network]
DNS=10.17.1.1
Domains= ~intranet
I am not sure if its possible to actually do something like that in systemd-networkd and after reading the documentation and playing around with it I didn't come up with any solution, could someone help me with an example?
configuration dnsmasq systemd-networkd
I updated my Ubuntu 16.04LTS to 18.04LTS, first I noticed that systemd-networkd is colliding with dnsmasq because it's using the port 53. After some research, I learned that the systemd-networkd is a system daemon that manages network configurations. Of course, I want to solve my problem with the native tools that come with the distro, therefore, I wanted to configure systemd-networkd to do the same thing my dnsmasq did, redirecting DNS queries to a specific name server.
For example, the configuration I was using in dnsmasq for redirecting all the request that came on 'intranet' were going over the '10.17.1.1' name server:
server=/intranet/10.17.1.1
I was trying to do something similar with the network configuration in systemd-networkd with the options "DNS" for the DNS server and "Domains" for the domain I want to resolve over the name server:
[Match]
Name=test
[Network]
DNS=10.17.1.1
Domains= ~intranet
I am not sure if its possible to actually do something like that in systemd-networkd and after reading the documentation and playing around with it I didn't come up with any solution, could someone help me with an example?
configuration dnsmasq systemd-networkd
edited May 3 at 18:42
asked May 3 at 17:48
mordax
12
12
add a comment |Â
add a comment |Â
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f441623%2fdnsmasq-redirection-config-rewrite-to-systemd-networkd-configuration%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password