I want my DNS server to resolve what I tell it to resolve and ONLY what I tell it. And I don't want it to resolve itself to some hard-coded interface unless I tell it to. Is that an unreasonable request?

@johnpoz: Create a public domain you want to use, then create a cname record and point it to whatever other names you want it to resolve too. I agree your using the wrong tool.. No a host file doesn't work that way either.. Oh man. I hate being dense. I've done this before (CNAME in my own domain to another hostname), I'm embarrassed I didn't think of it. Thanks for spoon-feeding me the answer, I'll just skulk away now  :'(

No problem.. Let us know how it works out or if you have more question..  So your working in the wild wild west of networking ;) I can for sure see it when you have tech based users.. But in your typical company setup, byod would be a help desk nightmare…. You could always just extend your networks across the vpn at Layer 2 and let them broadcast for host names ;) hehehe

If your ok with your isp intercepting dns queries - sure use forwarder mode…  I would be in a freaking uproar and on the phone with them, or finding a new isp..

It works only if you define the the the v6 primary with the correct statement. According to https://www.freebsd.org/cgi/man.cgi?query=dhcpd.conf&sektion=5&apropos=0&manpath=FreeBSD+9.0-RELEASE+and+Ports there are different statements for v6 and v4 addresses. The correct statement for v6 is "primary6". Right now pfsense only allows primary statement witch is v4 only.

Yeah but without knowing exactly what kind of bad name can end up in there, I can't get it fixed. :)

My /etc/inc/services looks like this : #option 121 option rfc3442-classless-static-rotues code 121 = array of unsigned integer 8; #option 120 option sip-servers code 120 = ip-address; #option 43         option space vendorSpecInfo;         option vendorSpecInfo.acs-url code 1 = text;

Hi Johnpz, We have updated to the latest version, it is observed that after updating only we are getting this issue, So that we reinstalled the older version manually. Still getting the same issue with the older version also now. We are sure there are no spaces in the hostname, checked many times.

@pozolero: @hny1: everybody can google it. http://www.freeformatter.com/csv-to-xml-converter.html http://xmlgrid.net/csvToXml.html http://www.convertcsv.com/csv-to-xml.htm …and so on...

Issue solved. turned out to be ACL's on the NAS device that was causing issues.

If you disable dhcp, then nobody would get anything.. If you only what your reservations to be served… Then click the little checkbox that says that ;) [image: denyunknown.png] [image: denyunknown.png_thumb]

@cmb: Fixed, thanks. https://redmine.pfsense.org/issues/6303 You're welcome. =)

Hi Sebastian, are you referring to the Client Export Wizard's option "Host Name Resolution"? Try the following, it did work for me: change the DynDNS "Hostname" option to a predefined provider like "City Network" set the hostname and save change the hostname back to Custom and save now there should be the entry "DynDNS: YOUR.DOMAIN.COM" in the Client Export Wizard's option "Host Name Resolution" Regards

@johnpoz: That is not what I see..  The latest lease is shown on top, then next then next, etc.. I believe that was fixed in the diff sorting method used in 2.3.

And do these problems occur if you shutdown dhcp, and clear all the old leases since they are no longer going to be valid.  Change the IP address of the interfrace, then do whatever you want to do for your dhcp range?

Interesting coincidence. my box with the DNS resolver problem-    (has IPv address obviously) PING6(56=40+8+8 bytes) 200x:1xx1:3xx4::1 –> ::1                (changed to obfuscate) --- ::1 ping6 statistics --- 3 packets transmitted, 0 packets received, 100.0% packet loss My customer box which works fine.  (does not have IPv6 set up) PING6(56=40+8+8 bytes) ::1 --> ::1 16 bytes from ::1, icmp_seq=0 hlim=64 time=0.521 ms 16 bytes from ::1, icmp_seq=1 hlim=64 time=0.353 ms 16 bytes from ::1, icmp_seq=2 hlim=64 time=0.459 ms

Unbound or bust. I have outbound filters that end up blocking DNS requests to some naughty authoritative DNS servers that ISP and other public available DNS would happily resolve.