[Bug 1947455] Re: sub sub domain names not properly resolved
I had other network hostname issues. google lead me to a file called /etc/nsswitch.conf I replaced a line from a other linux box `hosts: files mdns4_minimal [NOTFOUND=return] dns` resolving all my issues. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947455 Title: sub sub domain names not properly resolved To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1947455/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947455] Re: sub sub domain names not properly resolved
** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947455 Title: sub sub domain names not properly resolved To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1947455/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947455] Re: sub sub domain names not properly resolved
** Changed in: bind9 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947455 Title: sub sub domain names not properly resolved To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1947455/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947455] Re: sub sub domain names not properly resolved
apparently nothing happens when no package is selected. I dont know the package. i did apt search nslookup and added the associated package. IRC tells me to add network-manager that is what im going to do -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947455 Title: sub sub domain names not properly resolved To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1947455/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947455] Re: sub sub domain names not properly resolved
** Also affects: bind9 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947455 Title: sub sub domain names not properly resolved To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1947455/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947455] [NEW] sub sub domain names not properly resolved
Public bug reported: I have a local lan with a libvirt server and on that a vpn I have a wildcard sub domain at freedns.afraid.org (sub.hostname.com) that has a kvm and vpn sub sub domain names. (sub.sub.hostname.com) If i ping the sub sub hostname outside my local lan i get my external IP address. but also if i ping from within my local lan network dig and nslookup do a resolve to my local ip. But ping and applications like openvpn and libvirt cant connect to the local application. I worked around it by registering two sub domains at freedns.afraid.org those are resolved correctly to the local IP address. No logs due to privacy. ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947455 Title: sub sub domain names not properly resolved To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1947455/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947455] Re: sub sub domain names not properly resolved
O yes. this bug appeared in 21.10 before that it was working -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947455 Title: sub sub domain names not properly resolved To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1947455/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947364] Re: mt76 module disagrees on a lot
Well Issue does not appear when you make a clean installation. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947364 Title: mt76 module disagrees on a lot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947364/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947364] [NEW] mt76 module disagrees on a lot
Public bug reported: I had a 20.10 beta live cd with working wifi and bluetooth. (both use the same chipset) I upgraded to 20.10 and wifi is not working. bluetooth is. Description:Ubuntu 21.10 Release:21.10 after a modprobe mt76. the system returns: modprobe: ERROR: could not insert 'mt76': Invalid argument there is a lot of disagreeing in dmesg. [ 212.499500] mt76: disagrees about version of symbol ieee80211_sta_register_airtime [ 212.499506] mt76: Unknown symbol ieee80211_sta_register_airtime (err -22) [ 212.499550] mt76: disagrees about version of symbol __ieee80211_schedule_txq [ 212.499551] mt76: Unknown symbol __ieee80211_schedule_txq (err -22) [ 212.499609] mt76: disagrees about version of symbol ieee80211_free_hw [ 212.499610] mt76: Unknown symbol ieee80211_free_hw (err -22) [ 212.499661] mt76: disagrees about version of symbol ieee80211_txq_schedule_start [ 212.499664] mt76: Unknown symbol ieee80211_txq_schedule_start (err -22) [ 212.499685] mt76: disagrees about version of symbol ieee80211_tx_status_ext [ 212.499687] mt76: Unknown symbol ieee80211_tx_status_ext (err -22) [ 212.499714] mt76: disagrees about version of symbol ieee80211_register_hw [ 212.499716] mt76: Unknown symbol ieee80211_register_hw (err -22) [ 212.499794] mt76: disagrees about version of symbol __ieee80211_create_tpt_led_trigger [ 212.499797] mt76: Unknown symbol __ieee80211_create_tpt_led_trigger (err -22) [ 212.499828] mt76: disagrees about version of symbol ieee80211_sta_eosp [ 212.499829] mt76: Unknown symbol ieee80211_sta_eosp (err -22) [ 212.499841] mt76: disagrees about version of symbol ieee80211_get_hdrlen_from_skb [ 212.499842] mt76: Unknown symbol ieee80211_get_hdrlen_from_skb (err -22) [ 212.499900] mt76: disagrees about version of symbol ieee80211_get_tx_rates [ 212.499901] mt76: Unknown symbol ieee80211_get_tx_rates (err -22) [ 212.499907] mt76: disagrees about version of symbol ieee80211_send_bar [ 212.499908] mt76: Unknown symbol ieee80211_send_bar (err -22) [ 212.499925] mt76: disagrees about version of symbol ieee80211_sta_uapsd_trigger [ 212.499926] mt76: Unknown symbol ieee80211_sta_uapsd_trigger (err -22) [ 212.499976] mt76: disagrees about version of symbol ieee80211_queue_delayed_work [ 212.499977] mt76: Unknown symbol ieee80211_queue_delayed_work (err -22) [ 212.52] mt76: disagrees about version of symbol ieee80211_calc_rx_airtime [ 212.53] mt76: Unknown symbol ieee80211_calc_rx_airtime (err -22) [ 212.500012] mt76: disagrees about version of symbol ieee80211_find_sta_by_ifaddr [ 212.500013] mt76: Unknown symbol ieee80211_find_sta_by_ifaddr (err -22) [ 212.500019] mt76: disagrees about version of symbol ieee80211_next_txq [ 212.500020] mt76: Unknown symbol ieee80211_next_txq (err -22) [ 212.500032] mt76: disagrees about version of symbol ieee80211_beacon_cntdwn_is_complete [ 212.500034] mt76: Unknown symbol ieee80211_beacon_cntdwn_is_complete (err -22) [ 212.500041] mt76: disagrees about version of symbol ieee80211_sta_pspoll [ 212.500042] mt76: Unknown symbol ieee80211_sta_pspoll (err -22) [ 212.500061] mt76: disagrees about version of symbol ieee80211_free_txskb [ 212.500062] mt76: Unknown symbol ieee80211_free_txskb (err -22) [ 212.500075] mt76: disagrees about version of symbol ieee80211_alloc_hw_nm [ 212.500076] mt76: Unknown symbol ieee80211_alloc_hw_nm (err -22) [ 212.500086] mt76: disagrees about version of symbol ieee80211_tx_dequeue [ 212.500087] mt76: Unknown symbol ieee80211_tx_dequeue (err -22) [ 212.500092] mt76: disagrees about version of symbol ieee80211_rx_list [ 212.500093] mt76: Unknown symbol ieee80211_rx_list (err -22) [ 212.500116] mt76: disagrees about version of symbol ieee80211_tx_status [ 212.500117] mt76: Unknown symbol ieee80211_tx_status (err -22) [ 212.500141] mt76: disagrees about version of symbol ieee80211_iterate_active_interfaces_atomic [ 212.500143] mt76: Unknown symbol ieee80211_iterate_active_interfaces_atomic (err -22) [ 212.500158] mt76: disagrees about version of symbol ieee80211_unregister_hw [ 212.500159] mt76: Unknown symbol ieee80211_unregister_hw (err -22) [ 212.500177] mt76: disagrees about version of symbol ieee80211_sta_ps_transition [ 212.500179] mt76: Unknown symbol ieee80211_sta_ps_transition (err -22) [ 212.500193] mt76: disagrees about version of symbol ieee80211_csa_finish [ 212.500194] mt76: Unknown symbol ieee80211_csa_finish (err -22) lspci 00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne Root Complex 00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne IOMMU 00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe Dummy Host Bridge 00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe Dummy Host Bridge 00:02.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne PCIe GPP Bridge 00:02.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne PCIe GPP Bridge 00:02.3 PCI
