• Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Search
  • Register
  • Login
Netgate Discussion Forum
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Search
  • Register
  • Login

DNS forwarding issues in SNAPSHOT-05-14-2007

DHCP and DNS
3
5
3.0k
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • A
    ameir
    last edited by May 24, 2007, 4:57 PM

    This took me a bit of poking to figure out, but I think I got it.  In SNAPSHOT-05-14-2007, if pfSense's domain is example.local (so the box is pf1.example.local, etc), then DNS queries for anything.example.local fail.  Our internal DNS server hosts three zones, all of which I could lookup except example.local.  If I change the domain in pfSense to another that we host in DNS, then queries to that domain fail, and example.local works.

    My workaround:

    I used fw.example.local as the domain, and all queries worked fine from there.

    I believe this bug was introduced in this snapshot or a very recent one.  I used SNAPSHOT-05-04-2007 previously and had no such DNS issues.

    This bug is not a huge one for me, might it might be good to look into.

    Hope this helps someone!

    1 Reply Last reply Reply Quote 0
    • S
      sullrich
      last edited by May 24, 2007, 6:35 PM

      Please try the most recent snapshot.

      1 Reply Last reply Reply Quote 0
      • A
        ameir
        last edited by May 25, 2007, 1:38 AM

        I just tried the most recent snapshot (1.2-BETA-1-TESTING-SNAPSHOT-05-24-2007) and the problem still exists.

        1 Reply Last reply Reply Quote 0
        • C
          cmb
          last edited by May 25, 2007, 2:48 AM

          I think this is just expected behavior for dnsmasq. I recall someone reporting the same thing on m0n0wall.

          If you use the forwarder to forward that domain to the internal DNS servers, it may work around that, not sure.

          1 Reply Last reply Reply Quote 0
          • A
            ameir
            last edited by May 25, 2007, 6:38 AM

            I have the DNS forwarder for the domain enabled as well with no luck.  This did work fine in previous snapshots btw.  No biggie for me, though.  Just wanted to help others out.

            1 Reply Last reply Reply Quote 0
            1 out of 5
            • First post
              1/5
              Last post
            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.