Hi,
xxx.com and IP address 192.168.1.100 is just a example domain name and IP
address. Our boss want everybody access our domain example.com through
browser, then it will redirect to our web site www.example.com. So I want
to get more information about unexpected impact when we changed DNS records
Hi Kevin,
Thanks for your help. Do not worry. The IP address 192.168.1.100 is just
for example.
Best Regards,
Pete Fong
2014-09-09 3:30 GMT+08:00 Kevin Darcy :
> Based on the zone contents below, you shouldn't have any problem
> changing the 192.168.1.100 address to anything you want.
>
> But
On 9/9/2014 23:17, Len Conrad wrote:
>
> cat /usr/local/bin/bind_rss_history.sh
>
> #!/bin/sh
> touch /var/tmp/bind_rss_history.txt
>
> RSS=`ps auxw | awk '/^bind.*named/{print $6}'`
>
> NOW=`date "+%Y-%m-%d %H:%M:%S"`
>
> echo "$NOW $RSS" | awk '{printf "%10s%10s%11s\n",$1,$2,$3}' >>
> /va
At 09:40 PM 9/9/2014, you wrote:
>On 9/9/2014 05:05, lcon...@go2france.com wrote:
>> freebsd 10.0, bind-9.10.0-p2
>>
>> logging the rss field for named process:
>>
>>
>> less /var/tmp/bind_rss_history.txt
>>
>> This never happened with earlier BIND9, and our mx1 uses this recursive
>> BIND mach
On 9/9/2014 05:05, lcon...@go2france.com wrote:
> freebsd 10.0, bind-9.10.0-p2
>
> logging the rss field for named process:
>
>
> less /var/tmp/bind_rss_history.txt
>
> This never happened with earlier BIND9, and our mx1 uses this recursive
> BIND machine for all domain/ptr lookups
>
> I've n
In message , LuKreme writes:
> On 09 Sep 2014, at 19:42 , LuKreme wrote:
> > # named-checkconf -z | grep -v loaded
>
> Never mind. I recreated the files from scratch and the errors went away.
Which, presumably, is because all the records have relative names. You
still need to fix named.conf be
On 09 Sep 2014, at 19:42 , LuKreme wrote:
> # named-checkconf -z | grep -v loaded
Never mind. I recreated the files from scratch and the errors went away.
--
I DID NOT SEE ELVIS Bart chalkboard Ep. 7G07
___
Please visit https://lists.isc.org/mailma
In message <3cadc2fc-7338-4ac0-a6a2-c1aac48cb...@kreme.com>, LuKreme writes:
> # named-checkconf -z | grep -v loaded
> master/bt.tld:3: ignoring out-of-zone data (bt.tld)
> master/bt.tld:15: ignoring out-of-zone data (webdav.bt.tld)
> _default/dw.tld/IN: bad zone
> master/bt.tld:16: ignoring out-o
# named-checkconf -z | grep -v loaded
master/bt.tld:3: ignoring out-of-zone data (bt.tld)
master/bt.tld:15: ignoring out-of-zone data (webdav.bt.tld)
_default/dw.tld/IN: bad zone
master/bt.tld:16: ignoring out-of-zone data (www.bt.tld)
zone dw.tld/IN: has 0 SOA records
zone dw.tld/IN: has no NS rec
___
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe
from this list
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
Do you guys have max-cache-size set? I didn't see it in the borderworlds
named.conf. I've seen similar growth problems when testing 9.x before
setting that (experiment at the time just to see what would happen, and
confirmed this behavior). Set sensible resource limits based on available
resourc
I'm having the exactly same issue. Take a look at my post @ServerFault:
http://serverfault.com/questions/616752/bind-9-10-constantly-killed-on-freebsd-10-0-with-out-of-swap-space
Sent from my iPhone
On 09/09/2014, at 11:15, "Thomas Schulz" wrote:
>> Hello
>>
>> I recently upgraded my authorit
> Hello
>
> I recently upgraded my authoritative nameservers to bind-9.10.0-P2 and
> after a while one of them ended up using all its swap and the named
> process got killed. The other servers are seeing similar behaviour, but
> I restarted named on all of them to postpone further crashes.
>
>
Hello
I recently upgraded my authoritative nameservers to bind-9.10.0-P2 and
after a while one of them ended up using all its swap and the named
process got killed. The other servers are seeing similar behaviour, but
I restarted named on all of them to postpone further crashes.
I am using ra
14 matches
Mail list logo
