Hi there,

I've just searched the bug tracker with no luck.

I'm using "2.1-BETA0  (amd64) built on Thu Jun 28 09:42:08 EDT 2012"

I've got a problem with DNS resolution for the firewall itself.

I've added my two DNS servers (in LAN) to "General Setup" and checked
the "Do not use DNS Forwarder as a DNS server for the firewall". All
works fine for the firewall's point of view wrt DNS.

If I uncheck this option, DNS for the firewall itself doesn't work :
pfSense has added 127.0.0.1 in /etc/resolv.conf and uses it, but fails.

Also, despite checking the box again, and having a resolv.conf without
127.0.0.1, I can see in tcpdump that 127.0.0.1 is still used for DNS
(for clients because I've activated DNS masquerading, I suppose), but
always answers "NXDomain"

When doing tcpdump, I see that every packet sent to localhost has an
incorrect checksum. Could this be the source of my problem ?

11:21:35.461807 IP (tos 0x0, ttl 64, id 35149, offset 0, flags [none], proto 
UDP (17), length 118, bad cksum 0 (->f327)!)
    127.0.0.1.42732 > 127.0.0.1.53: 41354+[|domain]
11:21:35.461945 IP (tos 0x0, ttl 64, id 64302, offset 0, flags [none], proto 
UDP (17), length 118, bad cksum 0 (->8146)!)
    127.0.0.1.53 > 127.0.0.1.42732: 41354 NXDomain[|domain]

TIA

--
Jérôme Alet - <jerome.a...@univ-nc.nc> - Direction du Système d'Information
      Université de la Nouvelle-Calédonie - BPR4 - 98851 NOUMEA CEDEX
   Tél : +687 290081                                  Fax : +687 254829
_______________________________________________
List mailing list
List@lists.pfsense.org
http://lists.pfsense.org/mailman/listinfo/list

Reply via email to