supapupa
@rr.com
| reply to graysonf
Re: DNS Strangeness
said by graysonf  :OK, IP6. I wonder if he is actually running IP6, and if not what happens when things get configured to use it but can't. BIND is IPv6 aware, it doesn't matter if he's running a server with IPv6 addressing or not. If it didn't like the ::1 loopback IP, then named.conf would not load and named would not start. And it's only an ACL, and simply an entry allowing the IPv6 loopback of the server to do recursion. That's all that entry would be able to do.
But you're right, the # should not be a valid comment delimiter for BIND, it should be //. Although, I would expect BIND not to start if it saw that line, since it would be invalid. |
|
luminaire
Premium
join:2005-03-22
Oakville, ON
clubs:
| Dunno about valid comment, but when I comment that line out as such it is deactivated, named starts with no complaints. I'd say it looks valid. A quick google confirmed.
Quoted: »www.zytrax.com/books/dns/ch7/
named.conf format, structure and overview
A named.conf file can contain comments and will contain a number of clauses which group together related statements which control the functionality and security of the BIND server.
BIND provides a number of comment formats as follows:
/* C style comment format needs opening and closing markers
** but allows multiple lines or */
/* single lines */
// C++ style comments single line format no closing required
# PERL/SHELL style comments single lines no closing required
--
Luminaire
My Blog |
|
graysonf
Premium,MVM
join:1999-07-16
Fort Lauderdale, FL
| I don't have an answer, but I'll ask it anyway.
What happens when you use a single line comment approach within a command that spans more than one line?
I'd try it this way just for grins:
options {
directory "/var/named";
/*auth-nxdomain no;*/
recursive-clients 10000;
allow-recursion { clients; };
allow-query { "any"; };
}; |
|
