Is this something I should add to the FreeBSD port?
On 03/14/2012 17:58, Mark Andrews wrote:
>
> We believe this patch will fix this issue. It has been committed to be
> released as part of BIND 9.9.1.
>
> Mark
>
> diff --git a/bin/named/client.c b/bin/named/client.c
> index 2f4130c..ae13795
Or one can use nslookup from BIND 9 which doesn't have that
restriction.
nslookups with this restriction are at least 10 years old now and
there have been new types added. DNSSEC has been completely
overhauled in that time.
Mark
--
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Aust
Put record.ourdomain.com as a CNAME in both your internal and external
views.
Internal user will query internal view and get CNAME record to
record.client.otherdomain.com. Your recursive name server will look up
record.client.otherdomain.com and get the CNAME record to
otherhost.otherdomain.c
Who will be using this in-house DNS server? Your local users? If yes,
then you will need to enable recursion so they can look up outside
resources (google.com, etc.)
If this server will strictly be an authoritative server for your domain,
then it won't need recursion but queries that return a
On Fri, Mar 16, 2012 at 5:03 PM, G.W. Haywood wrote:
You didn't tell the OP what to use instead of nslookup!
sorry :-)
On 16.03.12 19:33, Ashok Agarwal wrote:
If PTR is present then it works pretty well. My concern is without PTR
record.
Ya I can use "dig" instead to nslookup
you can also u
I would NOT open the payload on this, just in case it gets through
anyones filters etc (fished this one out of my ClamAV redirect directory)
> On Fri, 16 Mar 2012 23:30:08 +0800 r...@mars.org wrote:
Cheers
Ian Manners
http://www.os2site.com/
___
Plea
> I was considering doing "rndc reconfig", followed by a "rndc reload
> " for each of the new zones.
>
> Would this work?
'reconfig' reloads the configuration without reloading all of the zones,
but if it sees that you've added or removed any zones in the config file,
it will load or unload those
If you are authoritative for a cname that points to an A elsewhere, your
server will resolve the cname and leave it to the client dns server to go
get the A from the server that hosts it.
On Mar 16, 2012 10:14 AM, "Samantha Steers" wrote:
> Hi,
>
> I am getting prepped to migrate dns from one ser
If PTR is present then it works pretty well. My concern is without PTR
record.
Ya I can use "dig" instead to nslookup but I need to fix it in nslookup as
well.
If anybody has any clue or can tell how it be fixed then it will really
help me and it be highly appreciated.
-Ashok
On Fri, Mar 16, 2012
Hi there,
On Fri, 16 Mar 2012, Matus UHLAR - fantomas wrote:
the main problem is nslookup itself, and this is just one of reasons
nslookup is not recommended for use.
You didn't tell the OP what to use instead of nslookup!
It's 'dig'.
--
73,
Ged.
___
On 3/16/2012 4:10 AM, Mark Pettit wrote:
We have an antiquated push process that copies files into the
zonefile directory and then tells BIND "rndc reload". For various
reasons, "rndc reload" takes about 120 seconds to complete. BIND is
not answering queries for a very large part of that time
On 3/16/2012 4:10 AM, Mark Pettit wrote:
I've read carefully through the BIND ARM and am still not sure of the answer to
this, so I figured I'd ask on here.
"rndc reconfig" causes BIND to re-load its config file, but unlike "rndc
reload", BIND will not scan the zone files it's mastering to s
On 16.03.12 14:57, Ashok Agarwal wrote:
I am trying to nslookup nameserver through IPv6 address. but nslookup is
failing to resolv nameserver when nameserver's PTR record is missing.
Kindly let me know if anybody has any fix for this problem.
the main problem is nslookup itself, and this is jus
Hi,
I am using BIND 9.3 as my DNS server.
I am trying to nslookup nameserver through IPv6 address. but nslookup is
failing to resolv nameserver when nameserver's PTR record is missing.
Kindly let me know if anybody has any fix for this problem.
Thanks in anticipation.
Regards,
-Ashok
2012/3/16 Mark Pettit
> I've read carefully through the BIND ARM and am still not sure of the
> answer to this, so I figured I'd ask on here.
>
> "rndc reconfig" causes BIND to re-load its config file, but unlike "rndc
> reload", BIND will not scan the zone files it's mastering to see if there
>
On 16/03/2012 09:10, Mark Pettit wrote:
Hi Mark,
> However, I'm curious what I should do when an update contains both a
> new config file and new zone files.
If you have *new* zones, "rndc reconfig" will also load them. You don't
need to run "rndc reload" for them when they are first added to th
I've read carefully through the BIND ARM and am still not sure of the answer to
this, so I figured I'd ask on here.
"rndc reconfig" causes BIND to re-load its config file, but unlike "rndc
reload", BIND will not scan the zone files it's mastering to see if there have
been any updates. This is
17 matches
Mail list logo
