I’ve been scouring the forums for a while and haven’t found anything. Is there a permanent fix to adding a nameserver? I know “echo nameserver xxx.xxx.xxx.xxx > /etc/resolv.conf” is the temporary fix but, it’s quite annoying have to go through the ssh and typing process after every reboot.
There was a discussion about this in an earlier thread: https://www.plcnext-community.net/index.php?option=com_easydiscuss&view;=post&id;=399&Itemid;=221⟨=en At the time, the resolution was to do a factory reset after adding a dns-nameservers entry to the /etc/network/interfaces file: I don’t know if more recent firmware behaves differently. P.S. Don’t try the ifdown/ifup suggestion I made in that thread - the ifdown command will (of course) disable the Ethernet interface, making it impossible to issue the ifup command. 
- Martin.
Would it be possible to just write a .sh that runs at boot with “echo nameserver xxx.xxx.xxx.xxx > /etc/resolv.conf”?
TRY AT YOUR OWN RISK So I don’t know if this will screw up the PLC with subsequent updates or something but to avoid having to repeatedly type “echo nameserver 10.209.1.44 > /etc/resolv.conf” every reboot, the following is how I managed to get it to do this every reboot: THE FOLLOWING TAKES PLACE ON THE PLC (via SSH) 1: Become Root 2: Navigate to /etc/init.d 3: Use an editor (I used nano) and type the following: “nano plcnext” and press enter 4: Scroll to the very bottom of the file. 5: Ensure that you are at the very end of the file and type “echo nameserver xxx.xxx.xxx.xxx > /etc/resolv.conf” where xxx.xxx.xxx.xxx is the IP of the nameserver you’re using. At least here in the USA branch, I was told to use 10.209.1.44 for my nameserver and it works as should. 6: Save yourself from having to retype the command with every reboot. Again, I DO NOT KNOW IF THIS IS A GOOD IDEA FOR A FIX, ITS JUST WHAT I DID. I HAVE NO CLUE IF THE PLC WILL BREAK IN SUBSEQUENT UPDATES!!!
UPDATE*** I updated to the 1.02 firmware and it kept everything the way its supposed to.