On 12/11/18 4:51 PM, Ed Greshko wrote:
> dnssec is a concern
is *not* a concern
--
Right: I dislike the default color scheme Wrong: What idiot picked the default
color scheme
___
users mailing list -- users@lists.fedoraproject.org
To unsubscrib
On 12/11/18 3:10 PM, Tim via users wrote:
> Allegedly, on or about 8 December 2018, sean darcy sent:
>> What I want is:
>>
>> nameserver 127.0.0.1
>> nameserver
> Is the DHCP server configurable by you? If so, then enter the list of
> DNS servers that you want clients to use into the DHCP serve
Allegedly, on or about 8 December 2018, sean darcy sent:
> What I want is:
>
> nameserver 127.0.0.1
> nameserver
Is the DHCP server configurable by you? If so, then enter the list of
DNS servers that you want clients to use into the DHCP server, and let
it configure your clients.
--
[tim@lo
On 12/9/18 12:23 AM, sean darcy wrote:
> FC28.
>
> I'm running a DNS server (unbound) on a VOIP server. It's crucial that I can
> always
> resolve addresses, even if it's slower. Now DNS1 is set to 127.0.0.1, peerdns
> no. Giving:
>
> cat /etc/resolv.conf
> # Generated by dnssec-trigger-script
>
Allegedly, on or about 10 December 2018, sean darcy sent:
> I still have a single point of failure. A backup would be very handy.
Within a small network, it's usual to run two DNS servers on two
different machines. On the WWW, it's usual to run more.
You really haven't provided enough informatio
On 12/9/18 10:19 PM, Cameron Simpson wrote:
On 09Dec2018 18:33, sean darcy wrote:
My local server - unbound - works great. Never a problem, almost.
Sometimes there's a problem on reboot, and unbound doesn't start.
Do you know why this is? I run unbound on my Mac, but I start it by hand
post
On 09Dec2018 18:33, sean darcy wrote:
My local server - unbound - works great. Never a problem, almost.
Sometimes there's a problem on reboot, and unbound doesn't start.
Do you know why this is? I run unbound on my Mac, but I start it by hand
post boot (just don't ask).
How is unbound star
On 12/8/18 5:53 PM, Samuel Sieb wrote:
On 12/8/18 8:23 AM, sean darcy wrote:
I'm running a DNS server (unbound) on a VOIP server. It's crucial that
I can always resolve addresses, even if it's slower. Now DNS1 is set
to 127.0.0.1, peerdns no. Giving:
How does the local DNS do the resolving.
Allegedly, on or about 8 December 2018, sean darcy sent:
> I'm running a DNS server (unbound) on a VOIP server. It's crucial
> that I can always resolve addresses, even if it's slower. Now DNS1 is
> set to 127.0.0.1, peerdns no. Giving:
What makes you think it'll be slower?
I run a local DNS serv
On 12/8/18 8:23 AM, sean darcy wrote:
I'm running a DNS server (unbound) on a VOIP server. It's crucial that I
can always resolve addresses, even if it's slower. Now DNS1 is set to
127.0.0.1, peerdns no. Giving:
How does the local DNS do the resolving. Why is it slower?
What I want is:
nam
FC28.
I'm running a DNS server (unbound) on a VOIP server. It's crucial that I
can always resolve addresses, even if it's slower. Now DNS1 is set to
127.0.0.1, peerdns no. Giving:
cat /etc/resolv.conf
# Generated by dnssec-trigger-script
nameserver 127.0.0.1
What I want is:
nameserver 127.
11 matches
Mail list logo