![]() ![]() My IP address is correctly registed for my network.ĭHCP is giving the router's address for DNS server, and of course the router is supposed to be pointing to OpenDNS.Įverything looks correct and just like I always set up OPenDNS for others. The router is updating my IP address with DNS-O-Matic, which is updating OpenDNS and some unrelated services for me. It sits behind the ISP's fiber "modem"/router (that also had one ISP initiated firmware update, but I don't know how significant it was). It's had several incremental upgrades during this process. To my surprise it doesn't appear that OpenDNS is working for me though the only thing I changed was the ISP.įor reference my router here is an ASUS RT-N66U running the latest Tomato firmware. I decided that I'd spend some time working with OpenDNS at my home/office, instead of only for clients and family that I support. It works great, but I immediately had connection problems that I eventually tracked down to the IPv6 tunnel so I disabled that. Recently I changed my ISP to the local municipal ISP to get their fiber service (100 Mbps up and down, recently upgraded to 300 Mbps up and down). That's not my problem, since it's a known issue. I've been running an IPv6 tunnel service for the last several years, so of course I'm not getting OpenDNS filtering with that since most or all of my DNS traffic is going out via IPv6. I'm assuming rotblitz will be the one to answer since he's much more conversant with nslookup than I am. I've got the permissions set to 755 on that script, so I'm a little confused why it wouldn't work, but at least it works as a regular cron job.Ok, now it's my turn to seek out help with a perplexing OpenDNS issue. (neither ddclient is updated nor is /tmp/ddclient-bg-updated created) I tried to setup a cron.hourly folder and putġ1 * * * * root run-parts /etc/cron.hourly I had to reboot to get it to rebuild /etc/crontab. I waited a day first and it didn't rebuild. Ps. dont forget to delete the "backup", after you edit crontab.logging there will be a backup made of crontab.logging~ which you should remove since otherwise you will get the events run 2x as both files are inserted into the crafted crontab file.Ĭreate a new file in /etc called crontab.custom or similar (I used crontab.myinitials)Ġ5 * * * * root /usr/sbin/ddclient -daemon 0 -file /etc/ddclient/nf This will cause it to be built into the crontab and run daily at 5:30 etc. you can google crontab syntax for more details on this if you like. Hope that clears up a way to add your own timed things via the cli.just watch after an up2date that your lines are still there, if not you will have to re-add them. Also, you could just create crontab.custom which wouldn't be overwritten, but i havent tried that lately to see if we parse with crontab.* or an actual list of specified files. The crontab is actually "built" at certain intervals via the various crontab.* files. Such as these files can often be replaced/built via up2dates, so if you have something custom you want to run as part of a certain process, simply add it like:ģ0 5 0 0 0 root /home/login/yourscript (eg) I'm trying cron.hourly now, but I'm not certain Astaro actually runs anything out of there. If not, /etc/crontab could be adjusted.ĭisclaimer: if you have an Astaro support contract, messing with the command line may void your support. I set up the config file last week, and #2 did work, but I just noticed today that #3 didn't work after a reboot. usr/sbin/ddclient -daemon 0 -file /etc/ddclient/nf usr/sbin/ddclient -file /etc/ddclient/nfģ. try to put it in the Astaro startup. if you do, remove the '-daemon 0' option from the command line. I tried putting it at the end of /etc/init.d/beeps but that didn't work.Ĥ. put a script in /etc/cron.hourly which contains: If that works, then you have several choices, depending upon how often your IP changes:ġ. run manually as needed, using above commandĢ. start the service manually after an Astaro restart ![]()
0 Comments
Leave a Reply. |