Author Topic: Cant resolve Windows DHCP Leases Hostname using unbound. (Read 3373 times)

FullyBorked · « **on:** January 02, 2021, 09:34:20 pm »

I have my opnsense handing out DHCP and serving and my DNS server via unbound. I've enabled the option to have DHCP leases registered in DNS. This works fine for non-windows devices, such as smart phones, IoT devices etc. But not a single windows client is registered. Can't seem to figure out why this is. Anyone have any ideas?

lar.hed · « **Reply #1 on:** January 02, 2021, 10:07:08 pm »

Which DNS server is windows using?

FullyBorked · « **Reply #2 on:** January 02, 2021, 10:12:06 pm »

Quote from: lar.hed on January 02, 2021, 10:07:08 pm

Which DNS server is windows using?

It's pointing to the opnsense box for dns.

Sent from my IN2025 using Tapatalk

lar.hed · « **Reply #3 on:** January 02, 2021, 10:26:01 pm »

Okay, good, how do you validate that you can (or can't) resolve the intranet host names? Web browser? If so which web browser?

lar.hed · « **Reply #4 on:** January 02, 2021, 10:30:03 pm »

Oops sorry, I have made a read wrong. I thought you could not resolve, however you are wondering why not registred, and I have no idea...

FullyBorked · « **Reply #5 on:** January 02, 2021, 10:36:42 pm »

Yea, can't resolve hostnames of dhcp leased windows clients.

Sent from my IN2025 using Tapatalk

Author Topic: Cant resolve Windows DHCP Leases Hostname using unbound. (Read 3373 times)

FullyBorked

Cant resolve Windows DHCP Leases Hostname using unbound.

lar.hed

Re: Cant resolve Windows DHCP Leases Hostname using unbound.

FullyBorked

Re: Cant resolve Windows DHCP Leases Hostname using unbound.

lar.hed

Re: Cant resolve Windows DHCP Leases Hostname using unbound.

lar.hed

Re: Cant resolve Windows DHCP Leases Hostname using unbound.

FullyBorked

Re: Cant resolve Windows DHCP Leases Hostname using unbound.