Hi,
On Thu, Mar 27, 2025 at 09:38:02PM +1030, Mal wrote:
> Without the conf package, I still don't get why it populated only one
> ipv4 nameserver target and ignored the ipv6 target.
Are you sure this is not just what the installation process did?
Without "resolvconf" the /etc/resolv.conf file i
Hi,
On Thu, Mar 27, 2025 at 03:24:24PM -, Greg wrote:
> I wonder humorously if this discussion might devolve into yet another
> gargantuan thread concerning resolv.conf and whether it's kosher to set
> the immutable bit on that file in order to prevent whatever the heck is
> writing to it fro
On 2025-03-27, Andy Smith wrote:
> Hi,
>
> On Thu, Mar 27, 2025 at 09:11:23AM -0400, Greg Wooledge wrote:
>> On Thu, Mar 27, 2025 at 13:06:54 +, Andy Smith wrote:
>> > Without "resolvconf" the /etc/resolv.conf file is just a static file so
>> > there's limited things that would be editing it.
On Thu, Mar 27, 2025 at 13:58:49 +, Andy Smith wrote:
> I think all DHCP clients in Debian have a "Recomends" relationship on
> resolvconf to do this modification for them.
hobbit:~$ apt-cache show isc-dhcp-client | grep -e Recommends -e resolv
Recommends: isc-dhcp-common
Suggests: resolvconf,
Hi,
On Thu, Mar 27, 2025 at 09:11:23AM -0400, Greg Wooledge wrote:
> On Thu, Mar 27, 2025 at 13:06:54 +, Andy Smith wrote:
> > Without "resolvconf" the /etc/resolv.conf file is just a static file so
> > there's limited things that would be editing it. The guesses of "you"
> > or "the installer
On Thu, Mar 27, 2025 at 13:06:54 +, Andy Smith wrote:
> Hi,
>
> On Thu, Mar 27, 2025 at 09:38:02PM +1030, Mal wrote:
> > Without the conf package, I still don't get why it populated only one
> > ipv4 nameserver target and ignored the ipv6 target.
>
> Are you sure this is not just what the ins
>>
>> iface enp1s0 inet6 static
>> address 2xxx::x00:1::50
>> netmask 64
>> gateway 2xxx::x00:1::1
>> dns-nameservers 12.34.56.80 2xxx:xxx:x00:1::80
> That dns-nameservers line is only used if you're running the "resolvconf"
> package
c
> address 12.34.56.78
> network 12.34.56.0
> netmask 255.255.255.0
> broadcast 12.34.56.255
> gateway 12.34.56.1
>
> iface enp1s0 inet6 static
> address 2xxx::x00:1::50
> netmask 64
> gateway 2xxx::x00:1::1
> dns-nameservers 12.34.56.80 2xxx:xxx:x0
setup is static then I would (and do) just put both
into resolv.conf manually rather than use resolvconf package - this is
what the dns-nameservers configuration is talking to.
If you want to debug it further, resolvconf will install something in
/etc/network/interfaces.d which looks for these
IN
;; ANSWER SECTION:
ipv6.com. 86400 IN 2602:fa20:1:40::201
;; Query time: 224 msec
;; SERVER: 2xxx::x00:1::50#53(2xxx::x00:1::50) (UDP)
root@debian:/home/user#
On 27/03/2025 5:23 pm, basti wrote:
> Hello,
>
>
Mal writes:
> On Debian 6.1.129-1, I have a static network interface conf (no Netplan)
> with both IPv4 & IPv6 addressing and Name-servers set.
[...]
> On another older machine (running kernel 4.9.35-v7+) with exactly the
> same configuration layout, I get BOTH the IPv4 & IPv6 addresses returne
Hello,
first of all the nameservers in /etc/resolv.conf are queried in order.
That means the 2'nd one is only queried when the first one does not
answer. Even NXDOMAIN is a valid answer.
So the first one should also return IPv6 over a IPv4 connection.
How do you query the nameserver
oopback
allow-hotplug enp1s0
iface enp1s0 inet static
address 12.34.56.78
network 12.34.56.0
netmask 255.255.255.0
broadcast 12.34.56.255
gateway 12.34.56.1
iface enp1s0 inet6 static
address 2xxx::x00:1::50
netmask 64
gateway 2xxx::x00:1::1
dns-nameservers 12.34.56.80 2xxx:xxx:x0
>
> Why on earth would it assume that the gateway is running a resolver?
In a domestic environment, it might be a router. If it's a router
that's not running a DNS server, it's likely to pass it on to any
nameservers the ISP has informed it about.
In a professional environment, I&
Le 01/08/2019 à 20:06, Greg Wooledge a écrit :
On Thu, Aug 01, 2019 at 07:58:56PM +0200, Pascal Hambourg wrote:
Le 01/08/2019 à 18:18, David Wright a écrit :
I think that a lot of people install resolvconf (deliberately or
incidentally) without really understanding what it's for or what
it doe
On Thu, Aug 01, 2019 at 08:16:38PM +0200, Pascal Hambourg wrote:
> Le 01/08/2019 à 19:58, Pascal Hambourg a écrit :
> > Le 01/08/2019 à 18:18, David Wright a écrit :
> > >
> > > I think that a lot of people install resolvconf (deliberately or
> > > incidentally) without really understanding what i
Le 01/08/2019 à 19:58, Pascal Hambourg a écrit :
Le 01/08/2019 à 18:18, David Wright a écrit :
I think that a lot of people install resolvconf (deliberately or
incidentally) without really understanding what it's for or what
it does. Then, because most people naturally check the contents of
/et
On Thu, Aug 01, 2019 at 11:11:33AM -0500, David Wright wrote:
It surprised me that systemd doesn't just use something
like the gateway address if/when some address is absolutely
essential.
Why on earth would it assume that the gateway is running a resolver?
On Thu, Aug 01, 2019 at 07:58:56PM +0200, Pascal Hambourg wrote:
> Le 01/08/2019 à 18:18, David Wright a écrit :
> >
> > I think that a lot of people install resolvconf (deliberately or
> > incidentally) without really understanding what it's for or what
> > it does. Then, because most people natu
Le 01/08/2019 à 18:18, David Wright a écrit :
I think that a lot of people install resolvconf (deliberately or
incidentally) without really understanding what it's for or what
it does. Then, because most people naturally check the contents of
/etc/resolv.conf, they indulge in all sorts of cargo-
On 2019-08-01, Curt wrote:
> On 2019-07-31, Bob Bernstein wrote:
>> I _think_ my upgrade from Jessie to Stretch -- which entailed
>> installing systemd for the first time on this box -- introduced
>> that 8.8.8.8. into my config. I've never been at a loss to
>>
On Wed 31 Jul 2019 at 23:38:34 (+0200), Pascal Hambourg wrote:
> Le 31/07/2019 à 23:30, ghe a écrit :
> > On 7/31/19 2:52 PM, Pascal Hambourg wrote:
> >
> > > Without resolvconf, the DHCP client would have completely overwritten
> > > resolv.conf instead of just adding one line. With resolvconf, a
On Wed 31 Jul 2019 at 18:56:08 (-0400), Bob Bernstein wrote:
> I _think_ my upgrade from Jessie to Stretch -- which entailed
> installing systemd for the first time on this box -- introduced that
> 8.8.8.8. into my config. I've never been at a loss to select my own
> nameserver
On 2019-07-31, Bob Bernstein wrote:
> I _think_ my upgrade from Jessie to Stretch -- which entailed
> installing systemd for the first time on this box -- introduced
> that 8.8.8.8. into my config. I've never been at a loss to
> select my own nameservers, and that never has
I _think_ my upgrade from Jessie to Stretch -- which entailed
installing systemd for the first time on this box -- introduced
that 8.8.8.8. into my config. I've never been at a loss to
select my own nameservers, and that never has been one of them.
I was not even aware of that other
Le 31/07/2019 à 23:30, ghe a écrit :
On 7/31/19 2:52 PM, Pascal Hambourg wrote:
Without resolvconf, the DHCP client would have completely overwritten
resolv.conf instead of just adding one line. With resolvconf, at least
you can have some control over resolv.conf.
OK. vi gives me all the cont
On 7/31/19 2:52 PM, Pascal Hambourg wrote:
> Without resolvconf, the DHCP client would have completely overwritten
> resolv.conf instead of just adding one line. With resolvconf, at least
> you can have some control over resolv.conf.
OK. vi gives me all the control I need over resolv.conf. I unde
Le 31/07/2019 à 21:44, ghe a écrit :
On 7/31/19 1:20 PM, Greg Wooledge wrote:
I still feel like you're missing the big picture here. resolvconf isn't
the thing that's modifying your /etc/resolv.conf file.
It's the thing (that was) modifying my resolv.conf.
Resolvconf does not modify resolv
On Mi, 31 iul 19, 13:44:51, ghe wrote:
> On 7/31/19 1:20 PM, Greg Wooledge wrote:
>
> > I still feel like you're missing the big picture here. resolvconf isn't
> > the thing that's modifying your /etc/resolv.conf file.
>
> It's the thing (that was) modifying my resolv.conf.
[...]
> At first
On 7/31/19 1:20 PM, Greg Wooledge wrote:
> I still feel like you're missing the big picture here. resolvconf isn't
> the thing that's modifying your /etc/resolv.conf file.
It's the thing (that was) modifying my resolv.conf.
I have 2 Enet connections: a reliable T1 and a reasonably fast WiFi.
On Wed, Jul 31, 2019 at 01:13:27PM -0600, ghe wrote:
> On 7/31/19 12:52 PM, Greg Wooledge wrote:
>
> > Removing /etc/resolvconf sounds like terrible> advice.
> > If you want to remove resolvconf, remove the> package with dpkg or apt.
> > Don't just start removing random
> configuration> files
On 7/31/19 12:52 PM, Greg Wooledge wrote:
> Removing /etc/resolvconf sounds like terrible> advice.
> If you want to remove resolvconf, remove the> package with dpkg or apt.
> Don't just start removing random
configuration> files and directories
Good point, well taken.
I've always just deleted
On Wed, Jul 31, 2019 at 12:44:50PM -0600, ghe wrote:
> On 7/31/19 12:17 PM, Bob Bernstein wrote:
>
> > Sure enough, there it was, for eth0. I commented it out and added a line
> > for the nameserver I wanted, and bingo, we have lift off.
>
> That works, but if you want to specify the DNS server,
On 7/31/19 12:17 PM, Bob Bernstein wrote:
> Sure enough, there it was, for eth0. I commented it out and added a line
> for the nameserver I wanted, and bingo, we have lift off.
That works, but if you want to specify the DNS server, delete those 2
DNS lines in /etc...interfaces, and edit /etc/reso
Le 31/07/2019 à 19:56, Greg Wooledge a écrit :
On Wed, Jul 31, 2019 at 07:51:45PM +0200, Pascal Hambourg wrote:
Le 31/07/2019 à 17:10, Bob Bernstein a écrit :
What I want to do is get rid of the google 8.8.8.8 and replace it with a
static nameserver suggested by my vpn.
Edit /etc/network/int
SOLVED, I think.
After all the reading you guys gave me I sat pondering this
morning, and it dawned on me that if I looked at 'interfaces'
and found that darn 8.8.8.8 ip in there, that I might have the
clue I needed.
Sure enough, there it was, for eth0. I commented it out and
added a line f
On Wed, Jul 31, 2019 at 07:51:45PM +0200, Pascal Hambourg wrote:
> Le 31/07/2019 à 17:10, Bob Bernstein a écrit :
> >
> > What I want to do is get rid of the google 8.8.8.8 and replace it with a
> > static nameserver suggested by my vpn.
>
> Edit /etc/network/interfaces.
That isn't a full answer
Le 31/07/2019 à 17:10, Bob Bernstein a écrit :
What I want to do is get rid of the google 8.8.8.8 and replace it with a
static nameserver suggested by my vpn.
Edit /etc/network/interfaces.
Hi.
On Wed, Jul 31, 2019 at 11:10:32AM -0400, Bob Bernstein wrote:
> # Dynamic resolv.conf(5) file for glibc resolver(3) generated by r$
This simplifies things greatly
> What I want to do is get rid of the google 8.8.8.8 and replace it with a
> static nameserver suggested by my vpn.
ls
I've begun a new thread to add some back-story to my "Which
resolv.conf file?" inquiry. *Thanks* to all who have chimed in.
nb. Judah: If "DE" means "desktop environment" then I don't
think I have one. I run the minimalist icewm, and I do not have
network manager installed.
I do not want to
H.S. wrote:
> Hello,
>
> Currently my router machine gets nameservers from my ISP and these
> nameservers appear in my /etc/resolv.conf after the ppp0 connection is
> made.
>
> Hearing about the recent DNS vulnerability, I am thinking of using
> OpenDNS for now. It appears
Hello,
Currently my router machine gets nameservers from my ISP and these
nameservers appear in my /etc/resolv.conf after the ppp0 connection is made.
Hearing about the recent DNS vulnerability, I am thinking of using
OpenDNS for now. It appears that one way is to enter the OpenDNS
nterface.
I think that the reason is because you can have different interfaces
connecting by different ways (for example in a notebook); when you
connect by ppp or by dhcp normally the nameservers are defined by
them.
Example:
# This file describes the network interfaces available on your syste
In testing, I'm installing postfix and it is pulling in this
resolvconf package. resolvconf is trying to tell me that it is much
better to put my name servers in /etc/network/interfaces. But why?
What is the benefit?
Does I need this line for each defined interface or just at the top
of t
John Holland said on Sun, Dec 14, 2003 at 10:23:08AM -0500:
> I have a recurring problem on a Debian machine that is running named.
> The bind program becomes unable to get the address of the root
> nameservers and fills up /var/log/daemonlog,/var/log/syslog with
> messages to
On Sun, Dec 14, 2003 at 10:23:08AM -0500, John Holland wrote:
> I have a recurring problem on a Debian machine that is running named.
> The bind program becomes unable to get the address of the root
> nameservers and fills up /var/log/daemonlog,/var/log/syslog with
> messages to
I have a recurring problem on a Debian machine that is running named.
The bind program becomes unable to get the address of the root
nameservers and fills up /var/log/daemonlog,/var/log/syslog with
messages to that effect.
sysquery: no addrs found for root NS (M.ROOT-SERVERS.NET)
This causes
Ok Howell.
Obviously doing my own resolv.conf by hand means calling tds for their
nameservers.
as to the second option, configuring so my nameservers are pulled down, how do i
do that? Actually, I didn't tell the programs to do anything; I installed
dhcpcd, added the auto line to /etc/ne
S. In looking over my files I found a
/etc/resolv.conf, /etc/dhcpc/resolv.conf and /var/lib/dhcpc/resolv.conf. These
contain what appear to be old nameservers from charter, and the /etc/resolv.conf
still also says "search mad.charter.net." If I remove the resolv.conf(s), I get
an ip address when
I am using tds dsl with a paradyne modem and dhcpcd. I have a cable from my
ethernet card to the modem and from the modem to the phone jack. I use dhcpcd to
manage my dhcp connection. I'm not having to use ppoe or anything like that.
Is this what you wanted to know?
Cheryl
--
To UNSUBSCRIBE, e
dhcpc/resolv.conf. These
contain what appear to be old nameservers from charter, and the /etc/resolv.conf
still also says "search mad.charter.net." If I remove the resolv.conf(s), I get
an ip address when I reboot but I don't actually connect--can't access anything
online. so it wo
Actually, it was quite simple once I put two and two together.
There is a /etc/dhcpc/config file, and it has lines to uncomment if you want to
allow your nameservers, domainname, hostname, and other names set according to
your isp's names. My nameservers are now changed.
Only don't let
All is joy,
Browsing "tasksel" I looked at the info on the DNS packages.
"dnsutils - Utilities for Querying DNS Servers" was one of the entrys.
I tried an "apt-get install dnsutils"
error was it was already installed.
So I thought I'd try removal and reinstallation.
After "apt-get rem
SamBozo Debian User wrote:
> my bad
> resolv.confis the file in question
>
> also the entrys are in numbers
>
> -----
> nameservers 208.6.xxx.xxx
> nameservers 208.6.xxx.xxx
> -
be sure its "nameserver" and not "nameserv
solv.confis the file in question
also the entrys are in numbers
-
nameservers 208.6.xxx.xxx
nameservers 208.6.xxx.xxx
-
these entrys are identical in both the box that is resolving names just
fine and the new box that is not resolving names.
the non-name reso
:-> "SamBozo" == SamBozo Debian User <[EMAIL PROTECTED]> writes:
> I have a new install of debian 2.2 potato on another box.
> It has the same nameserver entrys in /etc/resolve.config ... as this box
> has.
> But it won't resolve ip's.
> I had to use "ftp://207.XXX.XXX.XXX/
SamBozo Debian User wrote:
>
> I have a new install of debian 2.2 potato on another box.
> It has the same nameserver entrys in /etc/resolve.config ... as this box
be sure its resolv.conf not resolv.config
nate
--
:::
ICQ: 75132336
http://www.aphroland.org/
http://www.linuxpowered.net/
[EMAIL
I have a new install of debian 2.2 potato on another box.
It has the same nameserver entrys in /etc/resolve.config ... as this box
has.
But it won't resolve ip's.
I had to use "ftp://207.XXX.XXX.XXX/debian potato main"
as my entry in /etc/apt/sources.list
just to get "apt-get update" woul
> If I'm not mistaken it's supposed to be done this way:
>
> www IN NS www-dns
> www-dns IN A 12.12.12.12
>
>
Yesyesyes, that seems to do it. Thank you very much! Now wait until
dns updates are done to be sure.
Thanks,
Sebastiaan
On Mon, 27 Nov 2000 23:35:48 +0100 (CET), Leen Besselink said:
>
> If I'm not mistaken it's supposed to be done this way:
>
> www IN NS www-dns
> www-dns IN A 12.12.12.12
That is how I did it.
--
Andrew
On Mon, 27 Nov 2000, Sebastiaan wrote:
> Hello,
> I am trying to configure my dns so that a www query to my domain will be
> handled by another nameserver. Yet, I have the following line in
> /etc/bind/db.domain:
>
> www IN NS 202.67.129.130
>
> but when I do a nslookup with q=any, i
Hello,
I am trying to configure my dns so that a www query to my domain will be
handled by another nameserver. Yet, I have the following line in
/etc/bind/db.domain:
www IN NS 202.67.129.130
but when I do a nslookup with q=any, it gives:
Non-authoritive answer:
www.domain.com
Note that Tim and I have both sent ACKs that we should be removed from
those domains - I sent mine before the problem came up. Because of the
snafu, we might have to go through that process another time.
Also, moving the U.S. mail address requires a notarized document, it
can't be done electronica
Michael Shields wrote:
> Incidentially both the listed contacts of debian.org have left Debian;
> they should be changed to the new officers of SPI, I suppose, or to an
We're trying to achive this since Monday...
Since it needs some paper work this will take a while.
Regards,
Joey
--
In article <[EMAIL PROTECTED]>,
Martin Schulze <[EMAIL PROTECTED]> wrote:
> this morning the domain name 'debian.org' was removed from the
> root nameservers.
A large number (reportedly 48,000!) domains were placed "on hold" and
removed from the roo
Hi,
this morning the domain name 'debian.org' was removed from the
root nameservers.
At the moment we don't know what has caused this.
We have sent an inquiry to the InterNIC about this and tried
to phone them up. No response yet.
As a result you might not be able
>> "RK" == Robert Kerr <[EMAIL PROTECTED]> writes:
RK> after a long hiatus I'm back the the debian linux world. I got my ppp
RK> configuration set up alright, except that my system can't find the
RK> nameserver. I thought that all I had to do was have a resolv file with
RK> the nameserver li
Hi all,
after a long hiatus I'm back the the debian linux world. I got my ppp
configuration set up alright, except that my system can't find the
nameserver. I thought that all I had to do was have a resolv file with
the nameserver line in it. What am I doing wrong?
Thanks
-bob
Always remem
68 matches
Mail list logo
