summaryrefslogtreecommitdiffstats
path: root/mDNSResponder/mDNSShared/dnsextd.conf
diff options
context:
space:
mode:
Diffstat (limited to 'mDNSResponder/mDNSShared/dnsextd.conf')
-rw-r--r--mDNSResponder/mDNSShared/dnsextd.conf10
1 files changed, 5 insertions, 5 deletions
diff --git a/mDNSResponder/mDNSShared/dnsextd.conf b/mDNSResponder/mDNSShared/dnsextd.conf
index 0379580d..d8cac244 100644
--- a/mDNSResponder/mDNSShared/dnsextd.conf
+++ b/mDNSResponder/mDNSShared/dnsextd.conf
@@ -23,7 +23,7 @@
// network, you might allow anyone to perform updates. To do that, you just
// permit any and all updates coming from dnsextd on the same machine:
//
-// zone "my-dynamic-subdomain.company.com."
+// zone "my-dynamic-subdomain.example.com."
// { type master; file "db.xxx"; allow-update { 127.0.0.1; }; };
//
// On a machine connected to the Internet or other large open network,
@@ -32,11 +32,11 @@
// perform updates in your dynamic zone, like this:
//
// key keyname. { algorithm hmac-md5; secret "abcdefghijklmnopqrstuv=="; };
-// zone "my-dynamic-subdomain.company.com." in
+// zone "my-dynamic-subdomain.example.com." in
// {
// type master;
-// file "db.my-dynamic-subdomain.company.com";
-// update-policy { grant * wildcard *.my-dynamic-subdomain.company.com.; };
+// file "db.my-dynamic-subdomain.example.com";
+// update-policy { grant * wildcard *.my-dynamic-subdomain.example.com.; };
// };
//
// You could use a single key which you give to all authorized users, but
@@ -55,6 +55,6 @@ options {
// llq port 5352;
};
-zone "my-dynamic-subdomain.company.com." {
+zone "my-dynamic-subdomain.example.com." {
type public;
};