Recent content by CornfieldWin

Have not found a problem with this configuration. Will keep.

OK. "it was safer to drop this option than attempting to ensure it worked with the different scenarios, now that dnsmasq can run multiple instances for separate SDN." Curious if this applies to YazDHCP addon which runs successfully with dnsmasq instances on every comms related Linux interface...

Better yet, just replace what is in /etc\resolv.conf with "nameserver 127.0.01" and then it works as intended on the router to pass first through dnsmasq and then on to unbound (or whatever upstream DNS resolver) that dnsmasq is configured to use. Oddly, it is not even necessary to remove...

I know I had this working a few months back but can't find my notes. Everything I search for says this should work. The issue is not forwarding local names to unbound but rather letting dnsmasq resolve local names first (unbound.conf has an option for bypassing dnsmasq but it is not being used)...

Cannot find the WAN option in Administration - Tweaks or in WAN DNS Settings in WAN where I could Forward local domain queries to upstream Server DNS knowing that unbound lives there and I use no others, but don't like that idea for potential future confusion and misconfiguration.

All attempts to ping in SSH terminal say "bad address", nothing is resolving. Windows CMD is happy as a clam to ping local DNS names which I assign using DHCP assignment after which I religiously reboot. I know I saw this somewhere else as a YazDHCP and unbound interaction but off hand I can't...

Must be doing something basic the wrong way on my AX-88U Pro, but not sure what. Does unbound have to be installed after YazDHCP? Going to do a factory reset in any case, but would like to get it right.

Code block test etc/hosts Thank you

/etc/ethers Pla Or explaining what has been explained over and over. RTFP.

Both dnsmasq.postconf and hosts.conf as posted have "she bang" directive transpose to DOS notation for posting.

Cute. I still haven't figured out how you do those system file names without that nagging error message so I will go on using DOS notation to post. Yes it is correct in the original! Whether that is essential varies by *ix system although I have never seen one that didn't have a default shell...

I had to edit for the posting restriction that obviously from your post has a a work around. Now for the surprise. Found an online reference to hosts.add for jffss configs and it works, unlike hosts.postconf and the addn-hosts directive which I will simply leave on the list as broken in the...

Yes and no. Syslog says it ran if you trust the log message. But there is no sign that it actually spawned and executed. The hosts file did not change and the touch file in jffs did not appear as did from SSH. So did it actually execute or something intended to launch it but didn't. Frustrating...

Same difference in this case - if only hosts.postconf would just run at boot time, which so far it has not. The use of shell variables as symbolic names is intentional for reasons of good coding practice, clarity and consistency across scripts to enforce configuration relationships, and parallel...