[Dnsmasq-discuss] host(1) queries to AAAA, MX records; making authoritative server

[Johnny Utahh]

On 2020-07-03 1:07 PM, Johnny Utahh wrote:
> Two related questions:
>
>
> 1. Support non-error host(1) queries to AAAA and MX records?
>
> Cmdline-session details, with private info (hopefully) redacted:
> https://gist.githubusercontent.com/johnnyutahh/0f171e47e6ed861f66a1835150a11e4a/raw
>
> Short version:
>
> a. host(1) against my dnsmasq server == 5(REFUSED)
> b. host(1) against Cloudflare/GoDaddy == no error
>
> Details:
>
> Ubuntu 20.04's host(1) by default appears to (I think?) query all 3 of 
> of A, AAAA, and MX records. In my simple, 
> dnsmasq-served-by-only-the-A-record-is-in-/etc/hosts-config, host(1) 
> complains about the AAAA and MX looks. When asking Cloudflare (with 
> GoDaddy as source/authoritative server), host(1) does not complain.
>
> How can I make my dnsmasq server mimic the Cloudflare/GoDaddy response 
> and make host(1) happy?  (I'd like my users to not complain after a 
> switchover.)
>
> Does Cloudflare/GoDaddy answer with a blank/empty-string AAAA and MX 
> record, while dnsmasq simply respond with a "not here"/5(REFUSED) 
> response?
>
> What is better/best-practice behavior and why?
>
>
> 2. Make dnsmasq, sans upstream DNS, the authoritative DNS for my domains?
>
> The host(1) output from dnsmasq's server shows the reply as 
> non-authoritative, if I'm reading its output correctly.
>
> Why would dnsmasq not, by default, claim it's the authoritative server 
> if (in my case) there's no upstream DNS? And how can I make it do so?

Clarifying:
> When asking Cloudflare (with GoDaddy as source/authoritative server), 
> host(1) does not complain.

...even when there is no AAAA nor MX record.

-- 
//
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/attachments/20200703/0b973ae0/attachment.html>