On 10/21/23 16:46, Charles Curley wrote:
On Sat, 21 Oct 2023 14:40:49 -0400
Pocket<poc...@columbus.rr.com> wrote:
but the machine in question has
bind running so nameserver needs to be set to 127.0.0.1 and the
domain to example.org in the resolv.conf file.
This is my problem in a nutshell
Oh, why didn't you say that! Actually, it doesn't have to use the
loopback address; you can use the address of the Ethernet interface.
Also, you should not be using example.org. That is a reserved domain
name.https://en.wikipedia.org/wiki/Example.com
rfc2606.html 3 <https://www.rfc-editor.org/rfc/rfc2606.html#section-3>.
Reserved Example Second Level Domain Names
The Internet Assigned Numbers Authority (IANA) also currently has the
following second level domain names reserved which can be used as
examples.
example.com
example.net
example.org
rfc6761.html
7. DNS Registries/Registrars:
How should DNS Registries/Registrars treat requests to register
this reserved domain name? Should such requests be denied?
Should such requests be allowed, but only to a specially-
designated entity? (For example, the name "www.example.org" is
reserved for documentation examples and is not available for
registration; however, the name is in fact registered; and there
is even a web site at that name, which states circularly that the
name is reserved for use in documentation and cannot be
registered!)
Which I take it that you can use them for any purpose as long as it is not on
the internet.
Why would I register a domain name for an internal network?
Any name will do. You could make the same argument if you just makeup a domain
to use as it could already be registered or someone my register it in the
future.
That is why I picked example.org as It will/can not be used, no collision with
domain names that way.
Somebody is usinghttp://example.org/ on the internet, try it in your browser
and it ishttps://www.iana.org/help/example-domains
IANA-managed Reserved Domains
Certain domains are set aside, and nominally registered to “IANA”, for
specific policy or technical purposes.
Example domains
As described in RFC 2606 <https://www.iana.org/go/rfc2606> and RFC 6761
<https://www.iana.org/go/rfc6761>, a number of domains such as
example.com and example.org are maintained for documentation purposes.
These domains may be used as illustrative examples in documents without
prior coordination with us. They are not available for registration or
transfer.
So I can not use or I am forbidden to use 192.168.1.0/24 network as it is
reserved?
I am going to guess (since you haven't
said so) that this is also not a laptop, and therefor it has a permanent
IP address.
This is for a name server
If you insist on retaining NetworkManager, this page might be useful.
https://serverfault.com/questions/810636/how-to-manage-dns-in-networkmanager-via-console-nmcli
You can also add DNS servers in the GTK version of the NM GUI. I don't
know about the KDE version.
I am just using what was installed by my scripted debian installation
You can use isc-dhcp to tell the whole network where its DNS server is.
You can also make over-rides for individual hosts. In dhcpd.conf:
Yes but if the currently installed and enabled NetwokManager will work
then there is little need to change it. why change it?
You said in another email that you are using a dhcp server on a
"router". That doesn't tell me much. A router is simply a computer that
sits between two networks, and routes packets between them. My router
is a 16 year old computer designed for embedded applications that runs
Debian. I run ISC DHCPD on that an another machine with fail-over
between them.
It is a "home office router" by linksys
I could have built my own "router" with my own custom scratch built OS
as I did starting 35 years ago, but why should I if I can get something
off the shelf?
From what I have seen most "routers" these days are cheap boxes
provided by ISPs that have buggy, insecure, and limited software which
may not be able to do this.
You can also set the ISC dhcp client to add name servers.
prepend domain-name-servers 127.0.0.1;
Then all clients get the localhost address for DNS resolution, which
will not come close to working.
Anyway I have solved this issue by modifying the keyfile for device end0
see my previous post
I will find a way........
--
It's not easy to be me
