*** This bug is a duplicate of bug 80900 ***
https://bugs.launchpad.net/bugs/80900
** This bug has been marked a duplicate of bug 80900
problems resolving fully qualified domain names in environments where .local
is used as a TLD
--
You received this bug notification because you are a me
This bug is a duplicate of bug #80900
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1114948
Title:
unable to access server on lan by hostname on wi-fi
To manage notifications about this bug go to:
** Changed in: resolvconf (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1114948
Title:
unable to access server on lan by hostname on wi-fi
To mana
@Thomas,
Editing nsswitch.conf fixed the issue. Thank you very much for your help. How
should I mark this bug?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1114948
Title:
unable to access server o
Is your problem bug #80900? Does editing /etc/nsswitch.conf so that it
contains
hosts: files dns mdns
fix it?
** Changed in: resolvconf (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
Is you problem bug #80900. Does editing /etc/nsswitch.conf so that it
contains
hosts: files dns mdns
fix it?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1114948
Title:
unable to access serve
@Jeremy: Is your problem bug #1083565?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1114948
Title:
unable to access server on lan by hostname on wi-fi
To manage notifications about this bug go to:
I have 2 other laptops on my network. Both of them can access
server.local just fine. Mine seams to be the only one effected. I didn't
have any issues until after resolvconf got updated.
** Changed in: resolvconf (Ubuntu)
Status: Invalid => New
--
You received this bug notification becaus
.local is using avahi which relies on working multicast.
Changes are that your wifi is somehow breaking multicast leading to resolution
failure.
If .local is actually operated by an actual DNS server and not through
avahi, then you should move away from .local and use anything else.
I'm marking
@Thomas,
The output in my last comment was while using wi-fi. Would you like the same
thing with an ethernet cable pluged in?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1114948
Title:
unable to
@thomas,
Here's the output you asked for.
Code:
ping: unknown host server.local
jeremy@jeremy-HP-Pavilion-dm1-Notebook-PC:~$ host server.local
Host server.local not found: 3(NXDOMAIN)
jeremy@
jeremy@jeremy-HP-Pavilion-dm1-Notebook-PC:~$ dig server.local
; <<>> DiG 9.8.1-P1 <<>> server.local
;; glo
@Jeremy: Hi, and thanks for the report. Please provide more information
by taking the following steps.
* Reboot
* Log in and open a terminal
* In the terminal, run the following commands with the name of your server
replacing 'XYZ'.
ping XYZ
host XYZ
dig XYZ
ls -l /etc/resolv.con
12 matches
Mail list logo
