| 2008-10-30 16:38:39 |
João Pinto |
bug |
|
|
added bug |
| 2008-10-30 16:40:19 |
João Pinto |
description |
#@NETVPN_GENERATED@ -- this file is generated by NetVPN
# and will be overwritten by NetVPN
# as long as the above mark is intact
nameserver 127.0.0.1
nameserver 127.0.0.1
# Generated by NetworkManager
domain local.domain.com br.somewhere.com somewhere.com
search local.domain.com
nameserver 127.0.0.1
nameserver 127.0.0.1
nameserver 127.0.0.1
The file was not edited manually, it was generated by NM and the AT&T VPN Client.
I have changed the IPs/Domains for privacy reasons.
Thanks |
I am getting the following error using nslookup:
nslookup: parse of /etc/resolv.conf failed
The file was not edited manually, it was generated by NM and the AT&T VPN Client.
I have changed the IPs/Domains for privacy reasons, /etc/resolv.conf:
#@NETVPN_GENERATED@ -- this file is generated by NetVPN
# and will be overwritten by NetVPN
# as long as the above mark is intact
nameserver 127.0.0.1
nameserver 127.0.0.1
# Generated by NetworkManager
domain local.domain.com br.somewhere.com somewhere.com
search local.domain.com
nameserver 127.0.0.1
nameserver 127.0.0.1
nameserver 127.0.0.1 |
|
| 2008-11-05 21:43:33 |
João Pinto |
bug |
|
|
assigned to network-manager-applet (Ubuntu) |
| 2008-11-05 21:45:37 |
João Pinto |
bind9: status |
New |
Invalid |
|
| 2008-11-05 21:45:37 |
João Pinto |
bind9: statusexplanation |
|
nslookup error message is related to the "domain local.domain.com br.somewhere.com somewhere.com", which is invalid.
The bug us with NetworkManager which is building an invalid multiple domain script. |
|
| 2008-11-05 21:46:36 |
João Pinto |
title |
nslookup: parse of /etc/resolv.conf failed |
Invalid multi values domain string generated by network manager |
|
| 2008-11-06 14:46:03 |
João Pinto |
network-manager-applet: status |
New |
Invalid |
|
| 2008-11-06 14:46:03 |
João Pinto |
network-manager-applet: statusexplanation |
|
This turned to be an AT&T VPN client problem.
Setting NETVPN_DEF_DOMAIN to "" on /etc/agnclient/agnclient.conf fixed it.
|
|
| 2008-12-28 13:54:22 |
Alexander Sack |
bug |
|
|
assigned to network-manager (Ubuntu) |
| 2008-12-28 13:54:22 |
Alexander Sack |
bug |
|
|
assigned to network-manager |
| 2009-01-14 20:32:02 |
Martin Mai |
network-manager: status |
Incomplete |
Unknown |
|
| 2009-01-14 20:32:02 |
Martin Mai |
network-manager: importance |
Undecided |
Unknown |
|
| 2009-01-14 20:32:02 |
Martin Mai |
network-manager: statusexplanation |
|
Forwarded upstream |
|
| 2009-01-14 22:51:12 |
Bug Watch Updater |
network-manager: status |
Unknown |
New |
|
| 2009-01-20 02:41:04 |
Bug Watch Updater |
network-manager: status |
New |
Invalid |
|
| 2009-01-22 18:42:10 |
Martin Mai |
network-manager: status |
Triaged |
Invalid |
|
| 2009-01-22 18:42:10 |
Martin Mai |
network-manager: statusexplanation |
|
Upstream considers this not being a bug in network-manager, but in the AT&T VPN Client. Don't know which package is the right one for that. |
|
| 2010-09-16 03:22:31 |
Bug Watch Updater |
network-manager: status |
Invalid |
Unknown |
|
| 2010-09-16 03:22:31 |
Bug Watch Updater |
network-manager: importance |
Unknown |
Medium |
|
| 2012-06-30 13:00:22 |
H.-Dirk Schmitt |
bug |
|
|
added subscriber H.-Dirk Schmitt |
