Re: [Blink] Blink Ubuntu DNS lookup deadlock?

It's really strange. It worked for quite a while. But now again it started to stall because of this DNS issue... Adding a static outbound proxy fixed it though - thanks again for this hint. @Adrian: Can you elaborate a bit why in your opinion this CNAME is not allowed? It's for a subdomain,

Re: [Blink] Blink Ubuntu DNS lookup deadlock?

Hi, when it didn't work, I restarted Blink several times, so the lifetime shouldn't be the reason in my case... As soon I have this problem again I will do a more thorough analyse of the DNS packets received. Thanks for the hint with the proxy and port settings. This should solve the

Re: [Blink] Blink Ubuntu DNS lookup deadlock?

I guess you mean voipgateway.org as root domain, not the '.' domain above TLDs... I don't see an issue here. The idea of CNAME is to point to other names. They don't have to be in the same zone file. guest1.voipgateway.org points to ws1.voipgateway.org so this is even the same domain.

Re: [Blink] Blink Ubuntu DNS lookup deadlock?

CNAME on the root domain is not allowed in DNS. Each resolver may yield a different result when coping to this anomaly. As a start, just remove it and we can look at what happens afterwards. Adrian > On 30 Nov 2022, at 14:17, g4-l...@tonarchiv.ch wrote: > > It's really strange, right now it's

Re: [Blink] Blink Ubuntu DNS lookup deadlock?

Hi AFIAK you should always get that it ignores the CNAME. Why it sometimes behaves different I can’t tell. I run a test script here and I got it always, unless the lifetime of the resolver was reached. Then I got timeouts. So it could be that you’re hitting a timeout or a lifecycle timeout of

Re: [Blink] Blink Ubuntu DNS lookup deadlock?

It's really strange, right now it's working but I don't know what has changed. Again I did some network sniffing on port 53 and it seems a bit random how Blink is reacting to the DNS replies: Sometimes it simply ignores the CNAME answer to the NAPTR and doesn't send a request for

Re: [Blink] Blink Ubuntu DNS lookup deadlock?

Hi thank you for your replies. I'm a bit more familiar with DNS than with VOIP... If I get it right the NAPTR is optional and SIP should work without it. CNAME can always be a reply to a DNS lookup, it just means: The name you are looking for is an alias, i.e. guest1.voipgateway.org is a

Re: [Blink] Blink Ubuntu DNS lookup deadlock?

$dig cname guest1.voipgateway.org ;; QUESTION SECTION: ;guest1.voipgateway.org.IN CNAME ;; ANSWER SECTION: guest1.voipgateway.org. 21600 IN CNAME ws1.voipgateway.org. The CNAME should not be there for the domain name. — Adrian > On 30 Nov 2022, at 07:15,

Re: [Blink] Blink Ubuntu DNS lookup deadlock?

Hi, I looked at it a bit more and the fact that a CNAME is returned could happen. However in my Blink I can’t reproduce this fault, I used the domain guest1.voipgateway.org and I could register(?), if I made a call I got a prompt. This is how my logs look:

Re: [Blink] Blink Ubuntu DNS lookup deadlock?

Hi, The fact that you see the timeouts could be a bug. The problem is that a NAPTR does exist and is a CNAME? I’ve never seen this and I am not sure this is even valid in DNS. AFAIK a NAPTR in this case should return something like: 20 100 "s" "SIP+D2U" "" _sip._udp.sip2sip.info. 10 100 "s"

[Blink] Blink Ubuntu DNS lookup deadlock?

Hi there A few days ago I updated my OS to Pop! OS / Ubuntu 22.04 LTS with the Blink flatpack V5.5.0 A few times it worked flawlessly, but most of the time, starting a call lags a lot and it simply fails with a beep after a few minutes without any further message. The logs shows issues