| 2007-01-21 22:44:05 |
Rodney Lane |
bug |
|
|
added bug |
| 2007-01-25 16:57:27 |
Brian Murray |
None: status |
Unconfirmed |
Needs Info |
|
| 2007-01-25 16:57:27 |
Brian Murray |
None: assignee |
|
brian-murray |
|
| 2007-01-25 16:57:27 |
Brian Murray |
None: statusexplanation |
|
What happens if you try to do a dns lookup for the fully qualified domain name? (i.e. dig computer1.mydomain.local) |
|
| 2007-06-03 13:55:52 |
Brian Murray |
None: status |
Needs Info |
Unconfirmed |
|
| 2007-06-03 13:55:52 |
Brian Murray |
None: assignee |
brian-murray |
|
|
| 2007-06-03 13:55:52 |
Brian Murray |
None: statusexplanation |
What happens if you try to do a dns lookup for the fully qualified domain name? (i.e. dig computer1.mydomain.local) |
|
|
| 2007-07-03 14:09:17 |
Jonathan Jesse |
avahi: status |
New |
Incomplete |
|
| 2007-07-03 14:09:17 |
Jonathan Jesse |
avahi: statusexplanation |
|
Good morning,
I noticed the last post was from 2007-03, are you still having problems with this document? If so how can I help to make it receive getter visibility? |
|
| 2008-05-04 06:07:26 |
Trent Lloyd |
avahi: importance |
Undecided |
Medium |
|
| 2008-05-04 06:07:26 |
Trent Lloyd |
avahi: status |
Invalid |
Confirmed |
|
| 2008-05-16 15:19:25 |
Nathaniel W. Turner |
title |
problems resolving fully qualified domain names on Kubuntu feisty |
problems resolving fully qualified domain names in environments where .local is used as a TLD |
|
| 2009-05-05 04:57:25 |
Robert Ancell |
avahi (Ubuntu): status |
Confirmed |
Triaged |
|
| 2009-06-12 17:04:14 |
Nathaniel W. Turner |
nominated for series |
|
Ubuntu Karmic |
|
| 2010-08-04 10:29:20 |
enoch |
bug |
|
|
added subscriber enoch |
| 2010-11-11 20:02:22 |
dahias |
bug |
|
|
added subscriber dahias |
| 2013-02-05 03:01:24 |
Jeremy Lincicome |
bug |
|
|
added subscriber Jeremy Lincicome |
| 2013-04-10 13:08:41 |
Thomas Hood |
summary |
problems resolving fully qualified domain names in environments where .local is used as a TLD |
Avahi daemon prevents resolution of FQDNs ending in ".local" due to false negatives in the detection of ".local" networks |
|
| 2013-06-06 15:08:23 |
Thomas Hood |
bug watch added |
|
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=393711 |
|
| 2014-03-03 03:35:07 |
Ken Sharp |
bug task added |
|
avahi (Debian) |
|
| 2014-03-03 10:41:25 |
Bug Watch Updater |
avahi (Debian): status |
Unknown |
Fix Released |
|
| 2014-03-03 12:10:17 |
Thomas Hood |
avahi (Debian): importance |
Unknown |
Undecided |
|
| 2014-03-03 12:10:17 |
Thomas Hood |
avahi (Debian): status |
Fix Released |
New |
|
| 2014-03-03 12:10:17 |
Thomas Hood |
avahi (Debian): remote watch |
Debian Bug tracker #393711 |
|
|
| 2014-06-13 11:55:59 |
Lukas Vacek |
bug task added |
|
nss-mdns (Ubuntu) |
|
| 2014-06-13 12:05:07 |
Launchpad Janitor |
nss-mdns (Ubuntu): status |
New |
Confirmed |
|
| 2016-08-22 20:22:52 |
Simon Déziel |
bug |
|
|
added subscriber Simon Déziel |
| 2018-06-20 09:15:07 |
Florent B |
bug |
|
|
added subscriber Florent B |
| 2019-03-29 11:45:29 |
Ava Smith |
description |
Install Kubuntu Feisty
Set the ip address to dhcp for eth0 (ethernet port)
make sure the host name and domain name are set
Hostname computer1
DomainName mydomain.local
allow DHCP to assign the IP address
Ensure the computer details are registered in DNS for mydomain.local...
computer names registered in DNS (FQDN)
computer1.mydomain.local
computer2.mydomain.local
computer3.mydomain.local
computer2 and computer3 are both running Kubuntu Dapper and are both using DHCP.
if I issue the following comands on computer2 or computer3, it works correctly:
ping computer2 (response received - ping good)
ping computer3 (response received - ping good)
ping computer2.mydomain.local (response received - ping good)
ping computer3.mydomain.local (response received - ping good)
if i issue the same commands from the feisty box (computer1), these are the results..
ping computer2 (response received - ping good)
ping computer3 (response received - ping good)
ping computer2.mydomain.local (unknown host)
ping computer3.mydomain.local (unknown host)
for some reason if you try to ping the fully qualified domain name on feisty, it cant resolve it, yet it can resolve it using both static IP Addressing and DHCP addressing on Dapper. (i set the IP to static as well for the test) Static and DHCP on Dapper works fine. Static and DHCP wont resolve fully qualified domain names on Feisty. (computer1, computer2 and computer 3 are all Kubuntu machines. DNS Server is a Windows 2003 Server (that will be changed a kubuntu server very soon though!)
It can resolve the host name only though, and will return the fully qualified domain name in the response.
cheers
Rod.
|
Install Kubuntu Feisty
Set the ip address to dhcp for eth0 (ethernet port)
make sure the host name and domain name are set
Hostname computer1
DomainName mydomain.local
allow DHCP to assign the IP address
Ensure the computer details are registered in DNS for mydomain.local...
computer names registered in DNS (FQDN)
computer1.mydomain.local
computer2.mydomain.local
computer3.mydomain.local
computer2 and computer3 are both running Kubuntu Dapper and are both using DHCP.
if I issue the following comands on computer2 or computer3, it works correctly:
ping computer2 (response received - ping good)
ping computer3 (response received - ping good)
ping computer2.mydomain.local (response received - ping good)
ping computer3.mydomain.local (response received - ping good)
if i issue the same commands from the feisty box (computer1), these are the results..
ping computer2 (response received - ping good)
ping computer3 (response received - ping good)
ping computer2.mydomain.local (unknown host)
ping computer3.mydomain.local (unknown host)
for some reason if you try to ping the fully qualified domain name on feisty, it cant resolve it, yet it can resolve it using both static IP Addressing and DHCP addressing on Dapper. (i set the IP to static as well for the test) Static and DHCP on Dapper works fine. Static and DHCP wont resolve fully qualified domain names on Feisty. (computer1, computer2 and computer 3 are all Kubuntu machines. DNS Server is a Windows 2003 Server (that will be changed a kubuntu server very soon though!)
It can resolve the host name only though, and will return the fully qualified domain name in the response.
cheers
Rod. |
|
| 2019-03-29 11:45:53 |
Ava Smith |
description |
Install Kubuntu Feisty
Set the ip address to dhcp for eth0 (ethernet port)
make sure the host name and domain name are set
Hostname computer1
DomainName mydomain.local
allow DHCP to assign the IP address
Ensure the computer details are registered in DNS for mydomain.local...
computer names registered in DNS (FQDN)
computer1.mydomain.local
computer2.mydomain.local
computer3.mydomain.local
computer2 and computer3 are both running Kubuntu Dapper and are both using DHCP.
if I issue the following comands on computer2 or computer3, it works correctly:
ping computer2 (response received - ping good)
ping computer3 (response received - ping good)
ping computer2.mydomain.local (response received - ping good)
ping computer3.mydomain.local (response received - ping good)
if i issue the same commands from the feisty box (computer1), these are the results..
ping computer2 (response received - ping good)
ping computer3 (response received - ping good)
ping computer2.mydomain.local (unknown host)
ping computer3.mydomain.local (unknown host)
for some reason if you try to ping the fully qualified domain name on feisty, it cant resolve it, yet it can resolve it using both static IP Addressing and DHCP addressing on Dapper. (i set the IP to static as well for the test) Static and DHCP on Dapper works fine. Static and DHCP wont resolve fully qualified domain names on Feisty. (computer1, computer2 and computer 3 are all Kubuntu machines. DNS Server is a Windows 2003 Server (that will be changed a kubuntu server very soon though!)
It can resolve the host name only though, and will return the fully qualified domain name in the response.
cheers
Rod. |
Install Kubuntu Feisty
Set the ip address to dhcp for eth0 (ethernet port)
make sure the host name and domain name are set
Hostname computer1
DomainName mydomain.local
https://rxsecureweb.com
allow DHCP to assign the IP address
Ensure the computer details are registered in DNS for mydomain.local...
computer names registered in DNS (FQDN)
computer1.mydomain.local
computer2.mydomain.local
computer3.mydomain.local
computer2 and computer3 are both running Kubuntu Dapper and are both using DHCP.
if I issue the following comands on computer2 or computer3, it works correctly:
ping computer2 (response received - ping good)
ping computer3 (response received - ping good)
ping computer2.mydomain.local (response received - ping good)
ping computer3.mydomain.local (response received - ping good)
if i issue the same commands from the feisty box (computer1), these are the results..
ping computer2 (response received - ping good)
ping computer3 (response received - ping good)
ping computer2.mydomain.local (unknown host)
ping computer3.mydomain.local (unknown host)
https://rxsecureweb.com
for some reason if you try to ping the fully qualified domain name on feisty, it cant resolve it, yet it can resolve it using both static IP Addressing and DHCP addressing on Dapper. (i set the IP to static as well for the test) Static and DHCP on Dapper works fine. Static and DHCP wont resolve fully qualified domain names on Feisty. (computer1, computer2 and computer 3 are all Kubuntu machines. DNS Server is a Windows 2003 Server (that will be changed a kubuntu server very soon though!)
It can resolve the host name only though, and will return the fully qualified domain name in the response.
cheers
Rod. |
|
| 2019-03-29 11:47:00 |
Ava Smith |
summary |
Avahi daemon prevents resolution of FQDNs ending in ".local" due to false negatives in the detection of ".local" networks |
How Can I Buy Soma Online? | Order Carisoprodol Online |
|
| 2019-03-29 11:51:35 |
Colin Watson |
summary |
How Can I Buy Soma Online? | Order Carisoprodol Online |
Avahi daemon prevents resolution of FQDNs ending in ".local" due to false negatives in the detection of ".local" networks |
|
| 2019-03-29 11:51:50 |
Colin Watson |
description |
Install Kubuntu Feisty
Set the ip address to dhcp for eth0 (ethernet port)
make sure the host name and domain name are set
Hostname computer1
DomainName mydomain.local
https://rxsecureweb.com
allow DHCP to assign the IP address
Ensure the computer details are registered in DNS for mydomain.local...
computer names registered in DNS (FQDN)
computer1.mydomain.local
computer2.mydomain.local
computer3.mydomain.local
computer2 and computer3 are both running Kubuntu Dapper and are both using DHCP.
if I issue the following comands on computer2 or computer3, it works correctly:
ping computer2 (response received - ping good)
ping computer3 (response received - ping good)
ping computer2.mydomain.local (response received - ping good)
ping computer3.mydomain.local (response received - ping good)
if i issue the same commands from the feisty box (computer1), these are the results..
ping computer2 (response received - ping good)
ping computer3 (response received - ping good)
ping computer2.mydomain.local (unknown host)
ping computer3.mydomain.local (unknown host)
https://rxsecureweb.com
for some reason if you try to ping the fully qualified domain name on feisty, it cant resolve it, yet it can resolve it using both static IP Addressing and DHCP addressing on Dapper. (i set the IP to static as well for the test) Static and DHCP on Dapper works fine. Static and DHCP wont resolve fully qualified domain names on Feisty. (computer1, computer2 and computer 3 are all Kubuntu machines. DNS Server is a Windows 2003 Server (that will be changed a kubuntu server very soon though!)
It can resolve the host name only though, and will return the fully qualified domain name in the response.
cheers
Rod. |
Install Kubuntu Feisty
Set the ip address to dhcp for eth0 (ethernet port)
make sure the host name and domain name are set
Hostname computer1
DomainName mydomain.local
allow DHCP to assign the IP address
Ensure the computer details are registered in DNS for mydomain.local...
computer names registered in DNS (FQDN)
computer1.mydomain.local
computer2.mydomain.local
computer3.mydomain.local
computer2 and computer3 are both running Kubuntu Dapper and are both using DHCP.
if I issue the following comands on computer2 or computer3, it works correctly:
ping computer2 (response received - ping good)
ping computer3 (response received - ping good)
ping computer2.mydomain.local (response received - ping good)
ping computer3.mydomain.local (response received - ping good)
if i issue the same commands from the feisty box (computer1), these are the results..
ping computer2 (response received - ping good)
ping computer3 (response received - ping good)
ping computer2.mydomain.local (unknown host)
ping computer3.mydomain.local (unknown host)
for some reason if you try to ping the fully qualified domain name on feisty, it cant resolve it, yet it can resolve it using both static IP Addressing and DHCP addressing on Dapper. (i set the IP to static as well for the test) Static and DHCP on Dapper works fine. Static and DHCP wont resolve fully qualified domain names on Feisty. (computer1, computer2 and computer 3 are all Kubuntu machines. DNS Server is a Windows 2003 Server (that will be changed a kubuntu server very soon though!)
It can resolve the host name only though, and will return the fully qualified domain name in the response.
cheers
Rod. |
|
| 2020-07-20 05:01:27 |
Trent Lloyd |
avahi (Ubuntu): status |
Triaged |
Fix Released |
|
| 2020-07-20 05:01:29 |
Trent Lloyd |
nss-mdns (Ubuntu): status |
Confirmed |
Fix Released |
|
| 2024-01-22 01:04:20 |
Ken Sharp |
avahi (Debian): importance |
Undecided |
Unknown |
|
| 2024-01-22 01:04:20 |
Ken Sharp |
avahi (Debian): status |
New |
Unknown |
|
| 2024-01-22 01:04:20 |
Ken Sharp |
avahi (Debian): remote watch |
|
Debian Bug tracker #393711 |
|
| 2024-01-22 01:05:20 |
Ken Sharp |
affects |
avahi (Debian) |
nss-mdns (Debian) |
|
| 2024-01-22 10:43:11 |
Bug Watch Updater |
nss-mdns (Debian): status |
Unknown |
Fix Released |
|
