[Bug 1771353] Re: Server feature level is now lower than when we began our transaction. Restarting with new ID

[Steve Dodd]

I'm see this just trying to resolve names on my local LAN:

Aug 02 17:50:40 beelink systemd-resolved[6697]: Processing incoming packet on transaction 52812. (rcode=SUCCESS)
Aug 02 17:50:40 beelink systemd-resolved[6697]: Server doesn't support EDNS(0) properly, downgrading feature level...
Aug 02 17:50:40 beelink systemd-resolved[6697]: Using degraded feature set (UDP) for DNS server 192.168.128.32.
Aug 02 17:50:40 beelink systemd-resolved[6697]: Server feature level is now lower than when we began our transaction. Restarting with new ID.
Aug 02 17:50:40 beelink systemd-resolved[6697]: Transaction 52812 is now 18875.
Aug 02 17:50:40 beelink systemd-resolved[6697]: Cache miss for xu-host.lan IN AAAA
Aug 02 17:50:40 beelink systemd-resolved[6697]: Transaction 18875 for <xu-host.lan IN AAAA> scope dns on lan0/*.
Aug 02 17:50:40 beelink systemd-resolved[6697]: Using feature level UDP+EDNS0 for transaction 18875.
Aug 02 17:50:40 beelink systemd-resolved[6697]: Sending query packet with id 18875.
Aug 02 17:50:40 beelink systemd-resolved[6697]: Processing incoming packet on transaction 18875. (rcode=SUCCESS)
Aug 02 17:50:40 beelink systemd-resolved[6697]: Server feature level is now lower than when we began our transaction. Restarting with new ID.
Aug 02 17:50:40 beelink systemd-resolved[6697]: Transaction 18875 is now 44944.
Aug 02 17:50:40 beelink systemd-resolved[6697]: Cache miss for xu-host.lan IN AAAA
Aug 02 17:50:40 beelink systemd-resolved[6697]: Transaction 44944 for <xu-host.lan IN AAAA> scope dns on lan0/*.
Aug 02 17:50:40 beelink systemd-resolved[6697]: Using feature level UDP+EDNS0 for transaction 44944.
Aug 02 17:50:40 beelink systemd-resolved[6697]: Sending query packet with id 44944.
Aug 02 17:50:40 beelink systemd-resolved[6697]: Processing incoming packet on transaction 44944. (rcode=SUCCESS)
Aug 02 17:50:40 beelink systemd-resolved[6697]: Server feature level is now lower than when we began our transaction. Restarting with new ID.
Aug 02 17:50:40 beelink systemd-resolved[6697]: Transaction 44944 is now 42801.
Aug 02 17:50:40 beelink systemd-resolved[6697]: Cache miss for xu-host.lan IN AAAA
Aug 02 17:50:40 beelink systemd-resolved[6697]: Transaction 42801 for <xu-host.lan IN AAAA> scope dns on lan0/*.
Aug 02 17:50:40 beelink systemd-resolved[6697]: Using feature level UDP+EDNS0 for transaction 42801.
Aug 02 17:50:40 beelink systemd-resolved[6697]: Sending query packet with id 42801.
Aug 02 17:50:40 beelink systemd-resolved[6697]: Processing incoming packet on transaction 42801. (rcode=SUCCESS)
Aug 02 17:50:40 beelink systemd-resolved[6697]: Server feature level is now lower than when we began our transaction. Restarting with new ID.

Upstream DNS is a probably fairly ancient version of dnsmasq..

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1771353

Title:
  Server feature level is now lower than when we began our transaction.
  Restarting with new ID

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  systemd 237-3ubuntu10 from bionic

  There is no /etc/netplan/* file.

  I'm getting some sort of a loop when systemd-resolved tries to resolve
  the hostname of my canonistack instance:

  ubuntu at bip:~$ systemd-resolve bip.lcy02.canonistack
  bip.lcy02.canonistack: resolve call failed: All attempts to contact name servers or networks failed

  systemd-resolved debug output loops over like this:
  Transaction 36341 is now 19121.
  Cache miss for bip.lcy02.canonistack IN A
  Transaction 19121 for <bip.lcy02.canonistack IN A> scope dns on */*.
  Using feature level UDP+EDNS0 for transaction 19121.
  Sending query packet with id 19121.
  Processing incoming packet on transaction 19121. (rcode=SUCCESS)
  Server feature level is now lower than when we began our transaction. Restarting with new ID.
  Transaction 19121 is now 17157.
  Cache miss for bip.lcy02.canonistack IN A
  Transaction 17157 for <bip.lcy02.canonistack IN A> scope dns on */*.
  Using feature level UDP+EDNS0 for transaction 17157.
  Sending query packet with id 17157.
  Processing incoming packet on transaction 17157. (rcode=SUCCESS)
  Server feature level is now lower than when we began our transaction. Restarting with new ID.
  ...

  Packet capture shows a loop like this:
  13:38:32.293524 IP 10.55.32.54.53786 > 10.55.32.1.53: 46096+ [1au] A? bip.lcy02.canonistack. (50)
  13:38:32.293753 IP 10.55.32.1.53 > 10.55.32.54.53786: 46096* 1/0/0 A 10.55.32.54 (55)
  13:38:32.294026 IP 10.55.32.54.53786 > 10.55.32.1.53: 64494+ [1au] A? bip.lcy02.canonistack. (50)
  13:38:32.294249 IP 10.55.32.1.53 > 10.55.32.54.53786: 64494* 1/0/0 A 10.55.32.54 (55)

  I'm going to attach the full debug output, and the pcap file.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1771353/+subscriptions