Re: [Dnsmasq-discuss] Does dnsmasq support cname within same domain?

[Frank Liu]

On Wed, Mar 2, 2022 at 8:45 PM  wrote:

> On 3/3/22 15:07, Frank Liu wrote:
>
>
>
> On Wed, Mar 2, 2022 at 5:46 PM 
>  wrote:
>
>> I have:
>>
>> dhcp-host=,192.168.42.18,[::0:18],somehostname
>>
>> cname=somealias.mydomain,somehostname
>>
>>
>> This is working fine. I have version 2.80 (on OpenWRT 19.07).
>>
>> I see one difference to yours is that the target of the cname is only a
>> hostname and not the full domain. Does it work for you if you make that
>> change?
>>
>
> dhcp-host doesn't work for me. Geoff Back earlier in the thread also
> mentioned dhcp-host not working for him either.
>
> I don't think target full or short name matters. I always use full domain
> names in target, as mentioned earlier in this thread, but I just tried
> short hostname only, but it didn't make a difference.
>
>
> Ah well I also have
>
> addn-hosts=/tmp/hosts
>
> with /tmp/hosts containing a hosts file with:
>
> 192.168.42.18 somehostname.mydomain
>
>
> This was all set up by OpenWRT. Maybe that's why it works for me but not
> you.
>

That is correct. Using target from static hosts works, but not from dhcp,
even if you use dhcp-host reservation.
It seems like a dnsmasq bug to me.

Frank
___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss

Re: [Dnsmasq-discuss] Does dnsmasq support cname within same domain?

[hamish]

On 3/3/22 15:07, Frank Liu wrote:



On Wed, Mar 2, 2022 at 5:46 PM  wrote:

I have:

dhcp-host=,192.168.42.18,[::0:18],somehostname

cname=somealias.mydomain,somehostname


This is working fine. I have version 2.80 (on OpenWRT 19.07).

I see one difference to yours is that the target of the cname is
only a hostname and not the full domain. Does it work for you if
you make that change?


dhcp-host doesn't work for me. Geoff Back earlier in the thread also 
mentioned dhcp-host not working for him either.


I don't think target full or short name matters. I always use full 
domain names in target, as mentioned earlier in this thread, but I 
just tried short hostname only, but it didn't make a difference.



Ah well I also have

addn-hosts=/tmp/hosts

with /tmp/hosts containing a hosts file with:

192.168.42.18 somehostname.mydomain


This was all set up by OpenWRT. Maybe that's why it works for me but not 
you.



Hamish
___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss

Re: [Dnsmasq-discuss] Does dnsmasq support cname within same domain?

[Frank Liu]

On Wed, Mar 2, 2022 at 5:46 PM  wrote:

> I have:
>
> dhcp-host=,192.168.42.18,[::0:18],somehostname
>
> cname=somealias.mydomain,somehostname
>
>
> This is working fine. I have version 2.80 (on OpenWRT 19.07).
>
> I see one difference to yours is that the target of the cname is only a
> hostname and not the full domain. Does it work for you if you make that
> change?
>

dhcp-host doesn't work for me. Geoff Back earlier in the thread also
mentioned dhcp-host not working for him either.

I don't think target full or short name matters. I always use full domain
names in target, as mentioned earlier in this thread, but I just tried
short hostname only, but it didn't make a difference.

Frank
___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss

Re: [Dnsmasq-discuss] Does dnsmasq support cname within same domain?

[Frank Liu]

On Wed, Mar 2, 2022 at 7:08 PM Donald Muller 
wrote:

> Sorry there was a cut and paste mistake on my part. It should be
>
>
>
> cname=alias.test.example.com,alias.dummy.example.com,
> client1.test.example.com
>
>
>

No, it behaves the same as I use two separate cname lines:
different domain alias resolves, and same domain alias doesn't.
Did it work for you? If so, what version of dnsmasq do you use?

Thanks!
Frank
___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss

Re: [Dnsmasq-discuss] Does dnsmasq support cname within same domain?

[Donald Muller]

Sorry there was a cut and paste mistake on my part. It should be

cname=alias.test.example.com,alias.dummy.example.com,client1.test.example.com


From: Frank Liu 
Sent: Wednesday, March 2, 2022 5:39 PM
To: Donald Muller 
Cc: Matus UHLAR - fantomas ; 
dnsmasq-discuss@lists.thekelleys.org.uk
Subject: Re: [Dnsmasq-discuss] Does dnsmasq support cname within same domain?



On Wed, Mar 2, 2022 at 2:13 PM Donald Muller 
mailto:donmulle...@outlook.com>> wrote:

What if you try

cname=alias.test.example.com,client1.test.example.com,alias.dummy.example.com,client1.test.example.com

Does it work?

No, dnsmasq fails to start, with "CNAME loop" error.

Can anyone try to add cname for same domain, and see if it works for you?
Assuming your dhcp domain is 
internal.yourcompany.com, with an existing 
dhcp client client1, please add
cname=testalias.internal.yourcompany.com,client1.internal.yourcompany.com
and check if 
testalias.internal.yourcompany.com 
resolves?

Thanks!
Frank


___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss

Re: [Dnsmasq-discuss] Does dnsmasq support cname within same domain?

[hamish]

On 3/3/22 11:49, Frank Liu wrote:


dhcp target should work since it is known to dnsmasq. A name from a 
different dummy domain cname to dhcp target confirms working. The 
issue seems to be only within the same domain.




I have:

dhcp-host=,192.168.42.18,[::0:18],somehostname

cname=somealias.mydomain,somehostname


This is working fine. I have version 2.80 (on OpenWRT 19.07).

I see one difference to yours is that the target of the cname is only a 
hostname and not the full domain. Does it work for you if you make that 
change?




Hamish
___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss

Re: [Dnsmasq-discuss] Does dnsmasq support cname within same domain?

[Frank Liu]

On Wed, Mar 2, 2022 at 3:45 PM Geoff Back  wrote:

> With 2.86, I have found that cname works if the target is declared in a
> "host-record" line, but not if it is DHCP assigned.  Even if it's given
> a fixed IP address in a "dhcp-host" line.
>
>
Thanks for confirming!
I assume it also works for you if you use another/different dummy domain,
with a dhcp target.

The man page https://thekelleys.org.uk/dnsmasq/docs/dnsmasq-man.html says
*--cname=,[,][,]* Return a CNAME record which
indicates that  is really . There is a significant
limitation on the target; it must be a DNS record which is known to dnsmasq
and NOT a DNS record which comes from an upstream server.

dhcp target should work since it is known to dnsmasq. A name from a
different dummy domain cname to dhcp target confirms working. The issue
seems to be only within the same domain.

Frank
___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss

Re: [Dnsmasq-discuss] Does dnsmasq support cname within same domain?

[Geoff Back]

On 02/03/2022 22:38, Frank Liu wrote:
>
>
> On Wed, Mar 2, 2022 at 2:13 PM Donald Muller 
> wrote:
>
>
> What if you try
>
> cname=alias.test.example.com
> ,client1.test.example.com
> ,alias.dummy.example.com
> ,client1.test.example.com
> 
>
> Does it work?
>
>
> No, dnsmasq fails to start, with "CNAME loop" error.
>
> Can anyone try to add cname for same domain, and see if it works for you?
> Assuming your dhcp domain is internal.yourcompany.com
> , with an existing dhcp client
> client1, please add
> cname=testalias.internal.yourcompany.com
> ,client1.internal.yourcompany.com
> 
> and check if testalias.internal.yourcompany.com
>  resolves?
>
> Thanks!
> Frank

With 2.86, I have found that cname works if the target is declared in a
"host-record" line, but not if it is DHCP assigned.  Even if it's given
a fixed IP address in a "dhcp-host" line.

Cheers,

Geoff.
>
>
>
> ___
> Dnsmasq-discuss mailing list
> Dnsmasq-discuss@lists.thekelleys.org.uk
> https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss


___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss

Re: [Dnsmasq-discuss] Does dnsmasq support cname within same domain?

[Frank Liu]

On Wed, Mar 2, 2022 at 2:13 PM Donald Muller 
wrote:

>
> What if you try
>
> cname=alias.test.example.com,client1.test.example.com,
> alias.dummy.example.com,client1.test.example.com
>
> Does it work?
>

No, dnsmasq fails to start, with "CNAME loop" error.

Can anyone try to add cname for same domain, and see if it works for you?
Assuming your dhcp domain is internal.yourcompany.com, with an existing
dhcp client client1, please add
cname=testalias.internal.yourcompany.com,client1.internal.yourcompany.com
and check if testalias.internal.yourcompany.com resolves?

Thanks!
Frank
___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss

Re: [Dnsmasq-discuss] Does dnsmasq support cname within same domain?

[Donald Muller]

From: Dnsmasq-discuss  On 
Behalf Of Frank Liu
Sent: Wednesday, March 2, 2022 12:46 PM
To: Matus UHLAR - fantomas ; 
dnsmasq-discuss@lists.thekelleys.org.uk
Subject: Re: [Dnsmasq-discuss] Does dnsmasq support cname within same domain?



On Wed, Mar 2, 2022 at 7:14 AM Matus UHLAR - fantomas via Dnsmasq-discuss 
 wrote:
>> > > On Tue, Mar 01, 2022 at 01:01:51AM -0800, Frank Liu wrote:
>> > > > I am running dnsmasq for dhcp/dns of a local test domain: 
>> > > > http://test.example.com.
>> > > > Everything works fine. When a dhcp client (eg: client1) comes up, it 
>> > > > gets
>> > > > the IP from dnsmasq, and I can dig/nslookup 
>> > > > http://client1.test.example.com to get
>> > > > its IP.
>> > > >
>> > > > When I add a cname in the same domain, eg:
>> > > > cname=http://alias.test.example.com,http://client1.test.example.com
>> > > >
>> > > > dig/nslookup of http://alias.test.example.com only returns name
>> > > > http://client1.test.example.com, not the actual IP of 
>> > > > http://client1.test.example.com
>> > > >
>> > > > It's interesting that if I add the cname for a different domain, eg:
>> > > > cname=http://alias.dummy.example.com,http://client1.test.example.com
>> > > >
>> > > > dig/nslookup of http://alias.dummy.example.com will return both name
>> > > > http://client1.test.example.com and its IP.
>> > > >
>> > > > I tried a few different versions but that doesn't make a difference.

>> > On Tue, Mar 1, 2022 at 3:37 AM Geert Stappers via Dnsmasq-discuss wrote:
>> > > Please name those different versions.

>> On Tue, Mar 01, 2022 at 09:21:58AM -0800, Frank Liu wrote:
>> > 2.76 (Debian 9),   2.85 (Debian 11).

>On Tue, Mar 1, 2022 at 2:39 PM Geert Stappers via Dnsmasq-discuss 
>  wrote:
>> Ah, I'm now beyond the ambiguty of different version of dig/nslookup.

On 02.03.22 01:28, Frank Liu wrote:
>I don't think it matters with test OS or test application.

it may matter, 

>I also tried:
>ping http://alias.dummy.example.com works, but ping 
>http://alias.test.example.com gives
>unknown host error.
>(even though both names cname to the same http://client1.test.example.com in
>dnsmasq).

What do there result in?

dig http://alias.dummy.example.com http://alias.test.example.com 
http://client1.test.example.com
dig -t any http://alias.dummy.example.com http://alias.test.example.com 
http://client1.test.example.com

In below test, dnsmasq server (192.168.0.253) runs dnsmasq 2.85 (from Debian11).
I have below in the dnsmasq conf:

cname=http://alias.test.example.com,http://client1.test.example.com
cname=http://alias.dummy.example.com,http://client1.test.example.com

Test client is another Debian11 box

$ dig -v
DiG 9.16.22-Debian

$ dig @http://192.168.0.253 http://alias.dummy.example.com 
http://alias.test.example.com http://client1.test.example.com

; <<>> DiG 9.16.22-Debian <<>> @http://192.168.0.253 
http://alias.dummy.example.com http://alias.test.example.com 
http://client1.test.example.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 29718
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;http://alias.dummy.example.com. IN A

;; ANSWER SECTION:
http://alias.dummy.example.com. 0 IN CNAME http://client1.test.example.com.
http://client1.test.example.com. 0 IN A 192.168.0.70

;; Query time: 20 msec
;; SERVER: 192.168.0.253#53(192.168.0.253)
;; WHEN: Wed Mar 02 17:34:27 UTC 2022
;; MSG SIZE  rcvd: 114

;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 62870
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;http://alias.test.example.com. IN A

;; ANSWER SECTION:
http://alias.test.example.com. 5 IN CNAME http://client1.test.example.com.

;; Query time: 20 msec
;; SERVER: 192.168.0.253#53(192.168.0.253)
;; WHEN: Wed Mar 02 17:34:27 UTC 2022
;; MSG SIZE  rcvd: 96

;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 40301
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;http://client1.test.example.com. IN A

;; ANSWER SECTION:
http://client1.test.example.com. 5 IN A 192.168.0.70

;; Query time: 16 msec
;; SERVER: 192.168.0.253#53(192.168.0.253)
;; WHEN: Wed Mar 02 17:34:27 UTC 2022
;; MSG SIZE  rcvd: 75

$ dig -t any @http://192.168.0.253 http://alias.dummy.example.com 
http://alias.test.example.com http://client1.test.example.com

; <<>> DiG 9.16.22-Debian <<>> -t any @http://192.168.0.253 
http://alias.dummy.example.com http://alias.test.example.com 
http://client1.test.example.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 24227
;; flags: qr 

Re: [Dnsmasq-discuss] SERVFAIL and all-servers

[Simon Kelley]

The behaviour on this alternated between what you observed and what you 
advocate a few times before settling.


The problem with waiting for all replies is that a common source of 
SERVFAIL returns is domains with broken DNSSEC. In that case all the 
servers will return SERVFAIL, which is a bit of a pain if you have to 
wait for the slowest one, but a disaster if one server is not 
responding: in that case all you can do is wait for the timeout.


Defining SERVFAIL as the response to DNSSEC validation failure has 
always seemed odd to me.


all-servers is not necessarily more reliable: the default dnsmasq 
behaviour does a reasonably good job in most circumstances.



Cheers,

Simon.

On 28/02/2022 22:38, Tobias via Dnsmasq-discuss wrote:

Hi,

when using multiple upstream servers with "all-servers", and one
upstream is sending SERVFAIL very fast (e.g. because the upstream has a
dead upstream itself), dnsmasq uses this SERVFAIL as answer, probably
because it's the fastest one. This breaks the intended redundancy, but
is even worse, as other working upstreams are effectively not used
anymore. (Tested with v2.85 and v2.86.)

I'm not sure if that behavior has a valid use case, but at least for my
case it seems much better to only give a SERVFAIL if all upstream
servers answer with SERVFAIL.

Together with the other "all-servers" issue I reported ("DNSSEC and
all-servers"), the "all-servers" setup unfortunately is much less
reliable than I was hoping.

Thanks!

Tobias

___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss



___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss

Re: [Dnsmasq-discuss] Does dnsmasq support cname within same domain?

[Frank Liu]

On Wed, Mar 2, 2022 at 7:14 AM Matus UHLAR - fantomas via Dnsmasq-discuss <
dnsmasq-discuss@lists.thekelleys.org.uk> wrote:

> >> > > On Tue, Mar 01, 2022 at 01:01:51AM -0800, Frank Liu wrote:
> >> > > > I am running dnsmasq for dhcp/dns of a local test domain:
> test.example.com.
> >> > > > Everything works fine. When a dhcp client (eg: client1) comes up,
> it gets
> >> > > > the IP from dnsmasq, and I can dig/nslookup
> client1.test.example.com to get
> >> > > > its IP.
> >> > > >
> >> > > > When I add a cname in the same domain, eg:
> >> > > > cname=alias.test.example.com,client1.test.example.com
> >> > > >
> >> > > > dig/nslookup of alias.test.example.com only returns name
> >> > > > client1.test.example.com, not the actual IP of
> client1.test.example.com
> >> > > >
> >> > > > It's interesting that if I add the cname for a different domain,
> eg:
> >> > > > cname=alias.dummy.example.com,client1.test.example.com
> >> > > >
> >> > > > dig/nslookup of alias.dummy.example.com will return both name
> >> > > > client1.test.example.com and its IP.
> >> > > >
> >> > > > I tried a few different versions but that doesn't make a
> difference.
>
> >> > On Tue, Mar 1, 2022 at 3:37 AM Geert Stappers via Dnsmasq-discuss
> wrote:
> >> > > Please name those different versions.
>
> >> On Tue, Mar 01, 2022 at 09:21:58AM -0800, Frank Liu wrote:
> >> > 2.76 (Debian 9),   2.85 (Debian 11).
>
> >On Tue, Mar 1, 2022 at 2:39 PM Geert Stappers via Dnsmasq-discuss
> >  wrote:
> >> Ah, I'm now beyond the ambiguty of different version of dig/nslookup.
>
> On 02.03.22 01:28, Frank Liu wrote:
> >I don't think it matters with test OS or test application.
>
> it may matter,
>
> >I also tried:
> >ping alias.dummy.example.com works, but ping alias.test.example.com gives
> >unknown host error.
> >(even though both names cname to the same client1.test.example.com in
> >dnsmasq).
>
> What do there result in?
>
> dig alias.dummy.example.com alias.test.example.com
> client1.test.example.com
> dig -t any alias.dummy.example.com alias.test.example.com
> client1.test.example.com
>
>
In below test, dnsmasq server (192.168.0.253) runs dnsmasq 2.85 (from
Debian11).
I have below in the dnsmasq conf:

cname=alias.test.example.com,client1.test.example.com
cname=alias.dummy.example.com,client1.test.example.com

Test client is another Debian11 box

$ dig -v
DiG 9.16.22-Debian

$ dig @192.168.0.253 alias.dummy.example.com alias.test.example.com
client1.test.example.com

; <<>> DiG 9.16.22-Debian <<>> @192.168.0.253 alias.dummy.example.com
alias.test.example.com client1.test.example.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 29718
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;alias.dummy.example.com. IN A

;; ANSWER SECTION:
alias.dummy.example.com. 0 IN CNAME client1.test.example.com.
client1.test.example.com. 0 IN A 192.168.0.70

;; Query time: 20 msec
;; SERVER: 192.168.0.253#53(192.168.0.253)
;; WHEN: Wed Mar 02 17:34:27 UTC 2022
;; MSG SIZE  rcvd: 114

;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 62870
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;alias.test.example.com. IN A

;; ANSWER SECTION:
alias.test.example.com. 5 IN CNAME client1.test.example.com.

;; Query time: 20 msec
;; SERVER: 192.168.0.253#53(192.168.0.253)
;; WHEN: Wed Mar 02 17:34:27 UTC 2022
;; MSG SIZE  rcvd: 96

;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 40301
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;client1.test.example.com. IN A

;; ANSWER SECTION:
client1.test.example.com. 5 IN A 192.168.0.70

;; Query time: 16 msec
;; SERVER: 192.168.0.253#53(192.168.0.253)
;; WHEN: Wed Mar 02 17:34:27 UTC 2022
;; MSG SIZE  rcvd: 75

$ dig -t any @192.168.0.253 alias.dummy.example.com alias.test.example.com
client1.test.example.com

; <<>> DiG 9.16.22-Debian <<>> -t any @192.168.0.253 alias.dummy.example.com
alias.test.example.com client1.test.example.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 24227
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;alias.dummy.example.com. IN ANY

;; ANSWER SECTION:
alias.dummy.example.com. 0 IN CNAME client1.test.example.com.
client1.test.example.com. 0 IN A 192.168.0.70

;; Query time: 20 msec
;; SERVER: 192.168.0.253#53(192.168.0.253)
;; WHEN: Wed Mar 02 17:34:41 UTC 2022
;; MSG SIZE  rcvd: 114

;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 12433
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT 

Re: [Dnsmasq-discuss] Does dnsmasq support cname within same domain?

[Matus UHLAR - fantomas via Dnsmasq-discuss]

> > On Tue, Mar 01, 2022 at 01:01:51AM -0800, Frank Liu wrote:
> > > I am running dnsmasq for dhcp/dns of a local test domain: 
test.example.com.
> > > Everything works fine. When a dhcp client (eg: client1) comes up, it gets
> > > the IP from dnsmasq, and I can dig/nslookup client1.test.example.com to 
get
> > > its IP.
> > >
> > > When I add a cname in the same domain, eg:
> > > cname=alias.test.example.com,client1.test.example.com
> > >
> > > dig/nslookup of alias.test.example.com only returns name
> > > client1.test.example.com, not the actual IP of client1.test.example.com
> > >
> > > It's interesting that if I add the cname for a different domain, eg:
> > > cname=alias.dummy.example.com,client1.test.example.com
> > >
> > > dig/nslookup of alias.dummy.example.com will return both name
> > > client1.test.example.com and its IP.
> > >
> > > I tried a few different versions but that doesn't make a difference.



> On Tue, Mar 1, 2022 at 3:37 AM Geert Stappers via Dnsmasq-discuss wrote:
> > Please name those different versions.



On Tue, Mar 01, 2022 at 09:21:58AM -0800, Frank Liu wrote:
> 2.76 (Debian 9),   2.85 (Debian 11).


On Tue, Mar 1, 2022 at 2:39 PM Geert Stappers via Dnsmasq-discuss 
 wrote:

Ah, I'm now beyond the ambiguty of different version of dig/nslookup.


On 02.03.22 01:28, Frank Liu wrote:

I don't think it matters with test OS or test application.


it may matter, 


I also tried:
ping alias.dummy.example.com works, but ping alias.test.example.com gives
unknown host error.
(even though both names cname to the same client1.test.example.com in
dnsmasq).


What do there result in?

dig alias.dummy.example.com alias.test.example.com client1.test.example.com
dig -t any alias.dummy.example.com alias.test.example.com 
client1.test.example.com



I tried ping from various machines (Mac, Windows, Debian 9, Debian11) on
the test network. Same result.

I also tried curl alias.test.example.com which gives: curl: (6) Could not
resolve host: alias.test.example.com
but curl alias.dummy.example.com works fine.


ping and curl are not tools for debugging DNS problems.


> > > Is this a known issue/limitation?
> >
> > What is the actual question?
> >
>
> Sorry, the question is in the email Subject. I guess it isn't clear, so I
> am pasting here:
> Does dnsmasq support cname within same domain?



I think it is more a dns-client problem as a dnsmasq problem.
As in: I don't yet understand the "problem".



Are you implicitly answering my question in the subject line with a "Yes"
answer, because if the answer is "no", there is really no need to
troubleshoot any further.


there seems to be no limitation of what you asked for, however if there's a 
problem, we should find it first.



--
Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
WinError #9: Out of error messages.

___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss

Re: [Dnsmasq-discuss] Does dnsmasq support cname within same domain?

[john doe]

On 3/2/2022 10:28 AM, Frank Liu wrote:

On Tue, Mar 1, 2022 at 2:39 PM Geert Stappers via Dnsmasq-discuss <
dnsmasq-discuss@lists.thekelleys.org.uk> wrote:


On Tue, Mar 01, 2022 at 09:21:58AM -0800, Frank Liu wrote:

On Tue, Mar 1, 2022 at 3:37 AM Geert Stappers via Dnsmasq-discuss wrote:

On Tue, Mar 01, 2022 at 01:01:51AM -0800, Frank Liu wrote:

Hi,

I am running dnsmasq for dhcp/dns of a local test domain:

test.example.com.

Everything works fine. When a dhcp client (eg: client1) comes up, it

gets

the IP from dnsmasq, and I can dig/nslookup client1.test.example.com

to get

its IP.

When I add a cname in the same domain, eg:
cname=alias.test.example.com,client1.test.example.com

dig/nslookup of alias.test.example.com only returns name
client1.test.example.com, not the actual IP of

client1.test.example.com


It's interesting that if I add the cname for a different domain, eg:
cname=alias.dummy.example.com,client1.test.example.com

dig/nslookup of alias.dummy.example.com will return both name
client1.test.example.com and its IP.

I tried a few different versions but that doesn't make a difference.


Please name those different versions.



2.76 (Debian 9),   2.85 (Debian 11).



Ah, I'm now beyond the ambiguty of different version of dig/nslookup.



I don't think it matters with test OS or test application.
I also tried:
ping alias.dummy.example.com works, but ping alias.test.example.com gives
unknown host error.
(even though both names cname to the same client1.test.example.com in
dnsmasq).

I tried ping from various machines (Mac, Windows, Debian 9, Debian11) on
the test network. Same result.

I also tried curl alias.test.example.com which gives: curl: (6) Could not
resolve host: alias.test.example.com
but curl alias.dummy.example.com works fine.







Is this a known issue/limitation?


What is the actual question?



Sorry, the question is in the email Subject. I guess it isn't clear, so I
am pasting here:
Does dnsmasq support cname within same domain?


:-)

I think it is more a dns-client problem as a dnsmasq problem.
As in: I don't yet understand the "problem".



Are you implicitly answering my question in the subject line with a "Yes"
answer, because if the answer is "no", there is really no need to
troubleshoot any further.



The only thing that I can say , is that, this OP is annoying
and was asked multiple times to respect the list and not to pollute it.

Personally, I ignore any trafic from 'Geert Stappers' x...@stapper.nl.

This person is not involved in anyway what so ever with this fine
project and Simon Kelley is maintaining Dnsmasq.

--
John Doe

___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss

Re: [Dnsmasq-discuss] Does dnsmasq support cname within same domain?

[Frank Liu]

On Tue, Mar 1, 2022 at 2:39 PM Geert Stappers via Dnsmasq-discuss <
dnsmasq-discuss@lists.thekelleys.org.uk> wrote:

> On Tue, Mar 01, 2022 at 09:21:58AM -0800, Frank Liu wrote:
> > On Tue, Mar 1, 2022 at 3:37 AM Geert Stappers via Dnsmasq-discuss wrote:
> > > On Tue, Mar 01, 2022 at 01:01:51AM -0800, Frank Liu wrote:
> > > > Hi,
> > > >
> > > > I am running dnsmasq for dhcp/dns of a local test domain:
> test.example.com.
> > > > Everything works fine. When a dhcp client (eg: client1) comes up, it
> gets
> > > > the IP from dnsmasq, and I can dig/nslookup client1.test.example.com
> to get
> > > > its IP.
> > > >
> > > > When I add a cname in the same domain, eg:
> > > > cname=alias.test.example.com,client1.test.example.com
> > > >
> > > > dig/nslookup of alias.test.example.com only returns name
> > > > client1.test.example.com, not the actual IP of
> client1.test.example.com
> > > >
> > > > It's interesting that if I add the cname for a different domain, eg:
> > > > cname=alias.dummy.example.com,client1.test.example.com
> > > >
> > > > dig/nslookup of alias.dummy.example.com will return both name
> > > > client1.test.example.com and its IP.
> > > >
> > > > I tried a few different versions but that doesn't make a difference.
> > >
> > > Please name those different versions.
> > >
> >
> > 2.76 (Debian 9),   2.85 (Debian 11).
>
>
> Ah, I'm now beyond the ambiguty of different version of dig/nslookup.
>

I don't think it matters with test OS or test application.
I also tried:
ping alias.dummy.example.com works, but ping alias.test.example.com gives
unknown host error.
(even though both names cname to the same client1.test.example.com in
dnsmasq).

I tried ping from various machines (Mac, Windows, Debian 9, Debian11) on
the test network. Same result.

I also tried curl alias.test.example.com which gives: curl: (6) Could not
resolve host: alias.test.example.com
but curl alias.dummy.example.com works fine.


>
>
>
> > > > Is this a known issue/limitation?
> > >
> > > What is the actual question?
> > >
> >
> > Sorry, the question is in the email Subject. I guess it isn't clear, so I
> > am pasting here:
> > Does dnsmasq support cname within same domain?
>
> :-)
>
> I think it is more a dns-client problem as a dnsmasq problem.
> As in: I don't yet understand the "problem".
>

Are you implicitly answering my question in the subject line with a "Yes"
answer, because if the answer is "no", there is really no need to
troubleshoot any further.

Frank
___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss