pfSense English Support > DHCP and DNS

Wildcard DNS entries

(1/2) > >>

If you need a wildcard in your DNS forwarder (*

   1. Log in to pfSense 2.0 instance via the web interface.
   2. Go to Services-> DNS Forwarder (http://pfSensense_url/services_dnsmasq.php)
   3. Click the Advanced button Add as many of the following as you need, each entry on a new line.


Where dev is the end of the wildcard entry, and is the ip that these wildcard names will resolve to. Think of dev as *.dev, but only list the part after the dot. So,, and anything else that ends in .dev and is not defined elsewhere, will resolve to the ip provided.

So if you need *.com then the corresponding line will look like


Thank you Scott

Howto for DNS Resolver (Unbound):

1. Go to Services -> DNS Resolver
2. Add the desired wildcard entries to the Advanced box:

--- Code: ---server:
local-zone: "" redirect
local-data: " 3600 IN A"

--- End code ---

Documentation: unbound.conf(5)

--- Code: ---redirect
                 The query is answered from the local data for the zone  name.
                 There  may  be  no  local  data  beneath the zone name.  This
                 answers queries for the zone, and all subdomains of the  zone
                 with the local data for the zone.  It can be used to redirect
                 a domain to return a different  address  record  to  the  end
                 user,    with   local-zone:   ""   redirect   and
                 local-data: " A" queries for  www.exam-
        and are redirected, so that users
                 with web browsers  cannot  access  sites  with  suffix  exam-

--- End code ---

This is in the wiki as well.

I cant get it to work

Seems that if you try the above for pfSense 2.2.4 with an unbound resolver, you will get a duplicate zone error...

--- Code: ---unbound: [42597:0] warning: duplicate local-zone
unbound: [42597:0] error: could not enter zone transparent
unbound: [42597:0] fatal error: Could not set up local zones
--- End code ---

if I just use the last line (suggested by the wiki), it starts successfully. From an external IP dig doesn't seem to like it and the wildcard still doesn't work...

--- Code: ---[user@localhost /]$ dig

; <<>> DiG 9.10.2-P4-RedHat-9.10.2-5.P4.fc22 <<>>
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: REFUSED, id: 24562
;; flags: qr rd ad; QUERY: 0, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
;; WARNING: recursion requested but not available

;; Query time: 157 msec
;; WHEN: Wed Oct 14 15:01:32 PDT 2015
;; MSG SIZE  rcvd: 12

[user@localhost /]$
--- End code ---

FYI - I have opened TCP/UDP 53 in the firewall


[0] Message Index

[#] Next page

Go to full version