• 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 dteed

  1. dteed

    Connect to DNS automatically, blocks access by NATed bind resolver

    I had the same working set up as you describe, except using my own resolver inside the LAN. I've tried your suggestion of using 8.8.8.8 for DNS Server 1 as above. Any kind of lookup of bellaliant.net using these resolvers works fine: 8.8.8.8 192.168.0.1 (router) 192.168.0.3 (Linux system with...
  2. dteed

    Connect to DNS automatically, blocks access by NATed bind resolver

    If you took a look a the thread on the NSLUG linux users group, you'll see many things were tested. Worked: host bellaliant.net 8.8.8.8 host bellaliant.net 192.168.0.1 (asus router as gateway IP) host cbc.ca 192.168.0.3 (Linux resolver server on my LAN) (99%...
  3. dteed

    Connect to DNS automatically, blocks access by NATed bind resolver

    Hi, I've checked my settings. Under Parental controls I have time of day access configured only. DNS based filtering is off and I've never used it. To fix the problem, I have only changed the automatic DNS setting under WAN tab. I suspect it is a firmware bug, because the router is able...
  4. dteed

    Connect to DNS automatically, blocks access by NATed bind resolver

    I went through some days troubleshooting this issue with the help of my LUG and now have understood why I could not access my ISP's website while using my own DNS resolver on my LAN. One can read the thread conclusion here if you want more indications of the tracing...
Back
Top