What is the most authoritative file/process for managing IP addresses on an 18.04 server?
The 18.04 server installation process creates /etc/cloud/cloud.cfg.d/50-curtin-networking.cfg, which, in turn, seems to generate /etc/netplan/50-cloud-init.yaml. I can't seem to find exactly how 50-cloud-init.yaml gets generated from 50-curtin-networking.cfg though.
What is the recommended way to manage IP addresses on an 18.04 server? Edit 50-curtin-networking.cfg, and then run some command (?) to update 50-cloud-init.yaml? Or some other process?
networking 18.04 ip-address netplan cloud-init
add a comment |
The 18.04 server installation process creates /etc/cloud/cloud.cfg.d/50-curtin-networking.cfg, which, in turn, seems to generate /etc/netplan/50-cloud-init.yaml. I can't seem to find exactly how 50-cloud-init.yaml gets generated from 50-curtin-networking.cfg though.
What is the recommended way to manage IP addresses on an 18.04 server? Edit 50-curtin-networking.cfg, and then run some command (?) to update 50-cloud-init.yaml? Or some other process?
networking 18.04 ip-address netplan cloud-init
network-configgenerates50-cloud-init.cfg. andcloud-init( cloudinit.readthedocs.io/en/latest ) triggersnetwork-config( cloudinit.readthedocs.io/en/latest/topics/network-config.html ). That happens on initial creation, and on restarting but only when your force it.
– Rinzwind
May 23 '18 at 14:00
I don't have any files named50-cloud-init.cfg-- I have50-curtin-networking.cfgand50-cloud-init-yaml. Did you mean the former? If so, how exactly do you "force" cloud-init to regenerate50-cloud-init.yamlfrom50-curtin-networking.cfg?
– kartik_subbarao
May 23 '18 at 15:18
add a comment |
The 18.04 server installation process creates /etc/cloud/cloud.cfg.d/50-curtin-networking.cfg, which, in turn, seems to generate /etc/netplan/50-cloud-init.yaml. I can't seem to find exactly how 50-cloud-init.yaml gets generated from 50-curtin-networking.cfg though.
What is the recommended way to manage IP addresses on an 18.04 server? Edit 50-curtin-networking.cfg, and then run some command (?) to update 50-cloud-init.yaml? Or some other process?
networking 18.04 ip-address netplan cloud-init
The 18.04 server installation process creates /etc/cloud/cloud.cfg.d/50-curtin-networking.cfg, which, in turn, seems to generate /etc/netplan/50-cloud-init.yaml. I can't seem to find exactly how 50-cloud-init.yaml gets generated from 50-curtin-networking.cfg though.
What is the recommended way to manage IP addresses on an 18.04 server? Edit 50-curtin-networking.cfg, and then run some command (?) to update 50-cloud-init.yaml? Or some other process?
networking 18.04 ip-address netplan cloud-init
networking 18.04 ip-address netplan cloud-init
edited May 23 '18 at 12:46
Melebius
4,57651839
4,57651839
asked May 14 '18 at 20:20
kartik_subbaraokartik_subbarao
1418
1418
network-configgenerates50-cloud-init.cfg. andcloud-init( cloudinit.readthedocs.io/en/latest ) triggersnetwork-config( cloudinit.readthedocs.io/en/latest/topics/network-config.html ). That happens on initial creation, and on restarting but only when your force it.
– Rinzwind
May 23 '18 at 14:00
I don't have any files named50-cloud-init.cfg-- I have50-curtin-networking.cfgand50-cloud-init-yaml. Did you mean the former? If so, how exactly do you "force" cloud-init to regenerate50-cloud-init.yamlfrom50-curtin-networking.cfg?
– kartik_subbarao
May 23 '18 at 15:18
add a comment |
network-configgenerates50-cloud-init.cfg. andcloud-init( cloudinit.readthedocs.io/en/latest ) triggersnetwork-config( cloudinit.readthedocs.io/en/latest/topics/network-config.html ). That happens on initial creation, and on restarting but only when your force it.
– Rinzwind
May 23 '18 at 14:00
I don't have any files named50-cloud-init.cfg-- I have50-curtin-networking.cfgand50-cloud-init-yaml. Did you mean the former? If so, how exactly do you "force" cloud-init to regenerate50-cloud-init.yamlfrom50-curtin-networking.cfg?
– kartik_subbarao
May 23 '18 at 15:18
network-config generates 50-cloud-init.cfg. and cloud-init ( cloudinit.readthedocs.io/en/latest ) triggers network-config ( cloudinit.readthedocs.io/en/latest/topics/network-config.html ). That happens on initial creation, and on restarting but only when your force it.– Rinzwind
May 23 '18 at 14:00
network-config generates 50-cloud-init.cfg. and cloud-init ( cloudinit.readthedocs.io/en/latest ) triggers network-config ( cloudinit.readthedocs.io/en/latest/topics/network-config.html ). That happens on initial creation, and on restarting but only when your force it.– Rinzwind
May 23 '18 at 14:00
I don't have any files named
50-cloud-init.cfg -- I have 50-curtin-networking.cfg and 50-cloud-init-yaml. Did you mean the former? If so, how exactly do you "force" cloud-init to regenerate 50-cloud-init.yaml from 50-curtin-networking.cfg?– kartik_subbarao
May 23 '18 at 15:18
I don't have any files named
50-cloud-init.cfg -- I have 50-curtin-networking.cfg and 50-cloud-init-yaml. Did you mean the former? If so, how exactly do you "force" cloud-init to regenerate 50-cloud-init.yaml from 50-curtin-networking.cfg?– kartik_subbarao
May 23 '18 at 15:18
add a comment |
3 Answers
3
active
oldest
votes
Make your networking changes to the /etc/cloud/cloud.cfg.d/50-curtin-networking.cfg file as if you were putting them in the yaml file.
Then do the following:
sudo cloud-init clean
sudo cloud-init init
sudo netplan apply
This will process your 50-curtin-networking.cfg file, generate the 50-cloud-init.yaml file and apply the yaml file netplan configuration.
In this way, you can write your networking config in the 50-curtin-networking.cfg file as the comments imply you should do.
A lot of the confusion between setting networking up in the 50-cloud-init.yaml file vs the 01-netcfg.yaml found in the /etc/netplan directory comes down to the installer used for Ubuntu 18.04 LTS.
The live installer uses cloud-init, whereas the alternate installer does not.
So for networking your installer choice changes how you will set up networking.
ubuntu-18.04.1-server-amd64.iso -> 01-netcfg.yaml
ubuntu-18.04.1-live-server-amd64.iso -> 50-curtin-networking.cfg
add a comment |
I assume this is an ordinary server, behind a router or switch that then connects to the internet. I'd rename the 50-cloud-init.yaml file:
sudo mv /etc/netplan/50-cloud-init.yaml /etc/netplan/01-netcfg.yaml
Then find out the relevant interface name:
ifconfig
Assuming, for an example, that your relevant interface is enp0s25, edit the file:
sudo nano /etc/netplan/01-netcfg.yaml
Amend the file to read:
network:
version: 2
renderer: networkd
ethernets:
enp0s25:
dhcp4: no
addresses: [192.168.100.40/22]
gateway4: 192.168.100.1
nameservers:
addresses: [8.8.8.8,8.8.4.4]
Of course, susbstitue your exact details here. Spacing, indentation, etc. are crucial. Proofread carefully. Save (Ctrl+o followed by Enter) and close (Ctrl+x) the text editor.
Next:
sudo netplan apply
sudo ip link set enp0s25 down
sudo ip link set enp0s25 up
Did you get the requested IP address?
ip addr show
Can you ping?
ping -c3 8.8.8.8
ping -c3 www.ubuntu.com
If you get ping returns, you are all set.
It seems like you're suggesting that the text at the top of 50-cloud-init.yaml, warning against editing it manually, should be ignored :-) This may end up being the approach taken, but I'd ideally like to understand why that text is there in the first place. Presumably the designers had some workflow in mind when they created that process. And what about /etc/cloud/cloud.cfg.d/50-curtin-networking.cfg?
– kartik_subbarao
May 14 '18 at 21:01
I've renamed the question to hopefully make it clearer.
– kartik_subbarao
May 14 '18 at 21:16
Is this a cloud instance?
– chili555
May 14 '18 at 21:16
No, it is not a cloud instance. It is a standalone server on an internal network.
– kartik_subbarao
May 15 '18 at 12:20
That's what I meant above when I said, "I assume this is an ordinary server, ..." Please check here: blog.printk.io/2018/04/… I still think 01-netcfg.yaml is appropriate.
– chili555
May 15 '18 at 13:03
|
show 1 more comment
I ended up editing the /etc/systemd/resolved.conf file and removed the comment on the DNS= line and added my preferred DNS entries with a space separating entries I.E.: DNS = 8.8.8.8 8.8.4.4
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
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
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1036266%2fwhat-is-the-most-authoritative-file-process-for-managing-ip-addresses-on-an-18-0%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
Make your networking changes to the /etc/cloud/cloud.cfg.d/50-curtin-networking.cfg file as if you were putting them in the yaml file.
Then do the following:
sudo cloud-init clean
sudo cloud-init init
sudo netplan apply
This will process your 50-curtin-networking.cfg file, generate the 50-cloud-init.yaml file and apply the yaml file netplan configuration.
In this way, you can write your networking config in the 50-curtin-networking.cfg file as the comments imply you should do.
A lot of the confusion between setting networking up in the 50-cloud-init.yaml file vs the 01-netcfg.yaml found in the /etc/netplan directory comes down to the installer used for Ubuntu 18.04 LTS.
The live installer uses cloud-init, whereas the alternate installer does not.
So for networking your installer choice changes how you will set up networking.
ubuntu-18.04.1-server-amd64.iso -> 01-netcfg.yaml
ubuntu-18.04.1-live-server-amd64.iso -> 50-curtin-networking.cfg
add a comment |
Make your networking changes to the /etc/cloud/cloud.cfg.d/50-curtin-networking.cfg file as if you were putting them in the yaml file.
Then do the following:
sudo cloud-init clean
sudo cloud-init init
sudo netplan apply
This will process your 50-curtin-networking.cfg file, generate the 50-cloud-init.yaml file and apply the yaml file netplan configuration.
In this way, you can write your networking config in the 50-curtin-networking.cfg file as the comments imply you should do.
A lot of the confusion between setting networking up in the 50-cloud-init.yaml file vs the 01-netcfg.yaml found in the /etc/netplan directory comes down to the installer used for Ubuntu 18.04 LTS.
The live installer uses cloud-init, whereas the alternate installer does not.
So for networking your installer choice changes how you will set up networking.
ubuntu-18.04.1-server-amd64.iso -> 01-netcfg.yaml
ubuntu-18.04.1-live-server-amd64.iso -> 50-curtin-networking.cfg
add a comment |
Make your networking changes to the /etc/cloud/cloud.cfg.d/50-curtin-networking.cfg file as if you were putting them in the yaml file.
Then do the following:
sudo cloud-init clean
sudo cloud-init init
sudo netplan apply
This will process your 50-curtin-networking.cfg file, generate the 50-cloud-init.yaml file and apply the yaml file netplan configuration.
In this way, you can write your networking config in the 50-curtin-networking.cfg file as the comments imply you should do.
A lot of the confusion between setting networking up in the 50-cloud-init.yaml file vs the 01-netcfg.yaml found in the /etc/netplan directory comes down to the installer used for Ubuntu 18.04 LTS.
The live installer uses cloud-init, whereas the alternate installer does not.
So for networking your installer choice changes how you will set up networking.
ubuntu-18.04.1-server-amd64.iso -> 01-netcfg.yaml
ubuntu-18.04.1-live-server-amd64.iso -> 50-curtin-networking.cfg
Make your networking changes to the /etc/cloud/cloud.cfg.d/50-curtin-networking.cfg file as if you were putting them in the yaml file.
Then do the following:
sudo cloud-init clean
sudo cloud-init init
sudo netplan apply
This will process your 50-curtin-networking.cfg file, generate the 50-cloud-init.yaml file and apply the yaml file netplan configuration.
In this way, you can write your networking config in the 50-curtin-networking.cfg file as the comments imply you should do.
A lot of the confusion between setting networking up in the 50-cloud-init.yaml file vs the 01-netcfg.yaml found in the /etc/netplan directory comes down to the installer used for Ubuntu 18.04 LTS.
The live installer uses cloud-init, whereas the alternate installer does not.
So for networking your installer choice changes how you will set up networking.
ubuntu-18.04.1-server-amd64.iso -> 01-netcfg.yaml
ubuntu-18.04.1-live-server-amd64.iso -> 50-curtin-networking.cfg
edited Aug 13 '18 at 13:20
answered Aug 6 '18 at 15:57
JargonManJargonMan
314
314
add a comment |
add a comment |
I assume this is an ordinary server, behind a router or switch that then connects to the internet. I'd rename the 50-cloud-init.yaml file:
sudo mv /etc/netplan/50-cloud-init.yaml /etc/netplan/01-netcfg.yaml
Then find out the relevant interface name:
ifconfig
Assuming, for an example, that your relevant interface is enp0s25, edit the file:
sudo nano /etc/netplan/01-netcfg.yaml
Amend the file to read:
network:
version: 2
renderer: networkd
ethernets:
enp0s25:
dhcp4: no
addresses: [192.168.100.40/22]
gateway4: 192.168.100.1
nameservers:
addresses: [8.8.8.8,8.8.4.4]
Of course, susbstitue your exact details here. Spacing, indentation, etc. are crucial. Proofread carefully. Save (Ctrl+o followed by Enter) and close (Ctrl+x) the text editor.
Next:
sudo netplan apply
sudo ip link set enp0s25 down
sudo ip link set enp0s25 up
Did you get the requested IP address?
ip addr show
Can you ping?
ping -c3 8.8.8.8
ping -c3 www.ubuntu.com
If you get ping returns, you are all set.
It seems like you're suggesting that the text at the top of 50-cloud-init.yaml, warning against editing it manually, should be ignored :-) This may end up being the approach taken, but I'd ideally like to understand why that text is there in the first place. Presumably the designers had some workflow in mind when they created that process. And what about /etc/cloud/cloud.cfg.d/50-curtin-networking.cfg?
– kartik_subbarao
May 14 '18 at 21:01
I've renamed the question to hopefully make it clearer.
– kartik_subbarao
May 14 '18 at 21:16
Is this a cloud instance?
– chili555
May 14 '18 at 21:16
No, it is not a cloud instance. It is a standalone server on an internal network.
– kartik_subbarao
May 15 '18 at 12:20
That's what I meant above when I said, "I assume this is an ordinary server, ..." Please check here: blog.printk.io/2018/04/… I still think 01-netcfg.yaml is appropriate.
– chili555
May 15 '18 at 13:03
|
show 1 more comment
I assume this is an ordinary server, behind a router or switch that then connects to the internet. I'd rename the 50-cloud-init.yaml file:
sudo mv /etc/netplan/50-cloud-init.yaml /etc/netplan/01-netcfg.yaml
Then find out the relevant interface name:
ifconfig
Assuming, for an example, that your relevant interface is enp0s25, edit the file:
sudo nano /etc/netplan/01-netcfg.yaml
Amend the file to read:
network:
version: 2
renderer: networkd
ethernets:
enp0s25:
dhcp4: no
addresses: [192.168.100.40/22]
gateway4: 192.168.100.1
nameservers:
addresses: [8.8.8.8,8.8.4.4]
Of course, susbstitue your exact details here. Spacing, indentation, etc. are crucial. Proofread carefully. Save (Ctrl+o followed by Enter) and close (Ctrl+x) the text editor.
Next:
sudo netplan apply
sudo ip link set enp0s25 down
sudo ip link set enp0s25 up
Did you get the requested IP address?
ip addr show
Can you ping?
ping -c3 8.8.8.8
ping -c3 www.ubuntu.com
If you get ping returns, you are all set.
It seems like you're suggesting that the text at the top of 50-cloud-init.yaml, warning against editing it manually, should be ignored :-) This may end up being the approach taken, but I'd ideally like to understand why that text is there in the first place. Presumably the designers had some workflow in mind when they created that process. And what about /etc/cloud/cloud.cfg.d/50-curtin-networking.cfg?
– kartik_subbarao
May 14 '18 at 21:01
I've renamed the question to hopefully make it clearer.
– kartik_subbarao
May 14 '18 at 21:16
Is this a cloud instance?
– chili555
May 14 '18 at 21:16
No, it is not a cloud instance. It is a standalone server on an internal network.
– kartik_subbarao
May 15 '18 at 12:20
That's what I meant above when I said, "I assume this is an ordinary server, ..." Please check here: blog.printk.io/2018/04/… I still think 01-netcfg.yaml is appropriate.
– chili555
May 15 '18 at 13:03
|
show 1 more comment
I assume this is an ordinary server, behind a router or switch that then connects to the internet. I'd rename the 50-cloud-init.yaml file:
sudo mv /etc/netplan/50-cloud-init.yaml /etc/netplan/01-netcfg.yaml
Then find out the relevant interface name:
ifconfig
Assuming, for an example, that your relevant interface is enp0s25, edit the file:
sudo nano /etc/netplan/01-netcfg.yaml
Amend the file to read:
network:
version: 2
renderer: networkd
ethernets:
enp0s25:
dhcp4: no
addresses: [192.168.100.40/22]
gateway4: 192.168.100.1
nameservers:
addresses: [8.8.8.8,8.8.4.4]
Of course, susbstitue your exact details here. Spacing, indentation, etc. are crucial. Proofread carefully. Save (Ctrl+o followed by Enter) and close (Ctrl+x) the text editor.
Next:
sudo netplan apply
sudo ip link set enp0s25 down
sudo ip link set enp0s25 up
Did you get the requested IP address?
ip addr show
Can you ping?
ping -c3 8.8.8.8
ping -c3 www.ubuntu.com
If you get ping returns, you are all set.
I assume this is an ordinary server, behind a router or switch that then connects to the internet. I'd rename the 50-cloud-init.yaml file:
sudo mv /etc/netplan/50-cloud-init.yaml /etc/netplan/01-netcfg.yaml
Then find out the relevant interface name:
ifconfig
Assuming, for an example, that your relevant interface is enp0s25, edit the file:
sudo nano /etc/netplan/01-netcfg.yaml
Amend the file to read:
network:
version: 2
renderer: networkd
ethernets:
enp0s25:
dhcp4: no
addresses: [192.168.100.40/22]
gateway4: 192.168.100.1
nameservers:
addresses: [8.8.8.8,8.8.4.4]
Of course, susbstitue your exact details here. Spacing, indentation, etc. are crucial. Proofread carefully. Save (Ctrl+o followed by Enter) and close (Ctrl+x) the text editor.
Next:
sudo netplan apply
sudo ip link set enp0s25 down
sudo ip link set enp0s25 up
Did you get the requested IP address?
ip addr show
Can you ping?
ping -c3 8.8.8.8
ping -c3 www.ubuntu.com
If you get ping returns, you are all set.
answered May 14 '18 at 20:36
chili555chili555
38.4k55177
38.4k55177
It seems like you're suggesting that the text at the top of 50-cloud-init.yaml, warning against editing it manually, should be ignored :-) This may end up being the approach taken, but I'd ideally like to understand why that text is there in the first place. Presumably the designers had some workflow in mind when they created that process. And what about /etc/cloud/cloud.cfg.d/50-curtin-networking.cfg?
– kartik_subbarao
May 14 '18 at 21:01
I've renamed the question to hopefully make it clearer.
– kartik_subbarao
May 14 '18 at 21:16
Is this a cloud instance?
– chili555
May 14 '18 at 21:16
No, it is not a cloud instance. It is a standalone server on an internal network.
– kartik_subbarao
May 15 '18 at 12:20
That's what I meant above when I said, "I assume this is an ordinary server, ..." Please check here: blog.printk.io/2018/04/… I still think 01-netcfg.yaml is appropriate.
– chili555
May 15 '18 at 13:03
|
show 1 more comment
It seems like you're suggesting that the text at the top of 50-cloud-init.yaml, warning against editing it manually, should be ignored :-) This may end up being the approach taken, but I'd ideally like to understand why that text is there in the first place. Presumably the designers had some workflow in mind when they created that process. And what about /etc/cloud/cloud.cfg.d/50-curtin-networking.cfg?
– kartik_subbarao
May 14 '18 at 21:01
I've renamed the question to hopefully make it clearer.
– kartik_subbarao
May 14 '18 at 21:16
Is this a cloud instance?
– chili555
May 14 '18 at 21:16
No, it is not a cloud instance. It is a standalone server on an internal network.
– kartik_subbarao
May 15 '18 at 12:20
That's what I meant above when I said, "I assume this is an ordinary server, ..." Please check here: blog.printk.io/2018/04/… I still think 01-netcfg.yaml is appropriate.
– chili555
May 15 '18 at 13:03
It seems like you're suggesting that the text at the top of 50-cloud-init.yaml, warning against editing it manually, should be ignored :-) This may end up being the approach taken, but I'd ideally like to understand why that text is there in the first place. Presumably the designers had some workflow in mind when they created that process. And what about /etc/cloud/cloud.cfg.d/50-curtin-networking.cfg?
– kartik_subbarao
May 14 '18 at 21:01
It seems like you're suggesting that the text at the top of 50-cloud-init.yaml, warning against editing it manually, should be ignored :-) This may end up being the approach taken, but I'd ideally like to understand why that text is there in the first place. Presumably the designers had some workflow in mind when they created that process. And what about /etc/cloud/cloud.cfg.d/50-curtin-networking.cfg?
– kartik_subbarao
May 14 '18 at 21:01
I've renamed the question to hopefully make it clearer.
– kartik_subbarao
May 14 '18 at 21:16
I've renamed the question to hopefully make it clearer.
– kartik_subbarao
May 14 '18 at 21:16
Is this a cloud instance?
– chili555
May 14 '18 at 21:16
Is this a cloud instance?
– chili555
May 14 '18 at 21:16
No, it is not a cloud instance. It is a standalone server on an internal network.
– kartik_subbarao
May 15 '18 at 12:20
No, it is not a cloud instance. It is a standalone server on an internal network.
– kartik_subbarao
May 15 '18 at 12:20
That's what I meant above when I said, "I assume this is an ordinary server, ..." Please check here: blog.printk.io/2018/04/… I still think 01-netcfg.yaml is appropriate.
– chili555
May 15 '18 at 13:03
That's what I meant above when I said, "I assume this is an ordinary server, ..." Please check here: blog.printk.io/2018/04/… I still think 01-netcfg.yaml is appropriate.
– chili555
May 15 '18 at 13:03
|
show 1 more comment
I ended up editing the /etc/systemd/resolved.conf file and removed the comment on the DNS= line and added my preferred DNS entries with a space separating entries I.E.: DNS = 8.8.8.8 8.8.4.4
add a comment |
I ended up editing the /etc/systemd/resolved.conf file and removed the comment on the DNS= line and added my preferred DNS entries with a space separating entries I.E.: DNS = 8.8.8.8 8.8.4.4
add a comment |
I ended up editing the /etc/systemd/resolved.conf file and removed the comment on the DNS= line and added my preferred DNS entries with a space separating entries I.E.: DNS = 8.8.8.8 8.8.4.4
I ended up editing the /etc/systemd/resolved.conf file and removed the comment on the DNS= line and added my preferred DNS entries with a space separating entries I.E.: DNS = 8.8.8.8 8.8.4.4
answered Jan 14 at 18:56
Andrew KaddasAndrew Kaddas
1
1
add a comment |
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
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
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1036266%2fwhat-is-the-most-authoritative-file-process-for-managing-ip-addresses-on-an-18-0%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
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
Required, but never shown
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
Required, but never shown
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
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
network-configgenerates50-cloud-init.cfg. andcloud-init( cloudinit.readthedocs.io/en/latest ) triggersnetwork-config( cloudinit.readthedocs.io/en/latest/topics/network-config.html ). That happens on initial creation, and on restarting but only when your force it.– Rinzwind
May 23 '18 at 14:00
I don't have any files named
50-cloud-init.cfg-- I have50-curtin-networking.cfgand50-cloud-init-yaml. Did you mean the former? If so, how exactly do you "force" cloud-init to regenerate50-cloud-init.yamlfrom50-curtin-networking.cfg?– kartik_subbarao
May 23 '18 at 15:18