New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Comments
Yes, I did @TimboJones
I was holding it for couple of days until the support finally replied to my ask.
It will be restocked?
Sorry for not being able to pay your bill due to the anti-fraud system.
We have been verified and if you still require this service, please pay as soon as possible.
Hello everyone.
I'm sorry for the recent delay due to problems with the Japanese DC.
We have increased the hours of use for the orders replied to in this thread so far.
If you have any questions you can DM or ask via ticket.
Anyone here getting the VPS runs without issue, it's been days I got stuck. I'm new with ipv6 VPS. The "/etc/resolv.conf" got overwritten back to default whenever I reboot.
Hope someone is kind enought to share some tutorial for me to speed up :-)
When will the Japanese DC come?
This is known issue on many VPS, affecting both OpenVZ and KVM.
Solution is
sudo chattr +i /etc/resolv.conf.The file will then be locked.
SolusVM or Virtualizor cannot overwrite it.
You can't modify or delete it either.
You can unlock with the same command but changing
+ito-i.Thanks for your advice @yoursunny
Looks like they don't allow +i
sudo chattr +i /etc/resolv.conf
chattr: Operation not supported while reading flags on /etc/resolv.conf
Open tiket ask for provider to stop meddling when your filesystem.
These overrides can be turned off on hypervisor side.
Try editing /etc/systemd/resolved.conf instead. The nameservers can be changed in DNS= and FallbackDNS= (make sure it's ipv6)
After you're done and saved, sudo systemctl restart systemd-resolved.service
your system should be using the nameservers you've specified.
Got it @yoursunny, thanks. But looks like they are short of support staff. Only 1 person is responding and sometimes it takes more than 24 hours for a reply.
Thanks for your guide @homeos, I learned a lot today.
Unfortunately it's still not working when I reboot the system.
I'm not able to perform "apt update" whenever there is a system reboot :-)
Hi swag
I am very sorry. After my investigation, it was caused by the cloudinit module.
If you reboot through the control panel, it will reset to the system default dns, you can prevent the dns reset by just typing "reboot" in the system.
Thanks
@Chandler, FYI...I'm using ssh to login. Everytime i do a reboot the dns reset back to "127.0.0.53". I submitted a ticket since 12/25/2022 on this issue and until today it's not solve.
First operate sudo systemctl stop systemd-resolved After editing and saving DNS= and FallbackDNS= in /etc/systemd/resolved.conf, (ensure it is ipv6) run this command sudo systemctl start systemd-resolved. Finally run sudo systemctl enable systemd-resolved (Make sure after reboot, dns available) Good luck!
Update.
Usually we reply to your questions within 24 hours.
But you created two tickets for the same question and we replied to the latest one. Please check.
You can try @admax's method.
https://lowendtalk.com/discussion/comment/3573213/#Comment_3573213
Also, we have limited human resources and try to solve all problems for you as much as possible. But please do not create multiple tickets creating non-essential issues.
This is not caused by hypervisor/ provider.
It's part of your operating system.
See this answer Why does /etc/resolv.conf point at 127.0.0.53?
If you do this, the DNS in
/etc/resolv.confwould still be 127.0.0.53, but the DNS queries are forwarded to the configured DNS servers, as well as those received via DHCP (if you have KVM and enable DHCP).The other way is
sudo systemctl mask systemd-resolvedand you'll regain control over/etc/resolv.conf.Thank you so much @admax, finally it's working out nicely now :-)
Merry Christmas to those that's celebrating and happy holiday!
@Chandler It's working now, if the support is helpful at the first place. I do not need to come here seeking help and tutorial from the community.
Anyhow, thanks for your team effort :-)
@yoursunny Noted on why dns reset back to "127.0.0.53". Thanks for the link.
Besides, on > The other way is
sudo systemctl mask systemd-resolvedand you'll regain control over/etc/resolv.conf. <-- is this method is the recommended one?But that's the best I can do for now. Unless the dhcp configuration works (because I noticed dhcp on the control panel said "no"), the system has changed the dhcp configuration, but nothing works and the configuration is still faulty.
Another way to restart after dns is available, combined with @yoursunny can be like this:
sudo systemctl stop systemd-resolvedsudo systemctl disable systemd-resolvedsudo rm /etc/resolv.confsudo vim /etc/resolv.confType
nameserver(make sure it is ipv6)Regain control of
/etc/resolv.conf.I wrote
sudo systemctl mask systemd-resolved, which ensures the service cannot accidentally start as a dependency of another unit.sudo vimshould be replaced withsudoedit, so that the editor is running without root privilege.If it invokes the wrong editor (nano is for weaklings), you can type
EDITOR=vi sudoedit.It's me again as I need help, 1Nextnet support is not able to resolve my issue for weeks now.
I just want to add my new ipv6 to my VPS, usually I will just add it into /etc/network/interfaces for my other VPS's.
But when I restart I got below error.
root@can-163:~# vim /etc/network/interfaces
root@can-163:~# systemctl restart networking
Job for networking.service failed because the control process exited with error code.
See "systemctl status networking.service" and "journalctl -xe" for details.
root@can-163:~# systemctl restart networking
Is the promo still active?
So look at the log for details! It literally tells you what to do!
Below is the log details:-
root@can-163:~# systemctl status networking.service
● networking.service - Raise network interfaces
Loaded: loaded (/lib/systemd/system/networking.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Fri 2022-12-30 02:13:24 JST; 1 weeks 3 days ago
Docs: man:interfaces(5)
Process: 23712 ExecStart=/sbin/ifup -a --read-environment (code=exited, status=1/FAILURE)
Main PID: 23712 (code=exited, status=1/FAILURE)
Dec 30 02:13:24 can-163 systemd[1]: Starting Raise network interfaces...
Dec 30 02:13:24 can-163 ifup[23712]: ifup: /etc/network/interfaces:11: misplaced option
Dec 30 02:13:24 can-163 ifup[23712]: ifup: couldn't read interfaces file "/etc/network/interfaces"
Dec 30 02:13:24 can-163 systemd[1]: networking.service: Main process exited, code=exited, status=1/FAILURE
Dec 30 02:13:24 can-163 systemd[1]: networking.service: Failed with result 'exit-code'.
Dec 30 02:13:24 can-163 systemd[1]: Failed to start Raise network interfaces.
Line 11 of /etc/network/interfaces is invalid. Fix it and restart.
Thanks for your advice, here is my content of "/etc/network/interfaces".
Hope I'm doing it correctly.
root@can-163:~# paste /etc/network/interfaces
Include files from /etc/network/interfaces.d:
source-directory /etc/network/interfaces.d
Cloud images dynamically generate config fragments for newly
attached interfaces. See /etc/udev/rules.d/75-cloud-ifupdown.rules
and /etc/network/cloud-ifupdown-helper. Dynamically generated
configuration fragments are stored in /run:
source-directory /run/network/interfaces.d
auto eno1
iface eno1 inet6 static
address 2a12:f8c1:30::
netmask 64
gateway 2a12:f8c1:30::1
up ip addr add 2a12:f8c1:31::4f/64 dev eth0