On Sun, 2025-05-04 at 08:21 -0500, Patrick Dohman wrote:
> Sorry it seems that a pet alligator is actually a lot of work ;)
LOL, quite an apt description
--
uname -rsvp
Linux 3.10.0-1160.119.1.el7.x86_64 #1 SMP Tue Jun 4 14:43:51 UTC 2024 x86_64
Boilerplate: All unexpected mail to my mailb
> On May 1, 2025, at 4:11 AM, Samuel Sieb wrote:
>
> On 5/1/25 1:52 AM, Tim via users wrote:
>> The number of times I've tried to access my printer's configuration
>> server, and had to fight with Firefox to stop searching the internet
>> for a shop selling that model printer, is a right pain.
> On May 1, 2025, at 3:52 AM, Tim via users
> wrote:
>
> Tim:
If I were configuring my DHCP server to hand it out to clients, that
would be the following in the dhcpd.conf file:
option domain-name "internal.";
It's going by proper standards that a domain name
On 5/1/25 1:52 AM, Tim via users wrote:
The number of times I've tried to access my printer's configuration
server, and had to fight with Firefox to stop searching the internet
for a shop selling that model printer, is a right pain. Even when I've
typed http://laserprinter/ as a fully complete *
Tim:
>>> If I were configuring my DHCP server to hand it out to clients, that
>>> would be the following in the dhcpd.conf file:
>>>
>>> option domain-name "internal.";
>>>
>>> It's going by proper standards that a domain name ends with a dot.
& again, Tim:
>> That may not be needed, now. But
> On 1 May 2025, at 07:23, Mike Wright wrote:
>
> (fqdn).
>
> How utilities such as as nslookup and dig figure out what to do when the
> final dot on a fqdn is missing is a mystery to me. Perhaps they always add a
> dot then trim the name to have no more than one. IDK
The lack of a traili
On 4/30/25 22:21, Mike Wright wrote:
On 4/30/25 22:06, Tim via users wrote:
Follow-up...
On Thu, 2025-05-01 at 11:53 +0930, Tim via users wrote:
If I were configuring my DHCP server to hand it out to clients, that
would be the following in the dhcpd.conf file:
option domain-name "internal
Thanks
It is working now!
pepebuho@pepewin:~$ ping bloody.internal
PING bloody.internal (192.168.1.5) 56(84) bytes of data.
64 bytes from bloody.internal (192.168.1.5): icmp_seq=1 ttl=64 time=0.440 ms
64 bytes from bloody.internal (192.168.1.5): icmp_seq=2 ttl=64 time=0.195 ms
64 bytes from bloody
On 4/30/25 22:06, Tim via users wrote:
Follow-up...
On Thu, 2025-05-01 at 11:53 +0930, Tim via users wrote:
If I were configuring my DHCP server to hand it out to clients, that
would be the following in the dhcpd.conf file:
option domain-name "internal.";
It's going by proper standards th
Follow-up...
On Thu, 2025-05-01 at 11:53 +0930, Tim via users wrote:
> If I were configuring my DHCP server to hand it out to clients, that
> would be the following in the dhcpd.conf file:
>
> option domain-name "internal.";
>
> It's going by proper standards that a domain name ends with a do
Tim:
> > You could certainly whack ".internal" onto the end of your hostnames to
> > make up a FQDN without issues. And even though it's a long thing to
> > type, you can make use the search domain feature so it's configured
> > into the networking parameters, and you only ever have to type the
>
> You could certainly whack ".internal" onto the end of your hostnames to
> make up a FQDN without issues. And even though it's a long thing to
> type, you can make use the search domain feature so it's configured
> into the networking parameters, and you only ever have to type the
> hostname.
>
>
Samuel Sieb:
>> That shouldn't work. A name without a domain isn't valid. You
>> need to set things up so there's a domain (and don't use
>>
local!). You can have a default domain, so that bare names will
>> automatically be tried with the default domain.
Javier Perez:
> Sorry. It works. I do
On Tue, Apr 29, 2025 at 4:53 AM Samuel Sieb wrote:
> On 4/29/25 1:10 AM, Javier Perez wrote:
> > Help. Looking at the about systemd-resolved question prompted me to try
> > to clear a problem I am having with local DNS.
> > My home system have few pcs and other devices, some of them with static
>
>
>
On Tue, Apr 29, 2025 at 4:12 AM Barry wrote:
>
>
> On 29 Apr 2025, at 09:11, Javier Perez wrote:
>
>
> Help. Looking at the about systemd-resolved question prompted me to try to
> clear a problem I am having with local DNS.
> My home system have few pcs and other devices, some of them w
On Tue, 2025-04-29 at 03:10 -0500, Javier Perez wrote:
> Help. Looking at the about systemd-resolved question prompted me to
> try to clear a problem I am having with local DNS.
> My home system have few pcs and other devices, some of them with
> static ip addresses set at my local router.
> My si
On 4/29/25 1:10 AM, Javier Perez wrote:
Help. Looking at the about systemd-resolved question prompted me to try
to clear a problem I am having with local DNS.
My home system have few pcs and other devices, some of them with static
ip addresses set at my local router.
My situation is that name
On 29 Apr 2025, at 09:11, Javier Perez wrote:Help. Looking at the about systemd-resolved question prompted me to try to clear a problem I am having with local DNS.My home system have few pcs and other devices, some of them with static ip addresses set at my local router.My situation is that name
Help. Looking at the about systemd-resolved question prompted me to try to
clear a problem I am having with local DNS.
My home system have few pcs and other devices, some of them with static ip
addresses set at my local router.
My situation is that name resolution does not always work.
For example
19 matches
Mail list logo
