As phil spells out correctly already many systems will auto append the domain they are in, be it you set it up on the system or they got it from the dhcp server, etc.

If home.de is a valid domain on the public net, it normally is not a good idea to use that as your domain on your local network - unless in fact you own said domain.

I would suggest you change your local systems to use say home.lan or home.de.lan or .local or  de.home etc.. something where the .tld is not a valid on the public.  This should remove any issue of it resolving to a public IP.

You can then resolve these hosts via pfsense dns or as stated create a forwarder in pfsense to send to your local dns that can resolve such domains, etc.

Hi,
thanks for the answer;
i found a solution to update the  nameserver for the host only with curl and a xml file.
May be someone can help me to add this provider into pfsense in the right way.

To find out the id from the host entry it is possible to send a "query" to the provider and get back an xml with members/values  and on is the right one …or over webif you are able to see the id.
How do i parse the income xml on pfsense for the required info like id or status code; look like the xml file i post.

here a example to change the ip

curl -X POST -d @xml https://api.domrobot.com/xmlrpc/

<methodcall><methodname>nameserver.recordUpdate</methodname>
  <params><param>
        <value><struct><member><name>user</name>
                  <value><string>%YOURUSERNAME%</string></value></member>
              <member><name>pass</name>
                  <value><string>%YOURPASSWORD%</string></value></member>
              <member><name>id</name>
                  <value><string>%IdOfTheHostEntry%</string></value></member>
              <member><name>ttl</name>
                  <value><string>3600</string></value></member>
              <member><name>content</name>
                  <value><string>%WanIP%</string></value></member></struct></value></params></methodcall>

^ agreed there is no information to even start "guessing" at what could be wrong if anything.

@doktornotor:

http://forum.pfsense.org/index.php?topic=40157.0

Looks like that is for adding option 82 during relay and not matching option 82 to a specific dhcp pool.

People can clone MACs and set their mac address to anything they like, so if you are running wireless, that could be the case here.  Just a possibility.

You are missing:
(same as parrent folder) - Host (A) - ip.add.re.ss - domain.ca
(same as parrent folder) - IPv6 Host (AAAA) - ip🅰d:d:r:e:s:s - domain.ca

"Is it normal that clients extend a query for e.g. www.atmel.com to www.atmel.com.mydomain.de  given my domain is mydomain.de ?"

Yup – its suffix search, it can be your friend but to be honest it can cause unwanted queries..  If you don't like your clients doing it -- you might want to turn it off on the clients.  Its only really helpful when your trying to do a dns query via only host name, your local domain gets added for you auto, etc.

Glad you got it sorted, so not a dns issue but network problem.

@sevenmac:

there is no computer jack on lan.

That's what you think! Some computer, which thinks of itself as Jack, has MAC address 00:1e:64:28:df:84 and is requesting DHCP configuration on your LAN interface. It either doesn't get the reply or ignores it.

Here's an example of a successful DHCP transaction from my DHCP log for comparison with your DHCP log:
Jul 4 20:06:40 dhcpd: DHCPDISCOVER from 00:30:18:b0:19:85 via bridge0
Jul 4 20:06:40 dhcpd: DHCPOFFER on 192.168.211.217 to 00:30:18:b0:19:85 via bridge0
Jul 4 20:06:40 dhcpd: DHCPDISCOVER from 00:30:18:b0:19:85 via bridge0
Jul 4 20:06:40 dhcpd: DHCPOFFER on 192.168.211.217 to 00:30:18:b0:19:85 via bridge0
Jul 4 20:06:42 dhcpd: DHCPREQUEST for 192.168.211.217 (192.168.211.173) from 00:30:18:b0:19:85 via bridge0
Jul 4 20:06:42 dhcpd: DHCPACK on 192.168.211.217 to 00:30:18:b0:19:85 via bridge0

I wonder what happened to the DHCP replies from pfSense.

Thanks for your replies.

Yes, unbound works and running stable for me since almost a week on 2.1 RC0 (using amd64 Jun 26 something at the moment).

Never mind, I solved the problems saving and restoring the configuration, uninstalling the dns-server package and installing nsd from the freebsd ports instead. Configuring it was easy and it does work with classless delegation (apparently even some root servers are now using it instead of BIND).

One doubt though:
I tried using /etc/rc.conf.local for starting the service, but this did not work as expected. So I added the line to launch the service to the end of /etc/rc (before the exit instruction), but this seems a little hackish.
Is there a more proper place to call custom scripts or commands at system startup?

Hi,

this is my reported problem I think: http://forum.pfsense.org/index.php/topic,63546.0.html

Bests

Reiner

Apologies wallabybob - I've just realised I never got back to this thread. You were absolutely right - I got as far as testing against FreeBSD and a few mobile phones, and none of them worked. As this has to work with potentially any device I've had to abandon this idea. Damn.

@wallabybob:

Though this apparently works with Windows clients I think it won't work with FreeBSD clients and might not with MAC OS, Linux or Android (the client is not in the same subnet as the default gateway).

alright i can ask about the first one; but as for the second; i have triple checked my DOCSIS 3.0 signal levels are well with in tolerated bounds. ill explorer it a bit further with my ISP, but im going to have to tear my hair out if i have to deal with Taiwanese level 1 tech support for more then 5 seconds.

ill keep this thread updated; but for anyone in the same situation; put a powered switch inbetween your cable modem, and the pfSense box, and you may notice your problem has been solved.
thanks to wallabybob for his assistance !

Here ya go:
https://github.com/pfsense/pfsense/commit/850324a23e45b3a11231f910290f8ff9b774d9bc