In article , shulkae
wrote:
> Question on BIND 9 running on FreeBSD.
>
> My customer requested to add multiple IPs to a single name so that he
> can use the round-robin feature of BIND to load-balance the service.
>
> The entry we added looks something as below:
>
> # more db.myzone
> ..
> ..
In message <6.2.5.6.2.20090225140635.02c02...@resistor.net>, SM writes:
> At 13:46 25-02-2009, Mike Bernhardt wrote:
> >I've been looking into the RFCs regarding whether or not single-character
> >(alpha) host names are allowed or not. RFC 952 says no, but 2181 says that
> >host names must between
online-reg wrote:
Hi All:
Bind 9.5.0-p1 on Fedora...how do I clear the cache?
I updated a FUBAR MX record at godaddy.com's NS, with a TTL of 3600.
My local BIND seems to be caching the record after I updated at
godaddy. When I query the upstream NS that the local server uses, it
returns the
In message <49a55a7f.8010...@ou.edu>, Peter Laws writes:
> Mark Andrews wrote:
> > When does it stop? What will be the next character you
> > "just have to have"? At the moment you have 1 inter label
> > seperator and 1 intra label seperator. That should be
> > enough for anyone
Hi All:
Bind 9.5.0-p1 on Fedora...how do I clear the cache?
I updated a FUBAR MX record at godaddy.com's NS, with a TTL of 3600. My
local BIND seems to be caching the record after I updated at godaddy. When I
query the upstream NS that the local server uses, it returns the updated MX
record,
At Wed, 25 Feb 2009 09:20:52 -0500,
Todd wrote:
> My apologies again, you are correct. I ran a named -v on the boxes,
> forgetting that we were directly calling bind in a non-path. We are
> in fact using 9.4.2-P2 on everything, patched to protect against
> kaminsky. We will look at an upgrade
At 13:46 25-02-2009, Mike Bernhardt wrote:
I've been looking into the RFCs regarding whether or not single-character
(alpha) host names are allowed or not. RFC 952 says no, but 2181 says that
host names must between 1 and 63 octets in length, which would appear to say
"yes."
Section 2.1 of RFC
On 25-Feb-2009, at 17:14, Evan Hunt wrote:
Actually, to be lawyerly about it, while RFC952 says you can't have
a single-character name, it also defines names as including periods
to delimit domain-name components. So, "m.google.com." is really a
13-character name, with a single-character compo
On 25-Feb-2009, at 16:46, Mike Bernhardt wrote:
So what is the accepted view on this currently? Is there another RFC
that
has made it OK now?
I'm not going to say this definitively, because I'm not certain, but I
think 952 may have been updated by a later RFC. Certainly there are
sever
At Wed, 25 Feb 2009 14:17:27 -0600,
Timothy Holtzen wrote:
> I applied the patch on my test system and ran my little test using wget
> and this is the output I got in the log
>
> Feb 25 13:51:12 arthur named[17030]: libxml2 Error: Input is not proper
> UTF-8, indicate encoding !
> Feb 25 13:51:1
> Certainly, several large organizations (Google, Yahoo and CNN, to name 3)
> are using at least 1: "m"
Not to mention all the root-server operators. So the rule clearly
isn't being enforced very well. :)
Actually, to be lawyerly about it, while RFC952 says you can't have
a single-character name
I've been looking into the RFCs regarding whether or not single-character
(alpha) host names are allowed or not. RFC 952 says no, but 2181 says that
host names must between 1 and 63 octets in length, which would appear to say
"yes."
Certainly, several large organizations (Google, Yahoo and CNN, to
I've done some more digging today - I have found a couple 9.2.4
servers that had the same file descriptors problem at the same time as
the 9.4.2-p2 servers.
Feb 24 13:28:48 dns01 named[29292]: socket: too many open file descriptors
Both servers named processes seem to have 2048 FD's available:
#
Luis Silva wrote:
Hi all!
I read in some previous posts that you don't agree of not having cache
in a name server. The problem is that I wanted to have a bind server
resolving external queries and doing cache but not for a specific zone
that I use "forward".
client->ns#1(forward)->ns#2
Tha
I applied the patch on my test system and ran my little test using wget
and this is the output I got in the log
Feb 25 13:51:12 arthur named[17030]: libxml2 Error: Input is not proper
UTF-8, indicate encoding !
Feb 25 13:51:12 arthur named[17030]: libxml2 Error:
xmlTextWriterWriteDocCallback : XML
Hi all!
I read in some previous posts that you don't agree of not having cache in a
name server. The problem is that I wanted to have a bind server
resolving external queries and doing cache but not for a specific zone that
I use "forward".
client->ns#1(forward)->ns#2
That specific zone is priva
On Wed, 25 Feb 2009, Martin Moerman wrote:
> Hello,
>
> I have an issue with 9.5.3 on which I see that bind does a reload of the
> named.conf but does not reload the include files which are in named.conf
9.5.3 doesn't exist.
> Situation:
> I do an add or change of name / ip in Plesk, plesk nic
I'm looking for a method to cull out unused DNS entries from zone files.
Eventually, entries we add to zone files entries fall into disuse.
Usually the customers never report when this happens, so the zone
files grow and grow and grow with "cruft."
Can any of you share recommendations? I'm runni
Mark Andrews wrote:
When does it stop? What will be the next character you
"just have to have"? At the moment you have 1 inter label
seperator and 1 intra label seperator. That should be
enough for anyone.
Like 640k of memory.
Unicode is coming (as fast as I
Jeff Lightner wrote:
And of course you can legitimately say it is a "Standard" even if it
isn't enforced by the software. Your argument would be that people
implementing new servers or attempting to access the systems wouldn't be
able to do so because they wouldn't have added the "exception to
Just following this question up. The answer was that the user specified
in the smf_method(5) property needs to have
solaris.smf.manage.bind authorization to be able to disable the
service. I've opened a bug to update the Sun manual page, CR 6809900
Created, P4 manpage/section1m named(1M) shoul
Hello,
I have an issue with 9.5.3 on which I see that bind does a reload of the
named.conf but does not reload the include files which are in named.conf
Situation:
I do an add or change of name / ip in Plesk, plesk nicely rsyncs the
zone files to our two name servers.
nameserver 2 reloads corre
Question on BIND 9 running on FreeBSD.
My customer requested to add multiple IPs to a single name so that he
can use the round-robin feature of BIND to load-balance the service.
The entry we added looks something as below:
# more db.myzone
..
..
ws
..
..
So when my customer query the ws, he
My apologies again, you are correct. I ran a named -v on the boxes,
forgetting that we were directly calling bind in a non-path. We are
in fact using 9.4.2-P2 on everything, patched to protect against
kaminsky. We will look at an upgrade program to get these boxes
(about 80 servers, unfortunatel
24 matches
Mail list logo
