What's new
By:

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

Recent content by CornfieldWin

  1. C

    DNS works for clients but not router (in ssh terminal mode) using YazDHCP and Unbound.

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

    DNS works for clients but not router (in ssh terminal mode) using YazDHCP and Unbound.

    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...
  3. C

    DNS works for clients but not router (in ssh terminal mode) using YazDHCP and Unbound.

    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...
  4. C

    DNS works for clients but not router (in ssh terminal mode) using YazDHCP and Unbound.

    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)...
  5. C

    DNS works for clients but not router (in ssh terminal mode) using YazDHCP and Unbound.

    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.
  6. C

    DNS works for clients but not router (in ssh terminal mode) using YazDHCP and Unbound.

    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...
  7. C

    DNS works for clients but not router (in ssh terminal mode) using YazDHCP and Unbound.

    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.
  8. C

    Problems with dnsmasq scripts and manual configuration

    Code block test etc/hosts Thank you
  9. C

    Problems with dnsmasq scripts and manual configuration

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

    Problems with dnsmasq scripts and manual configuration

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

    Problems with dnsmasq scripts and manual configuration

    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...
  12. C

    Problems with dnsmasq scripts and manual configuration

    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...
  13. C

    Problems with dnsmasq scripts and manual configuration

    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...
  14. C

    Problems with dnsmasq scripts and manual configuration

    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...
  15. C

    Problems with dnsmasq scripts and manual configuration

See more
Back
Top
✖