On 11/16/2018 4:50 PM, Andrew Miskell wrote:
> Hi,
> I’m trying to setup a dnsmasq server (version 2.79 on Ubuntu 18.10) for DNS 
> and DHCP to replace the horrible DNS/DHCP service built into the AT&T Fiber 
> gateways. I've gotten everything configured and I have a client pulling a 
> DHCP address but I’m not able to resolve it’s name in DNS using dnsmasq as 
> the name server. I can resolve entries in the /etc/hosts file without any 
> issues.
> From what I can tell, the DHCP client name is being passed successfully from 
> the client to the server (as it’s visible in the dnsmasq.leases file).
> I’ve included my current configuration below, am I missing some configuration 
> option that enables DHCP clients to register themselves into dnsmasq ’s DNS?
> root@ubuntu:/etc/dnsmasq.d# grep -v '#' amiskell.net | sed '/^\s*$/d'
> domain-needed
> bogus-priv
> strict-order
> server=
> expand-hosts
> domain=amiskell.net
> dhcp-range=,,12h
> dhcp-option=option:router,
> dhcp-option=option:dns-server,
> dhcp-option=option:netmask,
> dhcp-lease-max=150
> dhcp-leasefile=/var/lib/misc/dnsmasq.leases

Any reasons why you're specifying the 'dhcp-option's (dnsmasq should
determine those values automatically)
The same goes for the dhcp-lease, there is no reason to set an option
when you use the default value.

> root@ubuntu:/etc/dnsmasq.d# cat /var/lib/misc/dnsmasq.leases 
> 1542425553 70:88:6b:83:XX:XX A17062407 01:70:88:6b:83:XX:XX

What do you get if you do:

$ host A17062407

P.S. I'm assuming that you're the owner of 'amiskell.net'.

John Doe

Dnsmasq-discuss mailing list

Reply via email to