Marking as confirmed. This is a known issue.
Unfortunately the .local detection script does not work if no root
local. domain exists. A possible fix may be to have libnss-mdns not
lookup .local hosts with more than 2 labels i.e. lookup test.local but
not machine.test.local
Seems all MS
Seems all MS networks always will use host-names in the form of
host.DOMAIN.local correct?
I'm not sure that will *always* be the case, but it has been the case in
every local domain I've ever seen. Your fix sounds good to me.
--
problems resolving fully qualified domain names on Kubuntu
Looks like turning it off is the best fix for now.
You can go under SystemAdministrationServices
Then Uncheck Multicast DNS service Discovery (avahi-daemon)
--
problems resolving fully qualified domain names on Kubuntu feisty
https://bugs.launchpad.net/bugs/80900
You received this bug
Hi,
The problem is that on a large network avahi plays a large role in finding
shares and printers. It makes this a lot more difficult to shut it down.
Dominic
On 11/9/07, slyride [EMAIL PROTECTED] wrote:
Looks like turning it off is the best fix for now.
You can go under
Ok, I spent the last WEEK trying to figure out what was going on before
stumbling on this thread. I consult for a school with 500 machines using
the Microsoft recommended .local domain name.
So what's the fix? Turn off avahi permanently?
--
problems resolving fully qualified domain names on
The bigger problem in large organizations is that the use of domain
names ending in .local is the recommendation from Microsoft for server
2000 and 2003 configurations. It's also well documented in other
places.
It's unfortunate that .local was chosen for mDNS. In many cases, (mine
included),
[Expired for avahi (Ubuntu) because there has been no activity for 60
days.]
--
problems resolving fully qualified domain names on Kubuntu feisty
https://bugs.launchpad.net/bugs/80900
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
I can confirm this problem on feisty (7.05). avahi should really warn
about this. You swear a lot 'wtf?!?' until you get the idea that avahi
is the problem.
See
http://www.avahi.org/wiki/AvahiAndUnicastDotLocal
(includes a suggestion for package maintainers)
And sadly
I am having this issue on Feisty and found this bug thread today.
avahi-daemon 0.6.17
When I stop the avahi-daemon using:
sudo avahi-daemon -k
I am able to ping things.mydomain.local
When I start it again using:
sudo avahi-daemon -D
pings to things.mydomain.local stop working.
--
problems
This problem still exists in Gutsy Tribe 5.
--
problems resolving fully qualified domain names on Kubuntu feisty
https://bugs.launchpad.net/bugs/80900
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
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?
** Changed in: avahi (Ubuntu)
Status: New = Incomplete
--
problems resolving fully qualified domain names on Kubuntu
I renamed my internal DNS to avoind the conflict. Others may still have
the problem though.
--
problems resolving fully qualified domain names on Kubuntu feisty
https://bugs.launchpad.net/bugs/80900
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
** Changed in: avahi (Ubuntu)
Sourcepackagename: None = avahi
Assignee: Brian Murray = (unassigned)
Status: Needs Info = Unconfirmed
--
problems resolving fully qualified domain names on Kubuntu feisty
https://bugs.launchpad.net/bugs/80900
You received this bug notification because
I have this same problem on 7.04 beta.
Avahi uses the .local as its SOA. Because you use it internally avahi causes
conflict.
What should happen is that avahi should warn you that you are using
.local as part of yout fqdn and offer to disable itself in a bubble.
For now, I have changed my
Ok, just disabled avahi through network configuration tool...
Now i can access my local ftp/http server with fqdn again! Ping does
also work again!
Don't know anything about avahi, but deactivated it seems to be a
working workaround.
Hope that someone with detailed information about avahi could
$ host -t soa local
Host local not found: 3(NXDOMAIN)
zigford, are you sure that this command is correct? host tries to
interpret local as hostname.
$ host -t soa hostname
hostname.domain.local has no SOA record
I am using dnsmasq as dns server (look at one of my previous posts for
more
Okay, I have changed to jspeed.private as my tld
When I go host -t soa private
I get:
chichi:~ harrisj$ host -t soa private
Host private not found: 3(NXDOMAIN)
chichi:~ harrisj$
When I go host -s soa jspeed.private
I get:
chichi:~ harrisj$ host -t soa jspeed.private
jspeed.private has SOA
Rod, Michael,
Can you run host -t soa local
and post back the results?
--
problems resolving fully qualified domain names on Kubuntu feisty
https://launchpad.net/bugs/80900
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Could someone else test/confirm whether that is avahi related? (look at
my previous post)
--
problems resolving fully qualified domain names on Kubuntu feisty
https://launchpad.net/bugs/80900
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
I have the same problem.
DNS/DHCP Server: Linksys WRT54G router with DD-WRT Firmware (dnsmasq as
dhcp/dns server)
Client Computers (OS): Edgy, Feisty (fresh install, updates installed)
network-manager is connecting through dhcp (search domain is automatically
defined in resolv.conf)
In feisty
On my Feisty install I don't have any problems resolving fully qualified
domain names.
--
problems resolving fully qualified domain names on Kubuntu feisty
https://launchpad.net/bugs/80900
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Are the fully qualified domain names names that are the same as your
computers domain name? I can resolve domain names that are not a part of
my local domain, ie, www.kubuntu.org resolves fine, its just when you
try to resolve fully qualified domain names when the domain name is the
same as the
Using NSLookup works fine for both computer1 and
computer1.mydomain.local
Its only if I try to ping or resolve the FQDN in a shell or app other
than nslookup.
--
problems resolving fully qualified domain names on Kubuntu feisty
https://launchpad.net/bugs/80900
--
ubuntu-bugs mailing list
What happens if you try to do a dns lookup for the fully qualified
domain name? (i.e. dig computer1.mydomain.local)
** Changed in: Ubuntu
Assignee: (unassigned) = Brian Murray
Status: Unconfirmed = Needs Info
--
problems resolving fully qualified domain names on Kubuntu feisty
24 matches
Mail list logo
