Vladimir wrote:
Hi, Jens.
I now attach my config file with zones and log files.
At 19:13 i have started named.
At 19:15 "dig 127.0.0.1"
JR> I'm busy for next 2 days. I'll prove it on Thursday if it's not to
JR> late for you, ok?
JR> Ok, I saved you cfg's into orig/, copied them into a new/
JR> di
Vladimir wrote:
Hi, Jens.
I now attach my config file with zones and log files.
At 19:13 i have started named.
At 19:15 "dig 127.0.0.1"
JR> I'm busy for next 2 days. I'll prove it on Thursday if it's not to
JR> late for you, ok?
And where are you?
Sorry, I've been very busy in last weeks. But
Vladimir wrote:
Hi, Jens.
Hi Vladimir,
JR> You have 2 lines with defined acl's in your config and allow
JR> only for requests matching the one of the list entries.
JR> If I were in your situation, I would remove them for testing
JR> to see whether it works than or not. I don't have any experience
Vladimir wrote:
Здравствуйте, Jens.
Здравствуйте Vladimir,
you've forgotten to cc questions@ - added.
Вы писали 25 октября 2003 г., 19:24:56:
JR> Vladimir wrote:
Hi, freebsd-questions.
;; res_nsend: Operation timed out
JR> Furthermore I don't use acl's, I'm using packet filtering.
?
You have
Vladimir wrote:
Hi, freebsd-questions.
Can some one help with subj?
-
# dig 127.0.0.1
; <<>> DiG 8.3 <<>> 127.0.0.1
;; res options: init recurs defnam dnsrch
;; res_nsend: Operation timed out
On my workstation:
$ cat /etc/resolv.conf
search muppets.liwing.de
nameserver 10.62.10.7
nameserve