Dear all,
I have the following test zone files:
8.example.com.signed
K8.example.com.+008+40162.key
K8.example.com.+008+40162.private
I edit the signed zone directly (8.example.com.signed) and remove for
example an A record and then resign the zone as following:
dnssec-signzone -z -o 8.example.c
I'm looking into the GEOIP functionality but we are in the 9.9 release tree.
I don't see in it in the documentation but wanted to check here incase I'm
just missing it.
smime.p7s
Description: S/MIME cryptographic signature
___
Please visit https://li
Olsen, Richard William (Rick) CTR (US) wrote:
> I'm looking into the GEOIP functionality but we are in the 9.9 release tree.
> I don't see in it in the documentation but wanted to check here incase I'm
> just missing it.
It's a 9.10 feature.
Tony.
--
f.anthony.n.finchhttp://dotat.at/ - I
> Tom, when your mail server establishes a connection to another host, the
> receiving host will likely automatically check the PTR record of the IP
> address your server used as it's source address. This PTR record should
> have a corresponding A record that points to the same IP address that
> That is mostly how I thought it worked. What I had in mind more
> specifically was:
>
> adi.com zone:
> mackerel.adi.com. IN A 75.100.245.141
> mackerel.adi.com. IN A 96.85.104.76
>
> reverse zones:
> 141.245.100.75.in-addr.arpa. IN PTR mackerel.adi.com
> 76.104.85.96.in-addr.arpa.
On Mon, Mar 21, 2016 at 1:57 PM, John Bond wrote:
> This is reminder that there is a scheduled change to the IPv6 addresses
> for the
> L-Root server, that will take effect on March 23, 2016.
>
> The new IP addresses for the L.ROOT-SERVERS.NET will be:
>
> 199.7.83.42
>
> 2001:500:9f::42
>
>
> P
Hi--
On Mar 22, 2016, at 9:44 AM, Bob Harold wrote:
[ ... ]
> I appreciate the announcement of the change ahead of time, but I don't feel
> like it is safe to update my root hints file based on an email, which could
> be spoofed. It's not that I don't trust you, but someone could spoof your
>
Charles Swiger wrote:
>
> You could always ask the A root server (or one of the others) what it
> thinks the IP should be:
>
> % dig l.root-servers.net. @a.root-servers.net | grep l
It's the record which is changing, not the A record, and it won't
change until tomorrow. (Hopefully https://tw
> > That is mostly how I thought it worked. What I had in mind more
> > specifically was:
> >
> > adi.com zone:
> > mackerel.adi.com. IN A 75.100.245.141
> > mackerel.adi.com. IN A 96.85.104.76
> >
> > reverse zones:
> > 141.245.100.75.in-addr.arpa. IN PTR mackerel.adi.com
> > 76.104.85.
Hi there,
On Tue, 22 Mar 2016, Bob Harold wrote:
I appreciate the announcement of the change ahead of time, but I
don't feel like it is safe to update my root hints file based on an
email ...
Hint: the 'hints' file contains hints. :)
https://deepthought.isc.org/article/AA-01309/0/Root-hints-
Hello all
I recently compiled and installed BIND 9.10.3-p4 from source on a system
running CentOS 7. This is for practice purposes. Ive been searching all of
the net and I cannot find the answer to this one question of mine: How do I
create the systemd service unit configuration file for the named
Hi Everyone,
Does BIND 9 support LLQ and UL?
LLQ http://files.dns-sd.org/draft-sekar-dns-llq.txt
UL http://files.dns-sd.org/draft-sekar-dns-ul.txt
They were originally in Apple's dnsextd implementation long ago. In my
own test, it seems that UL is working. When a clien
This is not specifically a bind question but rather a centos/red hat
question, but I think the below will get you on the right track:
https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/System_Administrators_Guide/sect-Managing_Services_with_systemd-Unit_Files.html
On Tue
13 matches
Mail list logo
