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

DNS redirect issue: Reply from unexpected source

Scheduled Pinned Locked Moved NAT
3 Posts 1 Posters 1.5k Views
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.
  • S
    S_m
    last edited by May 28, 2022, 8:10 AM

    I'm having issues with a pfSense installation (2.6.0) that had redirected the DNS configured as the docs: https://docs.netgate.com/pfsense/en/latest/recipes/dns-redirect.html

    PORT FORWARD and RULE, are working but the reply came from the pfSense LAN address instead of the DNS server.

    udp  192.168.100.191:54637 -> 127.0.0.1:53 (8.8.8.8:53)
    

    Result from a client:

    nslookup google.com
    ;; reply from unexpected source: 192.168.100.1#53, expected 8.8.8.8#53
    

    I don't recall when this started to happen exactly. Doing the same configuration on another box works fine.

    Same config for NAT on both boxes.

    1 Reply Last reply Reply Quote 0
    • S
      S_m
      last edited by May 28, 2022, 10:45 AM

      Shell output for: pfctl -ss

      all udp 127.0.0.1:53 (1.1.1.1:53) <- 192.168.100.175:36992       NO_TRAFFIC:SINGLE
      all udp 192.168.100.1:53 -> 192.168.100.175:36992       SINGLE:NO_TRAFFIC
      all udp 192.168.100.1:53 <- 192.168.100.175:55172       SINGLE:MULTIPLE
      
      1 Reply Last reply Reply Quote 0
      • S
        S_m
        last edited by S_m May 28, 2022, 7:23 PM May 28, 2022, 7:22 PM

        FIXED:
        I don't know why and how to check more deeply this issue:

        Following the documentation, to standarize every config.
        With Redirect target IP 127.0.0.1 as shown on the picture below.
        All the DNS answers came from the LAN address (each vlan)
        alt text

        Fixed with: Redirect target IP LAN_XX address

        1 Reply Last reply Reply Quote 0
        3 out of 3
        • First post
          3/3
          Last post
        Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
          This community forum collects and processes your personal information.
          consent.not_received