Why do you have a search list of cogeco.net??DNS Suffix Search List. . . . . . : cogeco.net
I show that as a public domain
Domain servers in listed order:
And no its not going to resolve pfsense.cogeco.net
dig @NS.CGOCABLE.NET pfsense.cogeco.net
;; QUESTION SECTION:
;pfsense.cogeco.net. IN A
;; AUTHORITY SECTION:
cogeco.net. 604800 IN SOA ns4.cgocable.net. dnsadmin.cgocable.net. 2009366394 1800 900 604800 86400
So if doing DNS query to your router, it would add that to the query, and you then go ask those name servers. They resolve www for exmaple
;; QUESTION SECTION:
;www.cogeco.net. IN A
;; ANSWER SECTION:
www.cogeco.net. 86400 IN A 188.8.131.52
Here is the thing your ROUTER would have nothing to at all with a netbios broadcast, NOTHING!! Other than the dhcp server on the router handing out dhcp info about it, ie the broadcast setting. The actual query and response would have nothing to do with your router. Nothing.. You would put the broadcast out on the wire, and then you would get a response from that box. But I can tell you for example pfsense wan interface is never in a million years going to respond to a netbios broadcast.
So for example, I have disabled my dns server then just pinged for host names (netbios) - and then showing you a sniff of this traffic.
So for example you see that pfsense does not ping, but one of my windows boxes does
Ping request could not find host pfsense.
Please check the name and try again.
Pinging storage [192.168.1.8] with 32 bytes of data:
Reply from 192.168.1.8: bytes=32 time=1ms TTL=128
Reply from 192.168.1.8: bytes=32 time<1ms TTL=128
Here from sniff you can see it try dns first with my domain added (local.lan) because all my boxes are in this domain and they use that as search domain, since my dns server was OFF, no replies. So then it tries to broadcast for the name. You see it ask for pfsense - he is never going to respond. See storage responded.. It went out on broadcast address for my segment 192.168.1.255, and then the acutal box says hey thats my netbios names and sends a directed response saying hey my IP is 192.168.1.8
If you want your boxes to respond to a netbios broadcast for their name, they would have to be setup to do so. Doubt your going to get pfsense to. Or setup dns to correctly resolve for your local machines, be it your router or another one. Use the correct search suffix, I doubt your router thinks its authoritative for cogeco.net? So even if your router did put its dhcp clients in dns, not sure it would be that domain - if you told your router it was owner of that domain, you would prob have issue resolving actual hosts on that domain.
So how do you want to resolve, be it broadcast, dns or wins? You could always just put host files on your boxes with your computer names. That is if you were static and nothing changes, etc. when it did you would have to update your hosts or in windows for netbios it would be lmhost. But host file works on them as well.