DNS/RFC and includes

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Guys,

If you check the DNS RFCs, you can see that we can use a $INCLUDE parameter
in the Myzone.dns file to ask the DNS service to include all the records that
are in an external file

For example :

MyZone.DNS
$include Countrya.dns
$include countryb.dns

It is very nice if you have a lot of names and if you want to split them in
different files.

Here is my question ...

According to the RFC (which is in UNIX) we can specify a full path to the
include files... but on Windows it does not work.. and I don't want to have
my file in the c:\windows\system32\dns directory...

I tried :
$include c:\mydir\mars.dns
$include "c:\mydir\mars.dns"

.. but when I start the service, it appears in red in the MMC.

Do you have any advice ? I am stuck ..

Thanks for your help

Regards
 
If you check the DNS RFCs, you can see that we can use a $INCLUDE
parameter
in the Myzone.dns file to ask the DNS service to include all the records that
are in an external file
Click to expand...

You might supply the RFC number -- the DNS developers
read this newsgroup and if it is truly a required RFC, which
is doubtful, then they will likely take an interest and fix it.

The reason it is doubtful that this is a required RFC is that
such would describe the internal storage of the server
rather than how the DNS server interacts on the network.

On the other hand, if it does describe the details of the zone
file as a requirement that might make some sense.

Microsoft does tout that their DNS is RFC compliant
and BIND compatible (note that BIND is in no technical
way the "reference implementation" of a DNS server.)
 
Thanks for the post.

There we go : RFC 1035 defines the format as:

An example :

$ORIGIN uk.mydomain.com.
@ IN NS ns2.mydomain.com.
; ns2.mydomain.com services uk.mydomain.com

$INCLUDE /path/to/file ; no ORIGIN
; INCLUDE file statements
www IN A 192.168.23.15
;www.uk.mydomain.com = 192.168.23.15
....
; end of included file

ftp IN A 192.168.35.16
; ftp.uk.mydomain.com = 192.168.35.16


Thanks for your help

Regards

F
 
In
fe said:
Thanks for the post.

There we go : RFC 1035 defines the format as:

An example :

$ORIGIN uk.mydomain.com.
@ IN NS ns2.mydomain.com.
; ns2.mydomain.com services uk.mydomain.com

$INCLUDE /path/to/file ; no ORIGIN
; INCLUDE file statements
www IN A 192.168.23.15
;www.uk.mydomain.com = 192.168.23.15
...
; end of included file

ftp IN A 192.168.35.16
; ftp.uk.mydomain.com = 192.168.35.16


Thanks for your help

Regards

F
Click to expand...

I haven't tried it, but have you tried it using the system variables
defining the path, such as %systemroot%, etc.


--
Regards,
Ace

G O E A G L E S !!!
Please direct all replies ONLY to the Microsoft public newsgroups
so all can benefit.

This posting is provided "AS-IS" with no warranties or guarantees
and confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft Windows MVP - Windows Server - Directory Services

Security Is Like An Onion, It Has Layers
HAM AND EGGS: A day's work for a chicken;
A lifetime commitment for a pig.
 
Back
Top